Changes

Jump to: navigation, search

Gramps and GEDCOM

5,136 bytes added, 22:32, 7 December 2023
m
Lost information on a GEDCOM export from Gramps: reword to indicate that the Sharing consolidation is lost, not the item that was referenced.
The native data exchange format for Gramps uses is [[GRAMPS_XML|Gramps XML]] which is considered , a superior format to structured [[GEDCOMGramps_Glossary#xml|XML]] by text format which supports ALL the Gramps developers. Although Gramps should Genealogical data that can be able to import most data from GEDCOM through its GEDCOM Import module, many of stored in the Gramps features are not supported by the GEDCOM standard and so GEDCOM Export from a Gramps Family Tree or Gramps working relational database file. XML is a lossy operation. This page shall list all more expansive format than the information that is lost on a sluggishly evolving [[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, currently 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|Since 1999, [[Import_from_another_genealogy_program#Standard_GEDCOM_as_transfer_tool|GEDCOM v5.5.1 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. In May 2021, a GEDCOM 7.0 version was announced. But as of September 2022, adoption is very limited with only 2 software tools reporting partial support. (See for updated [https://www.familysearch.org/en/GEDCOM/implementation-progress register of support for GEDCOM 7]) So, the 5.5.1 version remains the most widely compatible data exchange format for genealogical data.}} 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.  {{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 stopped evolving stalled on 10 January 1996. There is was a 1999 draft for a GEDCOM 5.5.1 version, of 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 [[Addon:GEDCOM Extensions]] for more information.
__TOC__
== Lost information on a GEDCOM export from Gramps ==
Some advanced information has no equivalent in the 5.5.1 GEDCOM format. Some data can partially handled in a less capable GEDCOM data element. Gramps family tree XML format (.gramps or .gpkg archive) is the recommended lossless data exchange format.
 
Here are the data nuances that do not downgrade cleanly into GEDCOM and will be lost during export:
 
* '''Bookmarks'''
* '''Preformatted flag on notes'''
* '''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.
* '''Events consolidation via Shared Eventsreferences''': 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.* '''Places consolidation via Shared Places references 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.
* '''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 [[Addon: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 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 4.1
* Multimedia object in source citation
* EVENT_TYPE_CITED_FROM and ROLE_IN_EVENT in source citation  == See also ==* Riggle, Keith. "[httphttps://wwwgenealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-project4/ Family Tree Software Alternatives, part 8]" ''(extensively revised for Gramps 5.0)''. [https://genealogytools.com/ Genealogy Tools] blog, 8 Aug 2018. <small>(cited in this wiki's [[Import_from_another_genealogy_program#Family_Tree_Maker|Family Tree Maker]] article)</small>* Riggle, Keith.org"[https:/bugs/viewgenealogytools.php?id=2918com/family-tree-maker-to-gedcom-to-other-apps-crosswalk/ Family Tree Maker to Gedcom To Other Apps Crosswalk]". [https://genealogytools.com/ Genealogy Tools] blog, 4 Apr 2022. <small>(extensive GEDCOM tag checklist spreadsheet)</small>* [[Import_from_another_genealogy_program|GEDCOM dialects when importing from another program]]* [[GEPS 037: Support GEDCOM X]] - a proposal to support the GEDCOM X file format* [[GEDCOM 7 support]]* [[GEDCOM]]* [[Lossless GEDCOM Export]]* Discourse forum article: "[https://gramps.discourse.group/t/funny-codes-in-notes-on-published-gedcom/2590 Funny codes in notes on published GEDCOM]" (Some exported Note types not recognized for [https://www.tribalpages.com/about.html Tribal Pages] website generation.)* Jones, Tamura. "'''[https://www.tamurajones.net/AGentleIntroductionToGEDCOM.xhtml A Gentle Introduction to GEDCOM]'''" ''Modern Software Experience'', 24 Aug 2010, [https://www.tamurajones.net/AGentleIntroductionToGEDCOM.xhtml https://www.tamurajones.net/AGentleIntroductionToGEDCOM.xhtml]. * Cardinal, John. "GEDCOM Assessment v1.05" [httphttps://www.gedcomassessment.com/en/assessment-gramps-project5.orghtm evaluating GEDCOM v5.5.1 import using Gramps AIO64-5.1.2-1] with the " [https:/bugs/viewwww.gedcomassessment.php?id=2924com/en/index.htm assess.ged] v1.05" test file, 7 Mar 2020 (GEDCOM Assessment [https://www.gedcomassessment.com/en/changelog.htm change log]) 
[[Category:Documentation]]
4,608
edits

Navigation menu