My app is used by English speakers who travel internationally. Therefore, I've tried to set up my HTTP Geocoder requests to return English city names using the "hl=en" flag.
This works great most of the time, for example, a point in Dusseldorf Germany: http://maps.google.com/maps/geo?q=51.2250093,6.7756310&output=xml&hl=en&key=yourkey The resulting LocalityName uses the English city name as opposed the German version with the umlaut. However, a point in Cologne comes back as "Colonia", which is Portuguese? http://maps.google.com/maps/geo?q=50.9406645,6.959911&output=xml&&hl=en&key=yourkey I know Google knows about "Cologne" because a normal Geocode request will return the correct LocalityName: http://maps.google.com/maps/geo?q=Cologne&output=xml&hl=en&key=yourkey If I set the language to German with "hl=de" then both Cologne and Dusseldorf get the correct German spellings. I also tried removing the hl flag entirely which seems to give English results by default (with the same Colonia problem). So perhaps there is a problem with the Reverse Geocoder not respecting language settings in some areas... seems like I'm not the only one with this problem: http://groups.google.com.au/group/Google-Maps-API/browse_thread/thread/f8ccd2ac15c1da1b Should I make a bug report and how do I do so? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
