but this just proves the point -- end users dont always enter the perfect address, but the interpretation of such addresses should be just as good in v3 as it is in v2. even if its ballpark by a couple turns, that is wayyyy preferable to miles off target the v3 gives. the results should be identical, and for some reason v3 isnt able to cope the same way given the same malformed address. there has to be some sort of fix or way around this?
-- 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/-/07fO_iYgJ88J. 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.
