I stopped using the Geo database long ago because it was so far off on many locations and didn't have others. I use Google maps, Bing maps, GENUKI, and other location finding sites for every location.
And I pinpoint every church, castle, etc. too, so I have more than a hundred thousand locations. When I am updating or amending a person, I also correct the locations for which I did use Geo before I realized it was useless. Yes, I may be OCD, but when I locate a church, I want the arrow to be on the church! I have not found any easier way to change the Geo database locations other than individually. Just do several at a time, and you will get there, CE From: [email protected] Date: Thu, 31 Jul 2014 16:22:04 -0700 Subject: [LegacyUG] Geo_code places How to review large numbers for correct placement To: [email protected] Has anyone found a way to review large numbers of Place Location Geo-Coded placement without having to do one location at a time? I have almost 10,000 places and I am constantly finding Geo -Code errors. For example I have two locations in my list Alban, South Dakota 44.4361381666667 -100.230491666667 Alban, Grant, South Dakota 44.6187705555556 -89.2845230555556 Yes, these should be merged, but they make a great example here Legacy Geo-coded the them as listed above. The first one, Alban, South Dakota points to center of the state and has the same coordinates that is used by the state generic South Dakota 44.4361416666667 -100.230451111111 In other words the geo coding did not find the correct place except to place the pin at the center of the state, which would be OK IF there was some disclaimer or notation somewhere. The second one is geo-coded to Alban, Portage County, WISCONSIN Why, is Geo coding setting wrong places?? (According to Google the coordinates for Alban, South Dakota are 45.1952395,-96.546404) With no tool to at least review the places in some sort of batch (like maybe 25 places on a page each with a small map of the geo-coded place. At least then I might have picked up that one of these was pointing to wisconsin and not South Dakota. One at a time review is just not a viable option. Anyone have any workable solutions? Thanks in advance for any help. Jay 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
