Re: Place Names Changing Over Time
toggle quoted messageShow quoted text
Every place has a Standardized field. From the Help file:
“Auto-geocoding (see the Map Window to learn more about geocoding) is normally based on the Place field (see previous). However, if the Standardized field is not blank, geocoding will be based on it instead. Some historical names may not be recognised, or may be incorrectly geocoded. In this situation, you can either simply specify the correct latitude and longitude yourself; or you can supply a modern, standardized name which will be correctly geocoded.”
From: email@example.com <firstname.lastname@example.org> On Behalf Of rcook@...
Sent: 04 March 2021 23:50
Subject: [family-historian] Place Names Changing Over Time
In many cases, place names in source documents change over time. In many cases, I have started out with one place name, only to change at a later time.
Example: Scott Twp., Ontario Co., Ontario, Canada is now Durham Region, Ontario, Canada as of January 1, 1974.
As well, many of the townships have been changed, amalgamated or dropped.
I have reviewed the guidance in https://fhug.org.uk/kb/kb-article/working-with-places-and-addresses-for-new-users/ But geocoding may be problematic.
What do other FH7 users do to accommodate changing place names?