> I think I see now , you were using the geocoder as a text parser. > Send it text "70.54, -4.32" and get a location back of 70.54, -4.32 in > an API-friendly format. I'm afraid that wasn't what the geocoder was > really intended for, and things have moved on now.
Using the geocoder as a text parser is normal. When somebody enters a wrong or unknown address the geocoder returns an error code indicating why it could not provide a location. It does that by parsing the input etc. 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, and that is fine, as long as you get the old behavior when you specify a version before 2.133. There is no way that this problem can be explained away. It is simply an error in the Google API. That is what I wanted to point out in the hope that Google might fix it. I am sure there are other users who rely on the fact that when you specify version 2.97 you get version 2.97 behavior. At the moment you don't. I can easily do my own parsing to detect a coordinates input, and that is what I have already done on the Danish page. It is certainly the right solution for the future, but the fact remains that you don't get the behavior you expect when you specify older versions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
