This is an old revision of the document!


Export Gedcom File ~ Output Formats

Introduction

The philosophy behind this plugin is that fh holds the master database, and the exports are secondary copies for other products, perhaps to obtain online hints in Ancestry, MyHeritage, etc, or to carry on a tablet when visiting record offices, churches, relatives, etc. Thus it is not critical that every tiny detail migrates from fh to the secondary product database. Migrating every detail is often not possible anyway, because of the various dialects of GEDCOM in use. Migrating the data back from the other product into fh is unlikely to succeed.

Wherever possible (except as defined below) exported data adheres to the GEDCOM Standard Release 5.5 excluding non-standard tags, with custom Events using the EVEN tag. Unless stated otherwise all export modes use the (Std) Standard GEDCOM 5.5 export rules.

Most export modes convert every double @@ to a single @ as many genealogy products do not handle them correctly. Exceptions are the modes that adhere to the GEDCOM standards.

For each export mode the Extra Options tab and Other Options tab allow alternative Rule choices. * See the F.A.Q. for further advice.

The Media formats are explained in the Output Media Style section.

See the following sections for default rules and other advice for each genealogy product:

(Std) Standard GEDCOM 5.5

Most fh custom tags are converted to GEDCOM standard tags. Otherwise they are simply deleted, including the GEDCOM header optional FILE name tag.

Synthesised Custom Events and Note Records and Source Records have a prefix Ω character (ZZ in ANSI/ISO mode or fh V5) to differentiate them from original records.

See the (Std) Standard GEDCOM 5.5 help page for the full GEDCOM export details.

(Sdr) Standard GEDCOM Draft 5.5.1

Most fh custom tags are converted to GEDCOM Draft standard tags. Otherwise they are simply deleted, including the GEDCOM header optional FILE name tag.

Synthesised Custom Events and Note Records and Source Records have a prefix Ω character (ZZ in ANSI/ISO mode or fh V5) to differentiate them from original records.

See the (Sdr) Standard GEDCOM Draft 5.5.1 help page for the full GEDCOM Draft export details.

(ANC) Ancestry Family Tree

All the Ancestry websites support a Family Trees option to upload GEDCOM files.

See the (ANC) Ancestry Family Tree help page for full GEDCOM export and import details.

(FH5) Family Historian 5

This mode is designed to allow fh V6 projects to be exported to fh V5 (or earlier) with minimum loss of data.

All fh custom tags are retained except for Fact Witness Roles and Place Records as defined above.

The default Multimedia mode is (FILE~REL) Multimedia via Relative Link Records to allow the Media folder structure and all Face/Detail frame details to migrate with the GEDCOM, so the files are NOT copied to the Export Folder.

(FST) Family Search Family Tree

The FamilySearch website allows GEDCOM files to be uploaded to a Pedigree Resource File that can display hourglass family trees.

See the (FST) Family Search Family Tree help page for full GEDCOM export and import details.

(FTA) Family Tree Analyzer

This uses the (Std) Standard GEDCOM 5.5 settings except as follows.

All the Named List tags are always Removed entirely. See Extra Options tab Named List Entry 1 _LIST:

The fh custom File Root (_ROOT) tag is always retained. See Extra Options tab File Root 1 _ROOT:

Each Source Record Short Title (ABBR) is converted to a full TITLe, unless that already exists, whereupon it is converted to a Record local Note with a Short Title: label.

By default all Media are excluded because Family Tree Analyzer does not use them.

(FTD) Family Tree DNA

This online tree offers DNA matching services.

See the (FTD) Family Tree DNA help page for full GEDCOM export and import details.

(FTM) Family Tree Maker

The (+) Full Data option intends Gedcom files to be exported to FTM, updated with Ancestry hints, and returned to fh as detailed in Exchanging Data with Ancestry and FTM. However, the return to fh import Plugin still needs to be developed.

FTM does not adhere to GEDCOM Standard Release 5.5 and needs extensive export rules.

See the (FTM) Family Tree Maker help page for full GEDCOM export and import details.

(FMP) FindMyPast Family Tree

All the FindMyPast websites support a Family tree option to upload GEDCOM files.

See the (FMP) FindMyPast Family Tree help page for full GEDCOM export and import details.

(GWC) GEDmill Website Creator

GEDmill from Logic Mill offers a free website/CD/DVD family history creation utility.

See the (GWC) GEDmill Website Creator help page for full GEDCOM export and import details.

(GST) GedSite by John Cardinal

GedSite launched in 2016 offers a website/CD/DVD family history building toolset.

It supports Witnessed/Shared Events and most other features of fh.

