Specific examples are not relevant here. What matters is the source of the data you are using, and Google's contractual obligations to the providers of that data.
The new data may disagree with the old data to only 0.000001 of a degree, but the fact still remains that geocodes results you have stored that were obtained before the map updates may be based on data sourced from a different provider than now used, and as such we are obliged to require that you regeocode. We understand that this may seem inconvenient and unnecessary, and we would not insist upon it if it were not absolutely necessary to do so. If you regeocode your addresses, and you find that you know from first hand experience that some of the results you are seeing are incorrect, then we ask that you submit a correction using the new 'Report a Problem' link on Google Maps. You can also right click on the correct location on Google Maps and select the 'What's here?' option on the popup menu to obtain the lat/lng (it will appear in the search box). You are then free to use that lat/lng in your application because you are the source of that geocode result, rather than any of Google's data providers, past or present. Many thanks, Thor. On Oct 26, 3:46 am, Marcelo <[email protected]> wrote: > The only possible situation that comes to mind is if the location of a > *street* has been changed because it was erroneous, and therefore all > addresses on that street have changed their lat/lon as well, but > still, that has nothing to do with "attributions", does it? > By "attributions" I understand the copyright notices displayed at the > bottom of the map. > > @Thor: Should this be the case, could you please point out some > specific areas where this may be visible? > > -- > Marcelo -http://maps.forum.nu > -- > > On Oct 25, 8:23 am, Andrew Leach <[email protected]> > wrote: > > > > > On Oct 25, 12:46 am, "Thor (Google Employee)" > > > <[email protected]> wrote: > > > So if the base map data disagrees with the stored > > > geocode you have for a particular address, and you place a marker on > > > the map to identify an address as being in the location given by the > > > old data, you are using the old data without attribution. > > > It strikes me that if I want to display a marker at an address and > > find its location by geocoding, I have a location. If that location > > differs in the new data, and it's now wrong, I can choose whether to > > use the new place or the location I know to be correct. > > > With "pre-found" points, we may well already know they are accurate. > > Why risk getting it wrong? > > > This doesn't apply to new addresses, where we have no choice but to > > use the new data. But if we're finding known addresses in advance, > > like we're supposed to, we may well wish to correct inaccurate > > geocodes. Who owns that corrected data? It's entirely possible that > > the location we correct the geocode to exactly matches the previous > > provider's data, isn't it? > > > Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
