Difference between revisions of "Gramps and GEDCOM"

From Gramps
Jump to: navigation, search
((enno)And even though there is no disclaimer on this page, it is outdated too, since there is no mention of the place hierarchy introduced in Gramps version 4.1, for which no GEDCOM data structure exists either.)
m (Revise for the advent of official publications of the 5.5.1 and 7 standards)
 
(29 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{out of date|as per enno on mailing list 20150707}}
+
Gramps uses [[Gramps XML]], which is a less confining format than '''''standard''''' [[GEDCOM]].
  
Gramps uses [[Gramps XML]] which is considered a superior format to [[GEDCOM]] by the Gramps developers. Although Gramps should be able to import most data from GEDCOM through its GEDCOM Import module, many of the Gramps features are not supported by the GEDCOM standard and so GEDCOM Export from a Gramps Family Tree or Gramps XML is a lossy operation. This page shall list all the information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the best compatibility possible. The Gramps version used as a reference is Gramps Trunk, which at the time was Gramps 3.3.  
+
Although Gramps is able to import '''''basic''''' genealogical data from GEDCOM through its GEDCOM Import module, much data commonly handled in modern Genealogical software can not be described while staying within the confines of the GEDCOM standard. So, GEDCOM Export from a Gramps Family Tree or Gramps XML is necessarily a '''lossy''' operation.  
 +
{{man tip|Gramps state of the GEDCOM art|
 +
[[Import_from_another_genealogy_program#Standard_GEDCOM_as_transfer_tool|GEDCOM has become the de facto standard]] for [https://wikipedia.org/wiki/Schema_crosswalk schema crosswalking] basic family history data between programs.<br/>Because [https://wikipedia.org/wiki/Dialect#Standard_and_nonstandard_dialects dialects] can arise for each program that writes GEDCOM files, we openly document where that additional layer of data loss occurs. But, since dialects cause incompatibilities in data exchange, we strive to avoid a "Gramps accented" dialect of GEDCOM.
  
The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.  
+
The 2018 revision of a blog article by Keith Riggle is a frank evaluation of GEDCOM dialect issues between [[Import_from_another_genealogy_program#Family_Tree_Maker|Gramps & Family Tree Maker]].}}
 +
This page attempts to list information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the broadest compatibility possible.  
  
The following assumes the standard GEDCOM export utility. However, there is also a set of common extensions that have been bundled together. See [[GEDCOM Extensions]] for more information.
+
{{man note|The Gramps version used as a reference for this page is|Gramps Trunk, which at the time was Gramps 3.3.(Released:2011-06-12)}}
 +
 
 +
The evolution of the GEDCOM standard stalled on 10 January 1996. There was a 1999 draft for a GEDCOM 5.5.1 version, which became the de facto standard but wasn't officially endorsed until November 2019. (The GEDCOM 7 specification was officially published in June 2021.)
 +
 
 +
Gramps uses several features of GEDCOM 5.5.1 as noted below.
 +
 
 +
The following assumes the 5.5.1 standard for the GEDCOM export utility. However, there is also a set of common extensions that have been bundled together as another dialect writable by Gramps. See [[GEDCOM Extensions]] for more information.
  
  
Line 18: Line 27:
 
* '''Parish''' Church Parish fields in Locations  
 
* '''Parish''' Church Parish fields in Locations  
 
* '''Media Attributes''': no equivalent in GEDCOM.
 
* '''Media Attributes''': no equivalent in GEDCOM.
* '''Source Data''': no equivalent in GEDCOM.
+
* '''Source Attributes (previously Data)''': no equivalent in GEDCOM.
* '''Source on places''': no equivalent in GEDCOM.
+
* '''Source and Date on places''': no equivalent in GEDCOM.
 
* '''Event Attributes different from age, father age, mother age, cause, agency'''. These other attributes have no equivalent in GEDCOM. AGNC and CAUS are exported from Agency and Cause attributes (respectively) of an event. AGE, HUSB:AGE and WIFE:AGE are exported from Age, Father's Age and Mother's Age (respectively) of an event reference. Hence these items of data should be stored in the appropriate place for export.
 
* '''Event Attributes different from age, father age, mother age, cause, agency'''. These other attributes have no equivalent in GEDCOM. AGNC and CAUS are exported from Agency and Cause attributes (respectively) of an event. AGE, HUSB:AGE and WIFE:AGE are exported from Age, Father's Age and Mother's Age (respectively) of an event reference. Hence these items of data should be stored in the appropriate place for export.
 
* '''Media Description''': set by user, no equivalent in GEDCOM.
 
* '''Media Description''': set by user, no equivalent in GEDCOM.
Line 25: Line 34:
 
* '''Tags''': an organizational tool for data analysis. This is not real genealogical data.
 
* '''Tags''': an organizational tool for data analysis. This is not real genealogical data.
 
* '''Shared Events''': will generate the same event for each record. On import Gramps tries to merge equal events.
 
* '''Shared Events''': will generate the same event for each record. On import Gramps tries to merge equal events.
 +
* '''Events order''': like for children, GEDCOM ignores events order.
 
* '''Shared Places in events''': GEDCOM does not know the concept of sharing places, so places are duplicated in the GEDCOM. On import, Gramps will automatically merge places with the ''same'' title and street, so this should be of no influence.
 
* '''Shared Places in events''': GEDCOM does not know the concept of sharing places, so places are duplicated in the GEDCOM. On import, Gramps will automatically merge places with the ''same'' title and street, so this should be of no influence.
 
* '''Call Name''': no equivalent in GEDCOM.
 
* '''Call Name''': no equivalent in GEDCOM.
Line 35: Line 45:
 
* '''Persian, Islamic, Swedish calendars'''
 
* '''Persian, Islamic, Swedish calendars'''
 
* '''Dual date and non 31/12 new year'''
 
* '''Dual date and non 31/12 new year'''
 +
* '''Independent event, source, citation, media, repository, note''': GEDCOM needs INDIvidual or FAMily as top level.
 +
 
* Some '''Gramps' Types''' (Note, Repository, Repository reference, etc ...)
 
* Some '''Gramps' Types''' (Note, Repository, Repository reference, etc ...)
 +
 +
* No GEDCOM data structure exists for the [[Hierarchical Place Structure|place hierarchy]] introduced in Gramps version 4.1.
 +
 +
* See also [[Lossless_GEDCOM_Export|Lossless Export]] and [[GEDCOM_Extensions|GEDCOM Extensions addon]].
  
 
== Information written in other form on GEDCOM export ==
 
== Information written in other form on GEDCOM export ==
* '''Compound surnames''': all name grouping info is present using comma-seperated lists. Using the ''Extract Information from Names'' tool, such a GEDCOM can be converted again in grouped names.
+
* '''Compound surnames''': all name grouping info is present using comma-separated lists. Using the ''[[Gramps_5.1_Wiki_Manual_-_Tools#Extract_Information_from_Names|Extract Information from Names]]'' tool, such a GEDCOM can be converted again in grouped names.
  
 
== Information available in GEDCOM 5.5.1 form ==
 
== Information available in GEDCOM 5.5.1 form ==
Line 46: Line 62:
 
== Information in GEDCOM 5.5 not in Gramps (lost on import) ==
 
== Information in GEDCOM 5.5 not in Gramps (lost on import) ==
  
{{man note|Gramps 4.1 GEDCOM Import|Details of GEDCOM import for Gramps 4.1 are provided in the [[Gramps_4.1_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Gramps 4.1 manual]], '''not here'''}}
+
{{man note|Gramps GEDCOM Import|Details of GEDCOM import for Gramps are already provided in the [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Gramps manual's Importing Data section]] and '''will not be repeated here'''.}}
  
Details for earlier versions of Gramps.
+
Details for earlier versions of Gramps 4.1
 
* Multimedia object in source citation
 
* Multimedia object in source citation
 
* EVENT_TYPE_CITED_FROM and ROLE_IN_EVENT in source citation
 
* EVENT_TYPE_CITED_FROM and ROLE_IN_EVENT in source citation
 +
 +
== See also ==
 +
* [[GEPS 037: Support GEDCOM X]] - a proposal to support the GEDCOM X file format
 +
* [[GEDCOM 7 support]]
 +
* [[GEDCOM]]
 +
* [[Lossless GEDCOM Export]]
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Latest revision as of 10:11, 21 July 2021

Gramps uses Gramps XML, which is a less confining format than standard GEDCOM.

Although Gramps is able to import basic genealogical data from GEDCOM through its GEDCOM Import module, much data commonly handled in modern Genealogical software can not be described while staying within the confines of the GEDCOM standard. So, GEDCOM Export from a Gramps Family Tree or Gramps XML is necessarily a lossy operation.

Tango-Dialog-information.png
Gramps state of the GEDCOM art

GEDCOM has become the de facto standard for schema crosswalking basic family history data between programs.
Because dialects can arise for each program that writes GEDCOM files, we openly document where that additional layer of data loss occurs. But, since dialects cause incompatibilities in data exchange, we strive to avoid a "Gramps accented" dialect of GEDCOM.

The 2018 revision of a blog article by Keith Riggle is a frank evaluation of GEDCOM dialect issues between Gramps & Family Tree Maker.

This page attempts to list information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the broadest compatibility possible.

Gramps-notes.png
The Gramps version used as a reference for this page is

Gramps Trunk, which at the time was Gramps 3.3.(Released:2011-06-12)

The evolution of the GEDCOM standard stalled on 10 January 1996. There was a 1999 draft for a GEDCOM 5.5.1 version, which became the de facto standard but wasn't officially endorsed until November 2019. (The GEDCOM 7 specification was officially published in June 2021.)

Gramps uses several features of GEDCOM 5.5.1 as noted below.

The following assumes the 5.5.1 standard for the GEDCOM export utility. However, there is also a set of common extensions that have been bundled together as another dialect writable by Gramps. See GEDCOM Extensions for more information.


Lost information on a GEDCOM export from Gramps

  • Bookmarks
  • Preformatted flag on notes
  • Markup in notes. Most other genealogy programs have markup in notes, but GEDCOM has no support.
  • Roles on events
  • One gender on same sex relation: GEDCOM does not support same sex relation.
  • Children status: GEDCOM only uses child-family relationships, ex: adoption as event not a relation.
  • County County fields in Locations
  • Parish Church Parish fields in Locations
  • Media Attributes: no equivalent in GEDCOM.
  • Source Attributes (previously Data): no equivalent in GEDCOM.
  • Source and Date on places: no equivalent in GEDCOM.
  • Event Attributes different from age, father age, mother age, cause, agency. These other attributes have no equivalent in GEDCOM. AGNC and CAUS are exported from Agency and Cause attributes (respectively) of an event. AGE, HUSB:AGE and WIFE:AGE are exported from Age, Father's Age and Mother's Age (respectively) of an event reference. Hence these items of data should be stored in the appropriate place for export.
  • Media Description: set by user, no equivalent in GEDCOM.
  • Reference region of a media reference.
  • Tags: an organizational tool for data analysis. This is not real genealogical data.
  • Shared Events: will generate the same event for each record. On import Gramps tries to merge equal events.
  • Events order: like for children, GEDCOM ignores events order.
  • Shared Places in events: GEDCOM does not know the concept of sharing places, so places are duplicated in the GEDCOM. On import, Gramps will automatically merge places with the same title and street, so this should be of no influence.
  • Call Name: no equivalent in GEDCOM.
  • Family Nickname: no equivalent in GEDCOM. Use an alternate name.
  • Date on Name
  • Group names: Used by Gramps for sorting.
  • Sort As on names: Used by Gramps for sorting.
  • Alternate Locations: This full data on alternate locations is not exported as GEDCOM has no support for this.
  • Private objects
  • Persian, Islamic, Swedish calendars
  • Dual date and non 31/12 new year
  • Independent event, source, citation, media, repository, note: GEDCOM needs INDIvidual or FAMily as top level.
  • Some Gramps' Types (Note, Repository, Repository reference, etc ...)
  • No GEDCOM data structure exists for the place hierarchy introduced in Gramps version 4.1.

Information written in other form on GEDCOM export

  • Compound surnames: all name grouping info is present using comma-separated lists. Using the Extract Information from Names tool, such a GEDCOM can be converted again in grouped names.

Information available in GEDCOM 5.5.1 form

  • Coordinates: Latitude and Longitude use MAP.LONG and MAP.LATI fields of GEDCOM 5.5.1
  • Custom attributes on Person, Family: FACT tag is used of GEDCOM 5.5.1

Information in GEDCOM 5.5 not in Gramps (lost on import)

Gramps-notes.png
Gramps GEDCOM Import

Details of GEDCOM import for Gramps are already provided in the Gramps manual's Importing Data section and will not be repeated here.

Details for earlier versions of Gramps 4.1

  • Multimedia object in source citation
  • EVENT_TYPE_CITED_FROM and ROLE_IN_EVENT in source citation

See also