@Rossko, I understand your point; if the Geocoder were smart enough to know that Donwing st. means Downing St, or that Londno means London, and return something like 'street_address' for the location_type and 'best_guess' for type[0] it would certainly be helpful.
...but is it helpful to return results of location_type 'locality', type[0] 'approximate' for the city of London if you misspell Downing St.? In other words, you misspell the street name, so rather than return results for that street with a type of 'approximate' or 'best_guess' the API returns the LatLng of *the city center?* I guess that depends on your use case (which I guess is your point, right?) Honestly, now that we are checking the other results, it's not really a problem. My frustration was that it *changed. *It used to return ZERO_RESULTS, but sometime in the last 8 weeks it started returning 'OK' with the location_type of 'locality' instead. If you go to maps.google.co.uk and type in '10 donwing st. London' it puts a marker on 10 Downing St. and says "did you mean..." So I think Google *is * smart enough to detect typos, at least. If you type in "10 bullshit st. london" it says "we could not locate this address" and doesn't put a marker there. ( I know that "maps" and the API are two different things, but I though it helped make my point). Anyway, I see where you're coming from. Thanks for the lively discussion. -Wes -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/a1XaQlnHZUUJ. 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-js-api-v3?hl=en.
