Difference between revisions of "Gramps and GEDCOM"

From Gramps
Jump to: navigation, search
(Lost information on a GEDCOM export from Gramps)
m (no alternate stand-alone primary objects as INDI and FAM)
Line 45: 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, no alternate stand-alone primary records.
* '''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 ...)

Revision as of 14:24, 18 October 2019


This article's content is incomplete or a placeholder stub.
Please update or expand this section.

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.

Gramps state of the GEDCOM art

GEDCOM has become the de facto standard for schema crosswalking family history data between programs. Because dialects arise for each program that writes GEDCOM files, we openly document where that additional layer of data loss occurs.

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 best compatibility possible.

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 GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a GEDCOM 5.5.1 version, of which Gramps uses several features as noted below.

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.

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 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 GEDCOM Import

Details of GEDCOM import for Gramps are provided in the Gramps manual, not 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