The Complete Genealogy Products

 
 

 

Home Reporter Builder GedPad Testimonials Compliance Compatibility Download Purchase Support History  


The Complete Genealogy Reporter
and The Complete Genealogy Builder are 99.9% compliant with the GEDCOM 5.5 standard.  The standard was created by The Church of Jesus Christ of Latter-day Saints and is published at their web site (www.familysearch.org).  

Although documentation exists of an alleged revision dated 10 January 1996, the officially published version of the GEDCOM 5.5 standard remains the original document dated 2 January 1996, and this is considered by The Complete Genealogy Reporter and The Complete Genealogy Builder to be the true standards definition (assuming that the "revision" must have been withdrawn.)

GEDCOM compliance is not important for users who are comfortable with being "locked-in" to the methodology and non-standard data capabilities of a particular genealogy program, but it is very important for those users who require the ability to transfer data freely between different genealogy products, websites, and utility programs, with maximum reliability and data integrity.

The Complete Genealogy Builder also supports many of the additional data types of the GEDCOM 5.5.1 proposal.  These include, for example, the ability to specify the latitude and longitude of places, and the FAX, eMail, and Web components of addresses.  These are only transportable via export and import with other genealogy products that support these data types.

Each product additionally supports capabilities that are powerful and are found in some other genealogy programs.  An example of this are "Cutouts" of images, corresponding the "Frame Links" of Family Historian and the "Marked Faces" of MyHeritage Family Tree Builder.  The Complete Genealogy Reporter understands each of these image forms and correctly includes them in the report exactly as specified within the respective genealogy program.  Moreover, The Complete Genealogy Builder will import a GEDCOM file from Family Historian and export a GEDCOM file for Family Tree Builder with all of the image Frame Links from Family Historian correctly expressed as Marked Faces - and vice-versa..

Each product has evolved to understand many of the major non-standard data types, and the non-standard application of standard data types, that may be exported by other leading genealogy programs.  Examples of these non-standard data types include "_MREL" and "_FREL" as extended alternatives to the standard PEDIgree data type, and "_PRIM", "_PREF", "_SCAN", and "_TYPE" as designations for media objects.

The Complete Genealogy Reporter and The Complete Genealogy Builder will import GEDCOM files created in the following standard formats: ASCII, ANSEL and Unicode, and in the following non-standard (but widely supported) formats: ANSI and UTF-8.  Any of these formats may be selected as the export format for a GEDCOM exported by The Complete Genealogy Builder.

The GEDCOM 5.5 standard provides for the following data fields.  All of these are supported by The Complete Genealogy Builder, except for: (i) "FORM <PLACE_HIERARCHY>" subordinate to PLACe data, and (ii) a TYPE OBJE tag subordinate to an ASSO tag (Association Structure).  The latter is not supported because it can apply only to BLOB-encoded embedded media objects, which are extremely rarely used.  (Most genealogy programs are not programmed to process BLOB-encoded media in any case.)

RECORDS
 

SUB-STRUCTURES (EVENTS AND ATTRIBUTES)
 

Header Record
0 HEAD
   1 SOUR <APPROVED_SYSTEM_ID>
      2 VERS <VERSION_NUMBER>
      2 NAME <NAME_OF_PRODUCT>
      2 CORP <NAME_OF_BUSINESS>
         3 <<ADDRESS_STRUCTURE>>
      2 DATA <NAME_OF_SOURCE_DATA>
         3 DATE <PUBLICATION_DATE>
         3 COPR <COPYRIGHT_SOURCE_DATA>
   1 DEST <RECEIVING_SYSTEM_NAME>
   1 DATE <TRANSMISSION_DATE>
      2 TIME <TIME_VALUE>
   1 SUBN @XREF:SUBN@
   1 SUBM @XREF:SUBM@
   1 FILE <FILE_NAME>
   1 COPR <COPYRIGHT_GEDCOM_FILE>
   1 GEDC
      2 VERS <VERSION_NUMBER>
         2 FORM <GEDCOM_FORM>
   1 CHAR <CHARACTER_SET>
      2 VERS <VERSION_NUMBER>
   1 LANG <LANGUAGE_OF_TEXT>
   1 PLAC
      2 FORM <PLACE_HIERARCHY>  NOT SUPPORTED
   1 NOTE <GEDCOM_CONTENT_DESCRIPTION>
      2 [CONT|CONC] <GEDCOM_CONTENT_DESCRIPTION>

