3 ms·
Genealogy applications run into this a lot. The person of interest lived at Engeset. FamilySearch has geocoded a place called "Engeset, Møre og Romsdal, Norway"
by vintermann 2y ago
Genealogy applications run into this a lot. The person of interest lived at Engeset. FamilySearch has geocoded a place called "Engeset, Møre og Romsdal, Norway". So that's it, right? Not so fast, [there are at least 3 Engesets in Møre og Romsdal](https://www.google.com/maps/search/Engeset/@62.3358577,6.2251463,132438m/data=!3m2!1e3!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMy4wIKXMDSoASAFQAw%3D%3D https://www.google.com/maps/search/Engeset/@62.3358577,6.225...).
But that's at least better than when it's some local place name which it's never heard of, and thinks sounds most similar to a place in Afghanistan (this happens all the time).
And to add to it, there are administrative regions, and ecclesiastical regions. Do you put them in the parish, or in the municipality? The birth in the parish and the baptism in the municipality, maybe? How about the burial then...
- modeless 2y agoConverting from a name/address to coordinates is geocoding. Reverse geocoding is mapping from coordinates to a name/address.
- vintermann 1y agoWell you need both. For instance to know that "Hauan" is likely a small named place near to the other named places this person is associated with, and not the name similar to it in Afghanistan. Any time there's any ambiguity about a name, you need the reverse too, to resolve it.