GEDCOM is a “standard” format devised by the Church of the Latter Day Saints<\/a> to support GEnealogical Data COMmunication of family history records.<\/p>\n There is an excellent and detailed article on the history and use of GEDCOM on the Encyclopedia of Genealogy<\/a>.<\/p>\n There is also a useful GEDCOM page<\/a> in Wikipedia.<\/p>\n As of version 7, Family Historian supports GEDCOM Standard Release 5.5.1.<\/p>\n Family Historian (\u0192h<\/span><\/span>) stores its information directly in a GEDCOM file and (from \u0192h<\/span><\/span> version 7) exports it by default as UTF-8 without a BOM, which will work for a variety of destinations. Earlier versions of \u0192h<\/span><\/span> used different formats, so take care to check compatibility with your intended destination. In all versions, you may need to use addtionial tools to prepare your data.<\/p>\n These tools include the Split Tree Helper,<\/a> Import\/Export > Export > GEDCOM<\/a> File, Utility ~ RJT Family Historian Converter<\/a>, Utility ~ Res Privata – Gedcom Privatisation<\/a>, and Family Historian Plugins such as Export Gedcom File<\/a>.<\/p>\n One thing worth remembering is that most other genealogy programs do not use GEDCOM as their standard format in the way \u0192h<\/span><\/span> does, so when sending a file to people not using \u0192h<\/span><\/span>, make sure you tell them they will need to use the Import or Merge option to load the GEDCOM data into their program.<\/p>\n For more information see the Import and Export topics.<\/p>\n The standard fields defined by GEDCOM have Tag names, such as SEX, DATE, NOTE, or NAME, that are followed by their data value.<\/p>\n GEDCOM allows custom user-defined fields with an underscore (_) prefix on the field Tag names, such as _ROOT, _EMAIL, or _TYPE, to distinguish them from standard Tag names.<\/p>\n\u0192h<\/span><\/span> uses these to support additional functionality. See the GEDCOM Extension List<\/a>.<\/p>\n Some genealogy products add custom fields without an underscore (_) prefix and are thus invalid GEDCOM. These and any other unrecognised field Tag names imported to \u0192h<\/span><\/span> are treated as Uncategorised Data Fields (UDF)<\/a>.<\/p>\n","protected":false},"template":"","fh_version":[13,14,15,739],"skill_level":[18,17,16],"topic":[66,93],"class_list":["post-9756","kb_article","type-kb_article","status-publish","hentry","fh_version-v4","fh_version-v5","fh_version-v6","fh_version-v7","search_term-gedcom","skill_level-advanced","skill_level-intermediate","skill_level-newcomer","topic-fh-folders-and-files","topic-gedcom-files"],"_links":{"self":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article\/9756","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article"}],"about":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/types\/kb_article"}],"wp:attachment":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/media?parent=9756"}],"wp:term":[{"taxonomy":"fh_version","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/fh_version?post=9756"},{"taxonomy":"skill_level","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/skill_level?post=9756"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/topic?post=9756"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Family Historian<\/h3>\n
GEDCOM Extensions<\/h3>\n