Submission Record
0 @XREF:SUBN@ SUBN
   1 SUBM @XREF:SUBM@
   1 FAMF <NAME_OF_FAMILY_FILE>
   1 TEMP <TEMPLE_CODE>
   1 ANCE <GENERATIONS_OF_ANCESTORS>
   1 DESC <GENERATIONS_OF_DESCENDANTS>
   1 ORDI <ORDINANCE_PROCESS_FLAG>
   1 RIN <AUTOMATED_RECORD_ID>

Submitter Record(s)
0 @<XREF:SUBM>@ SUBM
   1 NAME <SUBMITTER_NAME>
   1 <<ADDRESS_STRUCTURE>>
   1 <<MULTIMEDIA_LINK>>
   1 LANG <LANGUAGE_PREFERENCE>
   1 RFN <SUBMITTER_REGISTERED_RFN>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>

Individual Record(s)
0 @XREF:INDI@ INDI
   1 RESN <RESTRICTION_NOTICE>
   1 <<PERSONAL_NAME_STRUCTURE>>
   1 SEX <SEX_VALUE>
   1 <<INDIVIDUAL_EVENT_STRUCTURE>>
   1 <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>>
   1 <<LDS_INDIVIDUAL_ORDINANCE>>
   1 <<CHILD_TO_FAMILY_LINK>>
   1 <<SPOUSE_TO_FAMILY_LINK>>
   1 SUBM @<XREF:SUBM>@
   1 <<ASSOCIATION_STRUCTURE>>
   1 ALIA @<XREF:INDI>@
   1 ANCI @<XREF:SUBM>
   1 DESI @<XREF:SUBM>
   1 <<SOURCE_CITATION>>
   1 <<MULTIMEDIA_LINK>>
   1 <<NOTE_STRUCTURE>>
   1 RFN <PERMANENT_RECORD_FILE_NUMBER>
   1 AFN <ANCESTRAL_FILE_NUMBER>
   1 REFN <USER_REFERENCE_NUMBER>
      2 TYPE <USER_REFERENCE_TYPE>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>

Family Record(s)
0 @<XREF:FAM>@ FAM
   1 <<FAMILY_EVENT_STRUCTURE>>
      2 HUSB
         3 AGE <AGE_AT_EVENT>
      2 WIFE
         3 AGE <AGE_AT_EVENT>
   1 HUSB @<XREF:INDI>@
   1 WIFE @<XREF:INDI>@
   1 CHIL @<XREF:INDI>@
   1 NCHI <COUNT_OF_CHILDREN>
   1 SUBM @<XREF:SUBM>
   1 <<LDS_SPOUSE_SEALING>>
   1 <<SOURCE_CITATION>>
   1 <<MULTIMEDIA_LINK>>
   1 <<NOTE_STRUCTURE>>
   1 REFN <USER_REFERENCE_NUMBER>
      2 TYPE <USER_REFERENCE_TYPE>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>

Note Record(s)

n @<XREF:NOTE>@ NOTE <SUBMITTER_TEXT>
   1 [ CONC | CONT] <SUBMITTER_TEXT>
   1 <<SOURCE_CITATION>>
   1 REFN <USER_REFERENCE_NUMBER>
      2 TYPE <USER_REFERENCE_TYPE>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>

Source Record(s)
0 @<XREF:SOUR>@ SOUR
   1 DATA
      2 EVEN <EVENTS_RECORDED>
         3 DATE <DATE_PERIOD>
         3 PLAC <SOURCE_JURISDICTION_PLACE>
      2 AGNC <RESPONSIBLE_AGENCY>
      2 <<NOTE_STRUCTURE>>
   1 AUTH <SOURCE_ORIGINATOR>
      2 [CONT|CONC] <SOURCE_ORIGINATOR>
   1 TITL <SOURCE_DESCRIPTIVE_TITLE>
      2 [CONT|CONC] <SOURCE_DESCRIPTIVE_TITLE>
   1 ABBR <SOURCE_FILED_BY_ENTRY>
   1 PUBL <SOURCE_PUBLICATION_FACTS>
      2 [CONT|CONC] <SOURCE_PUBLICATION_FACTS>
   1 TEXT <TEXT_FROM_SOURCE>
      2 [CONT|CONC] <TEXT_FROM_SOURCE>
   1 <<SOURCE_REPOSITORY_CITATION>>
   1 <<MULTIMEDIA_LINK>>
   1 <<NOTE_STRUCTURE>>
   1 REFN <USER_REFERENCE_NUMBER>
      2 TYPE <USER_REFERENCE_TYPE>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>

