Importing GEDCOM from "Family Tree 9"

Help
1

People,

I just installed:

gramps-5.1.4-2.fc34.noarch (ie Fedora Linux)

My brother has produced a GEDCOM file from “Family Tree 9” - it does actually import some data by get 7504 errors reported like:

Line ignored as not understood                                      Line    18: 2 SECG Stuart
Tag recognized but not supported                                    Line    22: 2 CHAN 
Skipped subordinate line                                            Line    23: 3 DATE 2021-12-11
Skipped subordinate line                                            Line    24: 4 TIME 17:39:21

Line ignored as not understood                                      Line    25: 2 _CRE 
Skipped subordinate line                                            Line    26: 3 DATE 2021-12-11
Skipped subordinate line                                            Line    27: 4 TIME 17:39:08

In the GEDCOM file I used Vim to change all the “<0d>” bytes to LFs and tried again with the same result.

I realise there are idiosycrasies in GEDCOM files so I am not greatly surprised but being able to do a clean import would be very nice!

Thanks,
Phil.
Is there already a fix for these problems?

2

Do you mean Legacy Family Tree 9 https://legacyfamilytree.com/ ?

The GEDCOM errors you show are not actually errors but warnings that Gramps does not know what to do with the custom GEDCOM tag (typically start with an underscore) for example: Line 25 shows _CRE which is not a standard GEDCOM tag and Legacy’s list ( Last Updated: 2014-08-12) does not show it or how to interpret it?

Same goes for the earlier tag with no underline SECG which is not a standard GEDCOM tag and according to this article

Exported the following standard fields incorrectly:
…
Middle Name (Second Given Name) used tag SECG instead of GIVN (thanks to reader Peter McGregor for pointing this out).

So basically it depends on the program creating the GEDCOM to document how the custom GEDCOM should be interpreted, are you able to contact the company and ask?

3

@Patsyblefebre ,

Thanks for the super-fast response!

Right.

Not really - it is a paid-for app that my brother is using on an iPad (I am a Linux person) - I just sent him a note on Telegram asking him if there is an XML export option to see if that is any more enlightening . .

I guess if I can work out what the wayward tags are for I could produce a little script to convert them to something sensible . .

4

When you load the GEDCOM, in an editor that shows line numbers, you can see the context, and I bet that the _CRE refers to the creation time of an object. And I say that, because it appears to be in the same context as the CHAN line, which gives the time of the last change, but seems to appear in a non standard place.

7

It looks like the issue is related to non-standard GEDCOM tags rather than a problem with Gramps itself. If you open the GEDCOM file in a text editor that displays line numbers, check the lines where the errors are reported. The _CRE tag is most likely a custom field added by Family Tree 9, probably to store the record creation date or time. Since _CRE is not part of the standard GEDCOM specification, Gramps may flag it during import. In most cases, these warnings can be ignored if the imported data appears complete, or you can remove the unsupported custom tags before importing if they are not needed.