Importing GEDCOM Files into Ancestry.com Using Gramps

As an enthusiastic genealogist, you may have encountered issues while attempting to import your GEDCOM file from Family Tree Maker (FTM) or another app/website into Gramps. Despite some progress in correcting problems with GEDCOM import and export, several challenges remain. This article aims to provide valuable insights and solutions for overcoming common obstacles.

Gramps Version Tested

The information presented in this article is based on Gramps 5.0.0. For detailed guidance on GEDCOM import, please refer to the Wiki Manual article, 'Manage Family Trees.' Additionally, you can find instructions on importing a GEDCOM file from another genealogy program on the Gramps Wiki page, 'Import from another genealogy program.'

Gramps and GEDCOM 5.5 Support

Gramps supposedly supports GEDCOM 5.5, with limited support for version 5.5.1. Have you tried using these versions? If not, it's worth exploring their capabilities.

Encoding Issues

When importing a GEDCOM file, encoding can become a significant hurdle. For instance, you may encounter issues with CHAR ANSI or UTF-8. To resolve this, try replacing CHAR ANSI with CHAR UTF-8. In the error log you provided, I notice that LidkÃ¶ping is displayed instead of Lidköping, suggesting that the encoding is likely UTF-8. However, it's essential to remember that this can be misleading due to processing steps.

Character Set Analysis

To better understand the character set used in your GEDCOM file, you can employ tools like od or an editor that doesn't interpret characters on its own. In UTF-8, a name like Göteborg is encoded into two bytes with decimal values 195 and 182. If the file format is cp1252 or ISO-8859, the same name would be 8 bytes long, with the ö coded as a single byte having decimal value 246.

Corrections and Workarounds

To correct encoding issues, you can:

1. Use an octal dump of the file with the od command to determine what characters are actually present.

2. Let the file command figure out what the file contents are.

3. Specify the character set used in your GEDCOM file.

Editor Assumptions and Character Sets

When loading a text file into an editor, that editor makes assumptions about the character set. If these assumptions are incorrect, you may not see the correct characters, even if they're present in the file. This highlights the importance of understanding character sets when working with GEDCOM files.

GEDCOM Import Errors and Solutions

If you encounter errors during import, such as DEL or C1 control chars in line, you can try specifying CHAR cp1252 to resolve the issue.

UTF-8 Export and GRAMPS Preferences

When exporting your GEDCOM file from TNG 14.0.1, ensure that you change 'Encoding ANSI' to 'Encoding UTF-8.' This should help resolve character set issues during import into Gramps.

Media Path Settings in GRAMPS

In GRAMPS, navigate to Edit/Preferences/General/Base path for relative media paths to specify the folder where your images are stored. Make sure that there is only one reference with FILE in it, pointing at your GEDCOM file.

By following these guidelines and troubleshooting steps, you should be able to successfully import your GEDCOM file into Gramps, ensuring a seamless transition of your genealogical data.

Gramps import gedcom in ansel