Repository Record(s)
0 @<XREF:REPO>@ REPO
   1 NAME <NAME_OF_REPOSITORY>
   1 <<ADDRESS_STRUCTURE>>
   1 <<NOTE_STRUCTURE>>
   1 REFN <USER_REFERENCE_NUMBER>
   2 TYPE <USER_REFERENCE_TYPE>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>

Multimedia Object Record(s)
0 @XREF:OBJE@ OBJE
   1 FORM <MULTIMEDIA_FORMAT>
   1 TITL <DESCRIPTIVE_TITLE>
   1 <<NOTE_STRUCTURE>>
   1 BLOB
      2 CONT <ENCODED_MULTIMEDIA_LINE>
   1 OBJE @<XREF:OBJE>@
   1 REFN <USER_REFERENCE_NUMBER>
   2 TYPE <USER_REFERENCE_TYPE>
   1 RIN <AUTOMATED_RECORD_ID>
   1 <<CHANGE_DATE>>


 

Event Detail Structure
n TYPE <EVENT_DESCRIPTOR>
n DATE <DATE_VALUE>
n <<PLACE_STRUCTURE>>
n <<ADDRESS_STRUCTURE>>
n AGE <AGE_AT_EVENT>
n AGNC <RESPONSIBLE_AGENCY>
n CAUS <CAUSE_OF_EVENT>
n <<SOURCE_CITATION>>
n <<MULTIMEDIA_LINK>>
n <<NOTE_STRUCTURE>>

Individual Event Structure (Birth/Christening)
n {CODE} {Y}
   +1 <<EVENT_DETAIL>>
   +1 FAMC
@<XREF:FAM>@
Where {CODE) is one of:
BIRT, CHR
and {Y} may be:
Y to confirm that the event occurred (else blank)

Individual Event Structure (Adoption)
n ADOP {Y}
   +1 <<EVENT_DETAIL>>
   +1 FAMC @<XREF:FAM>@

      +2 ADOP <ADOPTED_BY_WHICH_PARENT>
and {Y} may be:
Y to confirm that the event occurred (else blank)

Individual Event Structure (Other - Standard)
n {CODE} {Y}
   +1 <<EVENT_DETAIL>>
Where {CODE) is one of:
BAPM, BARM, BASM, BLES, CHRA, CONF, FCOM, GRAD, ORDN, EMIG, IMMI, NATU, WILL, RETI, DEAT, BURI, CREM, PROB, CENS
and {Y} may be:
Y to confirm that the event occurred (else blank)

Individual Attribute Structure
n {CODE} <DATA>
   +1 <<EVENT_DETAIL>>
Where {CODE) <DATA> is one of:
CAST <CASTE_NAME>
DSCR <PHYSICAL_DESCRIPTION>
EDUC <SCHOLASTIC_ACHIEVEMENT>
IDNO <NATIONAL_ID_NUMBER>
NATI <NATIONAL_OR_TRIBAL_ORIGIN>
NCHI <COUNT_OF_CHILDREN>
NMR <COUNT_OF_MARRIAGES>
RELI <RELIGIOUS_AFFILIATION>
RESI
SSN <SOCIAL_SECURITY_NUMBER>
TITL <NOBILITY_TYPE_TITLE>
(for RESI, <DATA> is described via the ADDR/PLAC data of the <EVENT_DETAIL>)

Family Event Structure (Standard)
n {CODE} {Y}
   +1 <<EVENT_DETAIL>>
Where {CODE) is one of:
ENGA, MARR, MARB, MARC, MARL, MARS, DIV, DIVF, ANUL, CENS
and {Y} may be:
Y to confirm that the event occurred (else blank)

Family Attribute Structure
n NCHI <DATA>
   +1 <<EVENT_DETAIL>>

Individual/Family Event Structure (Custom)
n EVEN
   +1 <<EVENT_DETAIL>>

 

SUB-STRUCTURES (OTHER)
 

Personal Name Structure
n NAME <NAME_PERSONAL>
   +1 NPFX <NAME_PIECE_PREFIX>
   +1 GIVN <NAME_PIECE_GIVEN>
   +1 NICK <NAME_PIECE_NICKNAME>
   +1 SPFX <NAME_PIECE_SURNAME_PREFIX
   +1 SURN <NAME_PIECE_SURNAME>
   +1 NSFX <NAME_PIECE_SUFFIX>
   +1 <<SOURCE_CITATION>>
   +1 <<NOTE_STRUCTURE>>

