Many of my relatives were living in Virginia, areas now West Virginia. In prior software I used, the location could only be shown on a map if you gave the state as West Virginia, historically incorrect. What are Legacy best practices in this situation? Bill
Sent from my iPhone On Jul 20, 2014, at 10:11 PM, Ron Taylor <[email protected]> wrote: > The GEO database is a list of current locations...not time sensitive. The > county verifier can do some time sensitive lookup but it is not coordinated > with the GEO database. The Virtual Earth maps (now called the Bing Maps) are > not coordinated with the GEO database either. Those are 3 different ways > that locations can be checked in Legacy. What is really needed is a location > table based on longitude and latitude. Then given a date and the > coordinates, you could query the location for any language and any time frame. > > > On Sunday, July 20, 2014 6:32 PM, FLR <[email protected]> wrote: > > > From 1778 to 1820 it was called the District of Maine. > > FLR > > Sent from my Netbook > ----- Original Message ----- > From: [email protected] > To: [email protected] > Sent: Sunday, July 20, 2014 6:55 PM > Subject: [LegacyUG] Geo-Locator Not Always Correct > > I recently tried to insert a birthplace as Dixfield, Cumberland County, > Massachusetts only to be informed that there never was a Cumberland County in > Massachusetts. While it is is true that Cumberland County and Dixfield are > in Maine, the state of Maine did not come into existence until 1820. Since > Cumberland County was founded in 1760 out of York County, Massachusetts, I > entered the data against the advice of the geo-database. This is much like > saying a county like Brooke County, West Virginia existed in 1845 when the > entire state of West Virginia had not yet exist. Anyone else find errors in > the geo-database or can point me to where I have made an error? > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
