The differences might only be an issue in some parts of the country. For example, a few months ago I used the HTTP geocoder to geocode some addresses in Alaska. For some locations (e.g., Juneau), but not all (e.g., Anchorage), the locations looked good when viewed on the street map, but not when viewed on the satellite map because the street map and satellite tiles were not aligned. Those same points today appear in the wrong location, if they were not previously manually adjusted, but re-geocoding them puts them in the correct place (and the two tile sets are now aligned).
I've spot-checked some locations in other parts of the country and haven't noticed anything out of place, but I can't recall which of those locations were manually adjusted after the initial geocoding -- several of them were but I didn't keep track of them -- or never used the geocoder in the first place. I just remember some parts of Alaska having sometimes large discrepancies between the street map and satellite images and those are the locations that also seem to have been affected by the HTTP geocoder change. At least that's what I've seen in my particular case. YMMV. On Oct 15, 11:41 pm, Marcelo <[email protected]> wrote: > On Oct 16, 8:02 am, "Thor (Google Employee)" <[email protected]> > wrote: > > > As the blog post states "If you've been using the HTTP geocoder and > > caching any retrieved data, you should re-geocode with the new data as > > soon as possible." > > Thor, > > The reason for this is not entirely clear to me. > Despite recent changes, I'm confident that Sears Tower remains at the > same lat/lon it was last month and last year, doesn't it? > > -- > Marcelo -http://maps.forum.nu > -- > > > We ask that you, and all other sites that have > > stored geocoding results for addresses in the U.S. obtained before the > > recent map data updates, geocode the relevant addresses again so that > > you are only storing geocoding results for U.S. addresses obtained > > after the updates. > > > Many thanks, > > > Thor. > > > On Oct 15, 2:02 pm, sachin <[email protected]> wrote: > > > > Hi All, > > > > Before 5 months i geocoded all my address in DB with the help of > > > google's http geocode service and saved the lat lng in my DB, After > > > seeing this post by google > > > -http://googlegeodevelopers.blogspot.com/2009/10/map-data-updates-for-... > > > i understood they have made some changes to USA map data, now when i > > > compare my lat lng with google's lat lng for a particular address i > > > see some minute difference in the last 3 digits and when my > > > application plot the marker on map also i see a little difference when > > > comparing with google maps. My question is should i update my DB with > > > the new data from google or since its a minor change can i skip it. I > > > am little confused and worried, i have lot of address in my DB, if i > > > have to update the data for the whole DB it will take a long time and > > > some peoples are already using my application. Please suggest me some > > > solutions. > > > > PS: All the address in my DB are address in USA > > > > Thanks > > > Sachin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
