Howdy. I've been working on implementing a map that uses the API's Geocoding Service. Yesterday I noticed two geocoding search requests that return something different from what they used to return before yesterday. For Example:
Searching for "Lid Park" or "Lid Park, Seattle" or "Lid Park, Mercer Island" all used to return the LatLngs of the (to my knowledge) only Lid Park in the world: on Mercer Island, in Seattle, WA (see http://drop.io/meetamit/asset/expected-results-jpg). As of yesterday, searching for "Lid Park" returns 10 unexpected results in Chinese, dispersed throughout China (see http://drop.io/meetamit/asset/unexpected-results-jpg). There is no longer a search term that would geocode to the desired Lid Park. Even if I try to bias the search to the US (using the 'country' parameter in the request). Searching for "Lid Park, Seattle", geocodes to the LatLng (and bounds) of all of Seattle. Similarily, searching for "Lid Park, Mercer Island" geocodes to the LatLng of Mercer Island, rather than the desired park. It's worth noting that a Google Local search still returns the expected results, so if one searches for "Lid Park" on maps.google.com, one gets back the expected results (coming through Google Local). Unfortunately, we need to use the geocoder, and not Google Local. Any ideas? This is happening with both the V2 and the V3 APIs (probably because they both use the same underlying database). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to google-maps-api@googlegroups.com To unsubscribe from this group, send email to google-maps-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
