> *However, *entering a non-existent address such as "1234 nowhere Ln., > Durham, NC" or "532 Fake St. Durham NC" or "235 Gobbledygook Rd. Durham NC" > causes the API to return a status of "OK" and results[0] holds the same > LatLng object as if you type simply "Durham, NC" in maps.google.com.
The geocoder is working as it should; it's doing the best it can to provide some kind of location from mangled input. It's not an address validation service. But, as Andrew says, you can examine just what kind of guess it has made. -- 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.