Association Structure
n ASSO @<XREF:INDI>@
   +1 TYPE <RECORD_TYPE>
("TYPE OBJE" is NOT SUPPORTED)
   +1 RELA <RELATION_IS_DESCRIPTOR>
   +1 <<NOTE_STRUCTURE>>
   +1 <<SOURCE_CITATION>>

Place Structure
n PLAC <PLACE_VALUE>
   +1 FORM <PLACE_HIERARCHY>
 NOT SUPPORTED
   +1 <<SOURCE_CITATION>>
   +1 <<NOTE_STRUCTURE>>

Address Structure
n ADDR <ADDRESS_LINE>
   +1 CONT <ADDRESS_LINE>
   +1 ADR1 <ADDRESS_LINE1>
   +1 ADR2 <ADDRESS_LINE2>
   +1 CITY <ADDRESS_CITY>
   +1 STAE <ADDRESS_STATE>
   +1 POST <ADDRESS_POSTAL_CODE>
   +1 CTRY <ADDRESS_COUNTRY>
n PHON <PHONE_NUMBER>

Change-Date Structure
n CHAN
   +1 DATE <CHANGE_DATE>
      +2 TIME <TIME_VALUE>
   +1 <<NOTE_STRUCTURE>>

Child-Family Link
n FAMC @<XREF:FAM>@
   +1 PEDI <PEDIGREE_LINKAGE_TYPE>
   +1 <<NOTE_STRUCTURE>>

Spouse-Family Link
n FAMS @<XREF:FAM>@
   +1 <<NOTE_STRUCTURE>>

Multimedia Link (to Multimedia Object Record)
n OBJE @<XREF:OBJE>@

Multimedia Structure (Intra-Record)
n OBJE
   +1 FORM <MULTIMEDIA_FORMAT>
   +1 TITL <DESCRIPTIVE_TITLE>
   +1 FILE <MULTIMEDIA_FILE_REFERENCE>
   +1 <<NOTE_STRUCTURE>>

Note Link (to Note Record)
n NOTE @<XREF:NOTE>@
   +1 <<SOURCE_CITATION>>

Note Link Structure (Intra-Record)
n NOTE <SUBMITTER_TEXT>
   +1 [ CONC | CONT ] <SUBMITTER_TEXT>
   +1 <<SOURCE_CITATION>>

Source Citation Link (to Source Record)
n SOUR @<XREF:SOUR>@

   +1 PAGE <WHERE_WITHIN_SOURCE>
  
+1 EVEN <EVENT_TYPE_CITED_FROM>
     
+2 ROLE <ROLE_IN_EVENT>
  
+1 DATA
     
+2 DATE <ENTRY_RECORDING_DATE>
     
+2 TEXT <TEXT_FROM_SOURCE>
        
+3 [ CONC | CONT ] <TEXT_FROM_SOURCE>
  
+1 QUAY <CERTAINTY_ASSESSMENT>
  
+1 <<MULTIMEDIA_LINK>>
  
+1 <<NOTE_STRUCTURE>>

Source Citation Structure (Intra-Record)
n SOUR <SOURCE_DESCRIPTION>
  
+1 [ CONC | CONT ] <SOURCE_DESCRIPTION>
  
+1 TEXT <TEXT_FROM_SOURCE>
     
+2 [CONC | CONT ] <TEXT_FROM_SOURCE>
  
+1 <<NOTE_STRUCTURE>>

Repository Citation Structure
n REPO @XREF:REPO@
  
+1 <<NOTE_STRUCTURE>>
  
+1 CALN <SOURCE_CALL_NUMBER>
     
+2 MEDI <SOURCE_MEDIA_TYPE>
 

 
The following tags relating to the GEDCOM 5.5.1 proposal are also supported:
  Within a Family Record or Event/Attribute structure:
   1 RESN <RESTRICTION_NOTICE>

Within a Place Structure:
  
+1 MAP
     
+2 LATI <PLACE_LATITUDE>
     
+2 LONG <PLACE_LONGITUDE>

As part of an Address Structure:
   n EMAIL <ADDRESS_EMAIL>
   n FAX <ADDRESS_FAX>
   n WWW <ADDRESS_WEB_PAGE>

 


 

 

(Return to top of page)
 

2006-2013 Nigel Bufton Software. All rights reserved.