Jump to: navigation, search

Gramps and GEDCOM

1,860 bytes added, 10:11, 21 July 2021
Revise for the advent of official publications of the 5.5.1 and 7 standards
{{out of date|as per enno on mailing list 20150707}}Gramps uses [[Gramps XML]], which is a less confining format than '''''standard''''' [[GEDCOM]].
Although Gramps uses [[Gramps XML]] which is considered a superior format to [[GEDCOM]] by the Gramps developers. Although Gramps should be able to import most '''''basic''''' genealogical data from GEDCOM through its GEDCOM Import module, many much data commonly handled in modern Genealogical software can not be described while staying within the confines of the Gramps features are not supported by the GEDCOM standard and so . So, GEDCOM Export from a Gramps Family Tree or Gramps XML is necessarily a '''lossy ''' operation. This page shall list all {{man tip|Gramps state of the information GEDCOM art|[[Import_from_another_genealogy_program#Standard_GEDCOM_as_transfer_tool|GEDCOM has become the de facto standard]] for [ schema crosswalking] basic family history data between programs.<br/>Because [ dialects] can arise for each program that is lost on a writes GEDCOM export from Grampsfiles, so we openly document where that users may choose additional layer of data loss occurs. But, since dialects cause incompatibilities in data exchange, we strive to restrain their Gramps use to those features that GEDCOM can handle. avoid a "Gramps recognizes the relevance accented" dialect 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.
The 2018 revision of a blog article by Keith Riggle is a frank evaluation of GEDCOM standard stopped evolving on 10 January 1996dialect issues between [[Import_from_another_genealogy_program#Family_Tree_Maker|Gramps & Family Tree Maker]]. There }}This page attempts to list information that is lost on a draft for a 5.5.1 versionGEDCOM export from Gramps, of which so that users may choose to restrain their Gramps uses several use to those features as noted belowthat GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the broadest compatibility possible.
{{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 togetheras another dialect writable by Gramps. See [[GEDCOM Extensions]] for more information.
* '''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.
* '''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.
* '''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 [[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 ==
* '''Compound surnames''': all name grouping info is present using comma-seperated 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 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 already provided in the [[Gramps_4Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Gramps 4.1 manual's Importing Data section]], and '''will not be repeated here'''.}}
Details for earlier versions of Gramps4.1
* Multimedia object 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]]

Navigation menu