On Mar 3, 3:26 pm, Thomas <[email protected]> wrote: > In the past, when it found that the input was a set og > geographical coordinates it retuned the country name and the exact > location provided. This behavior has now been changed, > > There is no way that this problem can be explained away.
But the version number is the *client* version number, not the version number of server-side behaviour. The fact that the geocoder's behaviour changed with v2.133 of the client doesn't mean that the old behaviour will be available after that point. However, you may have found a problem if you are supplying a string to the getLocations() method and it's not behaving as the documentation says it should. Reverse geocoding should work with a GLatLng object; and if you supply a string it should do "forward" geocoding -- according to the documentation. If you are supplying a string and it's being treated as a GLatLng because it can be interpreted as that, you could validly claim it's a departure from the documented behaviour. BUT!! What you are describing is a form of reverse geocoding -- supply something which looks like coordinates and get the country returned -- so that's undocumented behaviour too, and you can't rely on its being available indefinitely. 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 -~----------~----~----~----~------~----~------~--~---
