|A GEDCOM is a text based file that details each individual and relationship in your Family Tree database.
GEDCOM is the most commonly used method to tranfer data between Genealogy Applications.
Regardless if your previous program was on a Mac, on Windows or on linux it is an agreed industry standard that we all meet GEDCOM specification 5.5 (Released in 1996).
iFamily for Mac Custom Tags
iFamily makes use of custom tags like most other programs on the market. These assist our program in recreating your
database quickly and will be ignored by other importers. They can be turned off as an option when conducting an export.
The following custom tags are used by iFamily and can be found in the header of each GEDCOM file:
Custom Tags genrated by iFamily for Leopard are as follows:
_CMTS = The comments field for a Person. It may have CONT and CONC sub-records
_CROP = The crop rectangle for the thumbnail of a Picture
_DATE = The date entered for a thumbnail or of a Source
_FPER = The Focal Person of the database when the Gedcom file was created
_FREL = The father-child relationship type. Natural, Adopted, Step or Foster
_GMAP = The Google Maps Geocode for an Event Place
_LATI = The latitude of an Event Place
_LONG = The longitude of an Event Place
_MREL = The mother-child relationship type. Natural, Adopted, Step or Foster
_OCTI = The occupation/title of a Person
_OFNM = The original file name of a Picture
_PROB = The Probability that a parent-child relationship is true
_SEQN = The sequence number of a thumbnail for a Person
_TOPI = The topic of a Source Reference (Citation)
_TYPE = The type of a Source
Some more text
You can view the contents of a GEDCOM file with a text editor such as TextEdit, TextWrangler or Pages
If you want to learn more about the structure of a GEDCOM, do an export of your whole database with Indented Gedcom Lines ticked to show the nesting
iFamily will provide a set of reports upon completing a GEDCOM load that will allow you to work through any faulty dates (inconsistent date formats) and unconnected and doubly connected identities who were exported from other programs.
Setting the diagram to show the maximum number of ancestral generations then choosing to export only the identities in the diagram can give you a smaller file that you can send to co-researchers when you don't want to expose your whole database.