# GEDCOM import shortcomings - no documentation?
**URL:** https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358
**Category:** Help
**Tags:** gedcom
**Created:** [November 1, 2023, 11:21am UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358 "2023-11-01T11:21:35Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@hartenthaler](https://gramps.discourse.group/u/hartenthaler)
#### Post date: [November 1, 2023, 11:21am UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/1 "2023-11-01T11:21:35Z")
Is there any document describing the GEDCOM tags that are **not** imported into Gramps?
I found in the wiki a description of the elements that are not exported, but no information about the other direction.
My findings up to now:
- one side date ranges are not imported correctly (ie n DATE FROM 1 JAN 1900; or n DATE TO 1 JAN 1900)
- media objects OBJE with more than one media files (what I’m using very often to store the front and back side of a postcard, to store several pages of a document, or an audio interview together with the transcribed text)
BTW the description of not exported elements shows a incomplete understanding of the GEDCOM standards. I’m a new and unexperienced user of Gramps so I’m not sure if I should modify the wiki. Maybe it is better to comment in Discourse?
---
### Author:  [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)
#### Post date: [November 1, 2023, 11:39am UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/2 "2023-11-01T11:39:52Z")
I am not aware of any such document.
Please feel free to add this list to our wiki documentation.
---
### Author:  [@hartenthaler](https://gramps.discourse.group/u/hartenthaler)
#### Post date: [November 1, 2023, 12:21pm UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/3 "2023-11-01T12:21:32Z")
The only reference I found: [Gramps and GEDCOM - Gramps](https://gramps-project.org/wiki/index.php/Gramps_and_GEDCOM)
---
### Author:  [@emyoulation](https://gramps.discourse.group/u/emyoulation)
#### Post date: [November 1, 2023, 1:28pm UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/4 "2023-11-01T13:28:54Z")
In the “see also” section of that page, there is a very exacting assessment of Gramps’ quality and shortfalls with standard 5.5.1 GEDCOM imports:
> - Cardinal, John. “GEDCOM Assessment v1.05” [evaluating GEDCOM v5.5.1 import using Gramps AIO64-5.1.2-1](https://www.gedcomassessment.com/en/assessment-gramps-5.htm) with the " [assess.ged](https://www.gedcomassessment.com/en/index.htm) v1.05" test file, 7 Mar 2020 (GEDCOM Assessment [change log](https://www.gedcomassessment.com/en/changelog.htm))
There’s also a thread about other 3rd party reviews of the Gramps GEDCOM implementation:
> [@3rd party reviews of Gramps GEDCOM import](https://gramps.discourse.group/t/3rd-party-reviews-of-gramps-gedcom-import/3954):
>
> Was looking for something else but found a tag-by-tag assessment of Gramps’ GEDCOM 5.5.1 import. Thought I’d post it (and a couple previous ones) here for future reference. In GEDasssement dot com’s [summary](https://www.gedcomassessment.com/en/comparison-gp.htm), counts ranged from tools correctly handling 121 tags to 229 tags. Gramps was 4th at 187 tags handled “correctly” by their standards. Cardinal, John. “GEDCOM Assessment v1.05” [evaluating GEDCOM v5.5.1 import using Gramps AIO64-5.1.2-1](https://www.gedcomassessment.com/en/assessment-gramps-5.htm) with the " [assess.ged](https://www.gedcomassessment.com/en/index.htm) v1.05" test file, 7 Mar 2020 Rig…
---
### Author:  [@emyoulation](https://gramps.discourse.group/u/emyoulation)
#### Post date: [November 1, 2023, 3:04pm UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/5 "2023-11-01T15:04:20Z")
> [@hartenthaler](#):
>
> one side date ranges are not imported correctly (ie n DATE FROM 1 JAN 1900; or n DATE TO 1 JAN 1900)
Support open ended dates (such “from” and “to” dates) will be new for Gramps 5.2 version. But the 5.2 GEDCOM import has not been revised to support them yet. So those dates will be imported as a text string.
There are some other date format that import as Text. So there’s a supertool script (described in [another thread](https://gramps.discourse.group/t/making-date-input-more-flexible/2814/4)) for pushing “invalid dates” back through the Gramps date validation function. Running that script once 5.2 is released should fix those.
---
### Author:  [@hartenthaler](https://gramps.discourse.group/u/hartenthaler)
#### Post date: [November 1, 2023, 5:29pm UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/6 "2023-11-01T17:29:03Z")
The report of John Cardinal was very helpful. Thank you for the link!
---
### Author:  [@system](https://gramps.discourse.group/u/system)
#### Post date: [December 1, 2023, 5:29pm UTC](https://gramps.discourse.group/t/gedcom-import-shortcomings-no-documentation/4358/7 "2023-12-01T17:29:14Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.