> I guess that depends on your use case (which I guess is your point, right?)
I think that's the size of it; so far as I can see the geocoder is provided by Google to extract some/any kind of location from user's mangled input, which makes it inherently unsuitable for address validation (or the partial validation you require) > Honestly, now that we are checking the other results, it's not really a > problem. Understood > My frustration was that it *changed. Yep, they do that. For most use-cases it would be an enhancement. One of the real maps gurus often said "never trust a geocoder", they're never more than a best-guesser. Only the end user knows what they really mean, hence maps.google.com "Did you mean?" feature. API developers can produce their own tailored version (e.g. in your case it might be geographically limited) -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
