What I'd like to see is the ability to link locations, and have dates associated with locations. That way, you can have the progression of a location throughout history easily visible. If you have the location listed one way, but put in a date where it should have a different 'name' at that time, Legacy could recognize it due to the linked dated locations and then auto-correct.
By historical progression, for example Bethabara, Rowan County, North Carolina Colony, British North America is where some of my ancestors lived in the 1750's (and beyond). That same location is now within the city of Winston-Salem, Forsyth County, North Carolina, United States. Every level of jurisdiction has changed (if only because state level changed from colony to state) - and more than once on the county level. The following are all the same location, in a historical progression: 1753-1771 - Bethabara, Rowan County, North Carolina Colony, British North America 1771-1776 - Salem, Surry County, North Carolina Colony, British North America [they actually built a new town nearby, and all villagers moved there. The county coincidentally changed in the same year.] 1776-1789 - Salem, Surry County, North Carolina, United States 1789-1849 - Salem, Stokes County, North Carolina, United States 1849-1913 - Salem, Forsyth County, North Carolina, United States 1913-today - Winston-Salem, Forsyth County, North Carolina, United States This is not to say I expect the Legacy team to expand the Geo Locations to include all historical names. Rather, I'd like the locations expanded to include dates that users can add, and then the ability to link them. Getting historical accuracy could be helped with forums or Facebook queries if a person is stuck and cannot find an answer online (which is where I look). Thank you, Trevor Carlson Edmonton, AB From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Jane Linkswiler Sent: 12-Apr-17 7:47 PM To: 'Legacy User Group' Subject: Re: [LegacyUG] Place names - olde vs current Sounds like a great idea for the suggestion box. Jane in Phoenix From: LegacyUserGroup [mailto:[email protected]] On Behalf Of CE WOOD Sent: Wednesday, April 12, 2017 6:35 PM To: Legacy User Group <[email protected]> Subject: Re: [LegacyUG] Place names - olde vs current? It's a real shame that Legacy does not use the same Access ability and create an alternate location index as they have done for the alternate name index. It would be SOOOOOOOO helpful! CE _____ From: LegacyUserGroup <[email protected]> on behalf of Ian Thomas <[email protected]> Sent: Wednesday, April 12, 2017 5:43 PM To: Legacy User Group Subject: Re: [LegacyUG] Place names - olde vs current? Cathy Thanks for the information; I had noticed some posts here about reverse sorting addresses, but I didn't think it applied to my situation. And I do occasionally "correct" the mapping / Bing Maps positioning for locations that end up in the wrong continent, etc. But not for the historic place naming. Also, I should use the additional description you cited for Newcastle/Toodyay - the "(now Toodyay)" is more explicit than how I have been doing it. I would like to include the farm/property names - "Summerhill", New Norcia, Western Australia, Australia - but I have been putting this in Notes or a residence event, assuming that the quotes and specific property names would guarantee that the location couldn't be found by Bing Maps. The article you referred to is good - I hadn't seen it. Also, Brian Kelly's suggestion for positioning is a very logical method for registering the historic location name at essentially the location of the currently-used name for the location. Thanks, Brian. Ian Thomas Albert Park, Victoria 3206 Australia From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Cathy Pinner Sent: Wednesday, 12 April 2017 7:59 PM To: Legacy User Group <[email protected]> Subject: Re: [LegacyUG] Place names - olde vs current? Ian, You can plot anything on the Bing maps in Legacy. Just highlight the location you are mapping then right click on the map to put the pin in the right place. I include addresses, including farm names like your examples, in my locations. Others don't. Because I do this I always sort my location list from right to left when I need places close to each other together on the list. RE recording historical names. You might want to read this for one suggestion. <http://support.legacyfamilytree.com/article/AA-01014> http://support.legacyfamilytree.com/article/AA-01014 Sometimes I simply put the current name in brackets. Newcastle (now Toodyay), Western Australia, Australia. Cathy Ian Thomas wrote: What's the best practice for preserving the older place names while still mapping them accurately? An Australian example, the current t on of Toodyay near Perth in Western Australia was known as Newcastle, and I have some people with that connection, around the late 1800s. Also commonly used by country people then and now, is their property name (pastoral/grazing/cropping, etc) - for example, "Summerhill", New Norcia, Western Australia, Australia (or, "Pankee" - also close to New Norcia). I tend to record as shown, but I "lose" the ability to place them geographically via Legacy. Ian Thomas Albert Park, Victoria 3206 Australia
-- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
