1 CHAR ANSI<\/code><\/p>\nIt is typically ignored by other programs and can be safely deleted.<\/p>\n
Unique Identity: _UID<\/h4>\n
This tag holds a unique code for Family Historian and appears after the standard tags in the Header Record:<\/p>\n
1 CHAR ANSI<\/code>
\n1 _UID {13F463F0-5340-4056-AB3F-49972FE733CB}<\/code><\/p>\nIt is typically ignored by other programs and can be safely deleted.<\/p>\n
Prepared Citation: _PCIT<\/h4>\n
This tag holds the currently Prepared Citation introduced by V7 and only appears in the Header Record:<\/p>\n
1 _PCIT<\/code>
\n2 SOUR @S55@<\/code>
\n3 _FIELD TX-PAGE<\/code>
\n4 TEXT Page 321<\/code>
\n3 QUAY 0<\/code><\/p>\nIt is typically ignored by other programs and can be safely deleted with its subsidiary tags.<\/p>\n
Used Record Ids: _USED<\/h4>\n
This holds a list of used Record Id introduced by V7 and appears in the Header Record:<\/p>\n
1 _USED I140,F62,N4,S64,R8,U2,B1,O50,P88,E1,T68<\/code><\/p>\nIt is typically ignored by other programs and can be safely deleted.<\/p>\n
Named Lists: _LIST, _FLAG, _NOTE, _IDS<\/h4>\n
These tags define Named Lists and appear in the Header Record:<\/p>\n
1 _LIST Key Individuals<\/code>
\n2 _FLAG E<\/code>
\n2 _NOTE Named List Note in Properties<\/code>
\n2 _IDS I3,I2<\/code>
\n3 _NOTE Named List Note for Record I2<\/code>
\n2 _IDS I19,I15
\n<\/code>
\nThese are typically ignored by other programs and can be safely deleted (or possibly converted into a Note Record with labels for Named List:, Editing Enabled, and Note: together with a list of Record Id & Names, and linked to from the associated Records).<\/p>\nGiven Name Used: _USED<\/h4>\n
This tag is subordinate to the NAME tag in Individual Records:<\/p>\n
1 NAME Anthony Edward \/Munro\/<\/code>
\n2 _USED Tony<\/code><\/p>\nSome programs recognise this tag but at level 1 i.e. 1 _USED Tony, or it could be moved to a NOTE and labelled Given Name Used:.<\/p>\n
Custom Attribute: _ATTR<\/h4>\n
This Custom Attribute tag is similar to the standard EVEN tag for Custom Events, but may have a text value:<\/p>\n
1 _ATTR Singing<\/code>
\n2 TYPE Hobby<\/code><\/p>\nMany programs will accept this if converted to a custom EVENt tag, and the text value could also be moved to a NOTE and labelled Attribute Value:.
\nFor programs that accept GEDCOM V5.5.1 it can be converted to a custom FACT tag.<\/p>\n
Sentence Template: _SENT<\/h4>\n
This overrides the default Fact Set Sentence Template for a specific Fact (Event\/Attribute):<\/p>\n
2 _SENT He was {a\/an value} {place} {age}
\n<\/code>
\nIt is typically ignored by other programs and can be safely deleted.<\/p>\nOther Place: _PLAC<\/h4>\n
This defines the EMIGration To place and IMMIgration From place:<\/p>\n
1 EMIG<\/code>
\n2 PLAC Liverpool<\/code>
\n2 _PLAC America<\/code>
\n1 IMMI<\/code>
\n2 PLAC America<\/code>
\n2 _PLAC Liverpool
\n<\/code>
\nIt is typically ignored by other programs and can be safely deleted, or could be moved to a NOTE and labelled Emigration To: or Immigration From:.<\/p>\nPedigree: _PEDI<\/h4>\n
This tag is subordinate to the Parents Family FAMC tag in Individual Records and similar to the standard PEDI tag but for additional relationships. These are typically ignored by other programs and can be safely deleted, or could be moved to a NOTE and labelled Pedigree: with the associated subsidiary field data.<\/p>\n
Witness Roles: _SHAR, _SHAN<\/h4>\n
These can be added to any Fact (Event\/Attribute) from V6. They are typically ignored by other programs and can be safely deleted, or could be moved to a record NOTE and labelled Relationship: with the associated subsidiary field data.<\/p>\n
Record Flags: _FLGS, __????<\/h4>\n
Record Flags are added to the end of an Individual Record, just before the change information:<\/p>\n
1 FAMC @F123@<\/code>
\n1 _FLGS<\/code>
\n2 __1871_CENSUS 1871 Census<\/code>
\n2 __1881_CENSUS 1881 Census<\/code>
\n1 CHAN<\/code>
\n2 DATE 22 APR 2007<\/code>
\n3 TIME 12:41:04
\n<\/code>
\nThe code block begins with a _FLGS tag and each subordinate line specifies which flags apply to this individual.<\/p>\nEach flag is given its own unique GEDCOM tag, starting with 2 underscores and then up to 13 characters from the flag name, which follows the tag.<\/p>\n
The flag tag is generated from the flag name as follows:<\/p>\n
\n- Remove all accents (i.e. replace each accented character with the equivalent unaccented character).<\/li>\n
- Convert all letters to uppercase.<\/li>\n
- Remove all characters except spaces, letters, and digits.<\/li>\n
- Convert all spaces to underscores.<\/li>\n
- Add 2 underscores on the front.<\/li>\n
- Truncate at 15 characters.<\/li>\n<\/ol>\n
These tags are typically ignored by other programs and can be safely deleted, or could be altered into custom EVENt tags, or moved to a NOTE and labelled Record Flag:.<\/p>\n
Fact Flags: _FLGS, __????<\/h4>\n
Fact Flags may be added to Individual or Family facts and were introduced by V7:<\/p>\n
2 _FLGS<\/code>
\n3 __PRIVATE Private<\/code>
\n3 __PREFERRED Preferred<\/code>
\n3 __TENTATIVE Tentative<\/code>
\n3 __REJECTED Rejected<\/code><\/p>\nThe code block begins with a _FLGS tag and each subordinate line specifies which flags apply to this fact. Only the four flag names shown are supported.<\/p>\n
These tags are typically ignored by other programs and can be safely deleted, or could be converted to a local NOTE and labelled Fact Flag:.<\/p>\n
E-mail\/Web Address: _EMAIL, _WEB<\/h4>\n
These define an E-mail or Website address for a Fact (Event\/Attribute) or for a Repository Record or Submitter Record:<\/p>\n
Individual\/Family Fact:
\n2 _EMAIL info@internet.com<\/code>
\n2 _WEB http:\/\/www.internet.com<\/code>
\nRepository\/Submitter Record:
\n1 _EMAIL info@internet.com<\/code>
\n1 _WEB http:\/\/www.internet.com<\/code>
\nThey often have equivalents in other programs such as the GEDCOM 5.5.1 tags EMAIL and WWW, or could be moved to a NOTE and labelled E-mail Address: or Website Address:, or appended to the PHONe tag.<\/p>\nSort Date:_SDATE<\/h4>\n
This defines a fact sort date introduced by V7 to supplement the standard fact DATE:<\/p>\n
2 DATE 2000<\/code>
\n2 _SDATE 1 MAY 2000<\/code><\/p>\nSome other programs support this fact tag as a de facto standard.
\nOtherwise, it is typically ignored by other programs and can be safely deleted, or could be converted to a local NOTE and labelled Sort Date:.<\/p>\n
Marriage Status: _STAT<\/h4>\n
This supplements the partnership status of a Family Record:<\/p>\n
1 _STAT Never Married
\n<\/code>
\nIt is typically ignored by other programs and can be safely deleted, but could be altered into a custom EVENt tag, or moved to a NOTE and labelled Marriage Status:.<\/p>\nAssessment Options: _QUAY<\/h4>\n
This adds citation assessment options introduced by V7 to supplement the standard QUAY tag:<\/p>\n
2 SOUR @S19@<\/code>
\n3 _QUAY 0x98<\/code><\/p>\nIt is typically ignored by other programs and can be safely deleted, but could be altered into a local NOTE and labelled Assessment:.<\/p>\n
Source Template Metafield: _FIELD<\/h4>\n
This tag appears in Source Template records and Source Citations to identify metafield definitions and values introduced by V7:<\/p>\n
3 _FIELD TX-PAGE<\/code>
\n4 TEXT Page 567<\/code><\/p>\nIt is typically ignored by other programs and can be deleted with its subsidiary tags, but could be altered into a local NOTE and labelled Metafield:.<\/p>\n
Source Type: _TYPE<\/h4>\n
This categorises the type of each Source Record:<\/p>\n
1 _TYPE Census Record
\n<\/code>
\nIt is typically ignored by other programs and can be safely deleted, but could be moved to a NOTE and labelled Source Type:.<\/p>\nFormatted Rich Text: _TEXT, _FMT, _LINK_?, _LKID<\/h4>\n
These define formatted Rich Text sections and record links introduced with V7:<\/p>\n
0 @N1@ NOTE The Munro family from Scotland supported the <i>Glorious Revolution of 1688<\/i> with clan chiefs at <u>Foulis Castle<\/u>.<\/code>
\n1 _TEXT<\/code>
\n2 _FMT 1<\/code><\/p>\n1 NOTE <b>Bold<\/b> <i>Italic<\/i> <u>Underline<\/u> <s>Strikeout<\/s><\/code>
\n2 _FMT 1<\/code>
\n2 _LINK_I @I6@<\/code>
\n3 _LKID 40<\/code><\/p>\nThese tags are typically ignored by other programs and can be safely deleted.
\nThe note text can be converted to plain text, although some programs recognise some of the formatting codes.<\/p>\n
Multimedia: _NOTE, _FILE, _DATE, _KEYS<\/h4>\n
These define the Picture Note, Linked File, Media Date & Keywords for a Multimedia Record:<\/p>\n
1 TITL Anthony Munro<\/code>
\n1 _NOTE Taken using a sepia effect on a digital camera<\/code>
\n1 _FILE C:\\Users\\Mike\\Documents\\Family Historian Projects\\My Tree\\My Tree.fh_data\\Media\\IMG_0083.JPG<\/code>
\n1 _DATE 2001<\/code>
\n1 _KEYS Picture
\n<\/code>
\nThese are typically ignored by other programs, but could be moved to a NOTE and labelled Picture Note:, Linked File:, Media Date: & Keywords: respectively.<\/p>\nAlthough the _FILE tag is typically ignored by other programs, it is usually recognised if converted to a FILE tag, as when File > Import\/Export > Export > GEDCOM File > Destination: Family Tree Maker<\/a> is used.<\/p>\nMultimedia: _ASID, _SEQ, _AREA, _EXCL, _CAPT, _NOTA<\/h4>\n
These define the attributes of a Multimedia image linked to a particular Individual\/Family\/Source Record:<\/p>\n
Individual\/Family\/Source Record Local Media Object:<\/p>\n
1 OBJE @O4@<\/code>
\n2 _ASID 3<\/code><\/p>\n1 OBJE @O7@<\/code>
\n2 _SEQ 1
\n<\/code>
\nMultimedia Record:<\/p>\n1 _NOTA Photo of Wedding<\/code>
\n2 _SEQ 1<\/code>
\n2 _AREA {154,46,243,127}<\/code>
\n2 _EXCL ALL<\/code>
\n2 _CAPT Y
\n<\/code>
\nThese are typically ignored by other programs, and probably best deleted as it is not obvious where these attributes can be saved in standard GEDCOM.<\/p>\nThe frame _AREA tags can be eliminated by using the Convert File Links<\/a> Plugin, or the Export Gedcom File<\/a> Plugin, which also moves some other Multimedia tags to a local NOTE with appropriate labels. They may be converted to GEDCOM V7.0 CROP tags supportd by a few programs.<\/p>\nPlace Record: _PLAC<\/h4>\n
Place Records were introduced with V6 and are typically ignored by other programs. They can either be deleted or converted to Source Records with a type such as Place Details.<\/p>\n
Research Note Record: _RNOT<\/h4>\n
Research Notes were introduced by V7 and are typically ignored by other programs. They can either be deleted or converted to standard Note records.<\/p>\n
Source Template Record: _SRCT<\/h4>\n
Source Templates were introduced by V7 and are typically ignored by other programs. They are complicated to handle for migration to other programs.<\/p>\n","protected":false},"template":"","fh_version":[13,14,15,739],"skill_level":[18,17],"topic":[93,58,73],"class_list":["post-10758","kb_article","type-kb_article","status-publish","hentry","fh_version-v4","fh_version-v5","fh_version-v6","fh_version-v7","search_term-custom-gedcom-extensions","search_term-gedcom","search_term-gedcom-extensions","skill_level-advanced","skill_level-intermediate","topic-gedcom-files","topic-importing-and-exporting","topic-writing-plugins"],"_links":{"self":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article\/10758","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=10758"}],"wp:term":[{"taxonomy":"fh_version","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/fh_version?post=10758"},{"taxonomy":"skill_level","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/skill_level?post=10758"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/topic?post=10758"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}