* V7 Importing places - Latitude / Longitude

Importing from another genealogy program? This is the place to ask. Questions about Exporting should go in the Exporting sub-forum of the General Usage forum.
Post Reply
avatar
arneko
Gold
Posts: 15
Joined: 25 Oct 2018 16:49
Family Historian: V7
Location: Norway

V7 Importing places - Latitude / Longitude

Post by arneko » 22 Dec 2020 22:39

I have installed V7 and import my TMG 9.5 database into a new FH v7 base.
But most of my places that have LAT/LONG value, will not put the value in the LAT/LONG field.

What can be done to move the value into the LAT/LONG field.

User avatar
tatewise
Megastar
Posts: 27077
Joined: 25 May 2010 11:00
Family Historian: V7
Location: Torbay, Devon, UK
Contact:

Re: V7 Importing places - Latitude / Longitude

Post by tatewise » 22 Dec 2020 23:01

I imagine the Lat/Longitude values are embedded in the Place fields and so FH does not see them as formal MAP data.

See the end of the posting FH TMG Direct import issues following V6.0.1 (12162) that offers a plugin to Copy LatLong in Name to LatLong BUT it had not been updated to FH v7.0 yet; however it only needed a small change so is attached below. Do take a Project Backup before use, just in case!!!!
[ EDIT: Attachment deleted as superseded later. ]

Does it seem to meet your needs?

BTW: As well as the KB Importing to Family Historian advice with specific details for TMG there is also the Compendium of Conversion Plugins which includes a reference to the above posting.
I apologize for those two topics not being cross-referenced in the new KB yet but everything is in state of flux with FH v7.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

avatar
arneko
Gold
Posts: 15
Joined: 25 Oct 2018 16:49
Family Historian: V7
Location: Norway

Re: V7 Importing places - Latitude / Longitude

Post by arneko » 25 Dec 2020 21:12

Helo Mike.

I tried the new version but it did not work. It is telling me "No place record found with LatLong in Name"

But when I am run the plugin with debugging, I see many examples on place with LAT/LONG at the end.

Here is an example of the debugging.

strMagic local "[%^%$%(%)%%%.%[%]%*%+%-%?])"
prtText item local Text: , Skånevik,, Etne, Hordaland, Norge,,, 59.73286911;5.93283176
strText local "Skånevik,, Etne, Hordaland, Norge,,, 59.73286911;5.93283176"
strLat local (nil)
strLong local (nil)
_ENV upvalue (table .137)
DEBUG_MODE global true
ptrPlac item global Place: , Skånevik,, Etne, Hordaland, Norge,,, 59.73286911;5.93283176


So whats is not working

avatar
arneko
Gold
Posts: 15
Joined: 25 Oct 2018 16:49
Family Historian: V7
Location: Norway

Re: V7 Importing places - Latitude / Longitude

Post by arneko » 25 Dec 2020 22:34

I cheked out the place name in the TMG database and there the LAT/LONG field is posted as this \59.73286911,5.93283176

So when FH is importing in the LAT/LONG it is translated to 59.73286911;5.93283176, and this make a mismatch to use the copy Lat/Long plugin which is expeting comma insted for semi colon.

I hope something could be done with the import function in FH to correct this problem.

User avatar
tatewise
Megastar
Posts: 27077
Joined: 25 May 2010 11:00
Family Historian: V7
Location: Torbay, Devon, UK
Contact:

Re: V7 Importing places - Latitude / Longitude

Post by tatewise » 26 Dec 2020 12:13

Thank you for the feedback.
It is such minor variations in format that upset the Plugin.
The previous posting had a comma separator and yours has a semicolon separator.

I have revised the Plugin to cater for any punctuation symbol ( , ; : ) as the separator.
Try the attached version.
Attachments
Copy LatLong in Name to LatLong.fh_lua
Version 1.1.1 Date 26 Dec 2020
(1.84 KiB) Downloaded 127 times
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

avatar
arneko
Gold
Posts: 15
Joined: 25 Oct 2018 16:49
Family Historian: V7
Location: Norway

Re: V7 Importing places - Latitude / Longitude

Post by arneko » 26 Dec 2020 22:14

Hello again.

I tested the new version, and it work nearly OK.
The LAT/LONG was moved to the correct field, but the place name have in the end \, this was not removed.

ex:
, Skånevik,, Etne, Hordaland, Norge,,, \59.73286911,5.93283176 was looking like this
, Skånevik,, Etne, Hordaland, Norge,,, \ after moving the LAT/LONG to the LAT/LONG field.

I used search and replace to removed the \, but it would be fine that the plugin could fix it.

Post Reply