See the (GST) GedSite help page for full GEDCOM export and import details.

(GSP) GedStar Pro for Android

GedStar Pro has two components: a program for Windows that creates an SQLite database to download to the Android app.

See the (GSP) GedStar Pro for Android help page for full GEDCOM export and import details.

(GRT) Genes Reunited Tree

This uses (Std) Standard GEDCOM 5.5 settings but some DATE fields are adjusted in length or format.

See Extra Options tab Date Field %d DATE:

The date fields are reduced to 30 characters maximum.
e.g.
FROM 21 JAN 1900 TO 12 FEB 1900 becomes 21 JAN 1900 TO 12 FEB 1900
BET 21 JAN 1900 AND 12 FEB 1900 becomes BET 21 JAN 1900 & 12 FEB 1900

Birth/Death event Range/Period dates extract the first date and make it Approx to satisfy the Year of Birth/Death requirements, and the original date is added to the event local Note.
e.g.
Born BET JAN 1900 AND FEB 1909 becomes ABT JAN 1900
Died AFT 12 MAR 1710/11 becomes ABT 12 MAR 1710

By default all Media are excluded.

(GFT) Gramps Family Tree

This uses (Std) Standard GEDCOM 5.5 settings except as follows.

Several standard Individual Name fields are moved to a labelled Record local Note otherwise they upset the name:
See Other Options tab Name Given 2 GIVN: that is moved to a Name Given: label.
See Other Options tab Surname Prefix 2 SPFX: that goes to a Surname Prefix: label.
See Other Options tab Surname 2 SURN: that is moved in to a Surname: label.
In any 1 NAME field, any text following /Surname/ is moved to a Name Tail: label.

The Associated Person tag 2 TYPE INDI is moved to its local Note with a Descriptor: label.

Each Source Record Short Title (ABBR) is converted to a full TITLe, unless that already exists, whereupon it is converted to a Record local Note with a Short Title: label.

Each Note Record Custom Id (REFN) is added to the Note with a Custom Id: label.

Each Source Note is converted to a synthesised Source Record where the TITLe starts with Ω Source Note: and followed by the original Source Note text, but some of these are still not supported.

Each local Note of any local Media Object is converted to a linked synthesised Note Record.

(HER) Heredis by BSD Concept

There is a version of Heredis for Windows, Mac, iOS, and Android.

The free trial Windows demo is limited to 50 Individuals but allows unlimited GEDCOM import & export.

All versions support Witnessed/Shared Events similar to fh.

See the (HER) Heredis by BSD Concept help page for full GEDCOM export and import details.

(LFT) Legacy Family Tree

The Legacy Family Tree Standard Edition is free, whereas the Deluxe Edition offers more features but must be bought.

Both editions support Witnessed/Shared Events similar to fh.

See the (LFT) Legacy Family Tree help page for full GEDCOM export and import details.

(MYH) MyHeritage Family Tree

MyHeritage offers both free and premium website Family Trees and Family Tree Builder Windows program. There are also iOS and Android apps in support of the website.

See the (MYH) MyHeritage Family Tree help page for full GEDCOM export and import details.

(RMT) Roots Magic Tree

RootsMagic Essentials is free, whereas the Basic and Standard versions offer more features but must be bought.

All versions support Witnessed/Shared Events similar to fh.

See the (RMT) Roots Magic Tree help page for full GEDCOM export and import details.

(RWW) RootsWeb WorldConnect

This uses (Std) Standard GEDCOM 5.5 settings except as follows.

Each ASSOciated Person is converted to a custom Event using the EVEN tag with a Fact local Note with an Associate: and Relationship: label.

All CHANge date/time tags are Removed entirely. See Extra Options tab Updated 1 CHAN:

(TNG) The Next Generation

The Next Generation is a popular, Internet based, genealogy product.

See the (TNG) The Next Generation help page for full GEDCOM export and import details.

(TPT) TribalPages Tree

TribalPages offers both free and subscription website Family Trees but with limited GEDCOM support.

See the (TPT) TribalPages Tree help page for full GEDCOM export and import details.

(ZPG) ZoomPast Genealogy

ZoomPast launched in 2015 offers free website Family Trees with good GEDCOM support.

See the (ZPG) ZoomPast Genealogy help page for full GEDCOM export and import details.

(CEA/B) Custom Export Alpha/Bravo

These default to (Std) Standard GEDCOM 5.5 mode, but allow two other export modes to be customised.

Use these for target products that are not listed above.

Return to Export Gedcom File Plugin Introduction.

CC Attribution-Noncommercial-Share Alike 4.0 International
Runs using DokuWiki Recent changes RSS feed www.rjt.org.uk