Import Geocom file from iHeritage

[searchr151]

My sister and I share data but her exports from iHeritage are grayed out as an option to import into iFamily is this an incodeing issue? I can opinion a text editor and see the data.

[Warwick Wilson]

The greying out is simply a filter for the filenames that end in the extension *.GED, (or possibly *.ged).

Can you let us know what your file name is? Perhaps you need to rename it? I encountered a MyHeritage file recently that had an unknown encoding stamp at the start which was preventing import. (The first three binary characters of the file before the "0 HEAD" refer to the encoding used. iFamily is expecting UTF8 but can manage most other formats also.).

I am also happy to have a look and try and load it from my end, just email it to support@ifamilyformac.com, or send a link to Dropbox or iCloud if it is too big to email.

[maleger]

I'm having the same problem. I'm looking to import a family site from My Heritage and am getting this same message about encoding (UTF-8) but when I open the ged file in a text editor it mentions utf-8 as the encoding. I'm using iFamily for Mac 2.12.0 with a M1 Mac mini on MacOS 12.0.1 (Monterey).

[Warwick Wilson]

I'm having the same problem. I'm looking to import a family site from My Heritage and am getting this same message about encoding (UTF-8) but when I open the ged file in a text editor it mentions utf-8 as the encoding. I'm using iFamily for Mac 2.12.0 with a M1 Mac mini on MacOS 12.0.1 (Monterey).

Please email the file to support@ifamilyformac.com and I'll try and import it at this end.

[maleger]

Thank you, I sent you the file.

Please email the file to support@ifamilyformac.com and I'll try and import it at this end.

[Warwick Wilson]

Thank you, I sent you the file.

The cause of the problem here is that iFamily is reading the gedcom file a line at a time and encoding the characters as they come.

The line continuations from MyHeritage gedcom export, are emplacing half of the ecoute and grave characters on each CONT line, it is splitting them.

When I loaded the gedcom, it logged where the errors were, being one line greater than the following 122 lines:

[127, 347, 1110, 1326, 1380, 1806, 3032, 3323, 4353, 4554, 5318, 5653, 5786, 6402, 6403, 7893, 8766, 9209, 9501, 9502, 9753, 12517, 13076, 13237, 14594, 18495, 19250, 20258, 22348, 22754, 23080, 23943, 23946, 24315, 24604, 24986, 25303, 25306, 26034, 28433, 28566, 28887, 29488, 30626, 30727, 31602, 31781, 34602, 34696, 34796, 35174, 35503, 36070, 36775, 37280, 37504, 38218, 41859, 44287, 45230, 48693, 49272, 49487, 49584, 49623, 51854, 51937, 51983, 56949, 56955, 60401, 62196, 63901, 64810, 66190, 68882, 70083, 70506, 70674, 71014, 75371, 75557, 75932, 78102, 79451, 83531, 85331, 85455, 86410, 87090, 87147, 87562, 89248, 89586, 90991, 92306, 92358, 95712, 96905, 99150, 101524, 104915, 106046, 106648, 106911, 107089, 110070, 111335, 111466, 112810, 114977, 115018, 120576, 123579, 126120, 130583, 131418, 133980, 135251, 138495]

The first 4 of which map as:

127: Ending line 128 You will find Ã, starting line 129 you will find ©
347: Ending line 361 You will find Ã, starting line 362 you will find ©
1110: Ending line 1124 You will find Ã, starting line 1125 you will find ©
1326: Ending line 1340 You will find Ã, starting line 1341 you will find ´

As you can see it is unfortunate that my line reports are getting further off the further into the file we go. off by 14 after 4 entries, but it conveniently remains off by 14 until the very end of the gedcom.

To clean the file:

1. Copy the file into your iFamilyData folder, as a woking copy (save the original elsewhere.).
2. Open terminal
3. type "vi ~/iFamilyData/e70p61_72456957k6ewag1y5e6179_A.ged"
4. type a number followed by SHIFT-G to go to a line number.
5. cursor over the offending chars and use "x" to delete the offending characters that follow the above pattern. Ã from the end of one line and its pairing from the start of the next.
6. Repeat 122 times
7. Import the file, If it still doesn't load, email the revised copy to me and I will test it once more to find what's left.

I will be able to code around this in the next release, whenever we get that, but it will be quicker for you to do the cleaning for the moment and get the result you need. even If missing 122 characters.

[maleger]

I'm going to see if I can use an editor, like ATOM that I use for writing code and do a search and replace of the characters. This may be quicker. Another option might be to write some Python code.

[maleger]

Thank you, based on this information I was able to edit the file with Atom and was then able to load it into iFamiliy for Mac. Problem solved!

[Warwick Wilson]

Yay. Also thanks -> I have installed Atom.