Thanks -- specifying the language in the query does help! As far as the accuracy of the results, I still have not found a way to improve that. For now, I am just moving the Google Geocoding service down in terms of preference, since it seems to be the least accurate of the services I use (Yahoo! is by far the best).
Ben On Nov 2, 11:04 am, Andrew Leach <[email protected]> wrote: > On Nov 2, 3:50 pm, exline <[email protected]> wrote: > > > Also, I am not sure why the LocalityName node appears like this: > > > <LocalityName>??????? ??????</LocalityName> > > > Can anyone help? > > I can answer that. It comes back in Arabic (may not appear correctly > below though). I can't see any reason why the response should not be > in English; but adding hl=en fixes that. > <LocalityName>لويفيل، كنتاكي</LocalityName> > It translates as "Louisville, Kentucky". > > I wonder if that means the new geocoder data for the US comes from the > Middle East...? > > The API puts the address in North Keats Avenue, Louisville. That's > probably enough for most purposes -- if you know it's wrong, just use > the right location. > > 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.
