* Problem with Place export to TNG

[bgriffiths]

Hi All
I have recently rearranged the 2000+ places in my gedcom from 5 field, left justified, no padding to 5 field, right justified with padding.

I have the Export Gedcom plugin set to TNG, all options default except for media, set to WIPE. Looking at the resulting gedcom it seems to have converted all the places in events to left justified, no padding, and created the _PLAC record as in the original file. (If I run a place report on the output file it now shows nearly 2x the number of places (allowing for places which have all 5 fields populated ) eg:

0 @I3@ INDI
1 NOTE @N1807@
1 NAME Brian Charles /Griffiths/
1 SEX M
1 BIRT
2 DATE 30 JUL 954
2 PLAC Liverpool, Lancashire, England
1 FAMC @F1@
1 FAMS @F3@
1 CHAN
2 DATE 2 DEC 2015
3 TIME 17:37:31


0 _PLAC , , Liverpool, Lancashire, England
1 MAP
2 LATI N53.4127033
2 LONG W2.9606608
1 CHAN
2 DATE 2 DEC 2015
3 TIME 17:37:31

Result is when I run the import I end up with all the events with no geocoding, and all the geocoded places with no events, and a places table with 4000+ records

Original input file has all events with the fully padded PLAC record:

0 @I3@ INDI
1 NAME Brian Charles /Griffiths/
1 SEX M
1 BIRT
2 DATE 30 JUL 1954
2 PLAC , , Liverpool, Lancashire, England
1 FAMC @F1@
1 FAMS @F3@
1 CHAN
2 DATE 2 DEC 2015
3 TIME 17:37:31

Where am I going wrong?

[tatewise]

Sorry, that is a bug in the Plugin that only appears when you have any blank parts in Place names.

It should NOT be Tidying those Place names for TNG.

That will be fixed in the next Plugin Store version, but a prototype fixed version will be ATTACHED to Export Gedcom File Plugin/Media notes and privacy (13066) soon.

BTW: Open an exported Gedcom in FH does not necessarily behave well, because the dialect of Gedcom is specifically designed for the other product and my be incompatible with FH.

[bgriffiths]

That will be fixed in the next Plugin Store version, but a prototype fixed version will be ATTACHED to Export Gedcom File Plugin/Media notes and privacy (13066) soon.

Thanks Mike - that seems to have fixed it
Brian