Rossko wrote: > That bahaviour is correct. It'd be like insisting a search engine > should always return the same results for a given keyword, for ever. > Geocoding is an inexact art, and the geocoders are being improved - > well changing, anyway - constantly.
That is not the same at all. The issue is not the data that is returned by the reverse geocoding function. The issue is that the API functionality has changed. When I submitted getLocations() with geographical coordinates before 2.133 I got the same point back, now I get multiple locations none of which (in general) have the exact coordinates that I entered. If you want to see the difference in behavior, you can try entering coordinates at map.netkvik.dk (an English version) and at kort.netkvik.dk, the Danish version that I have just corrected so that it behaves like pre-2.133. The English version will soon be corrected as well. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
