Thanks to everyone for the fast responses and for kicking me in the right direction.
I really appreciate your time. On Jan 27, 11:12 am, Andrew Leach <[email protected]> wrote: > On Jan 27, 4:50 pm, Fred Wilson <[email protected]> wrote: > > > Greetings, > > > When I use the ShowAddress() function, it does not fail when using a > > fake/invalid address. > > The geocoder does its best with what it's supplied with, and returns a > flag with the result to indicate how well it thinks it's done. > > > For instance: > > "12344 W. Thereisnostreet St., Dallas, TX" returns coords 32.802955, > > -96.769923 > > These are the coordinates for "Dallas" and the geocoder returns an > Accuracy of 4. > > > "12344 W. Thereisnostreet St., Dallaz, TX" returns coords 31.9685988, > > -99.9018131 > > These are the coordinates for the centre of Texas and the geocoder > returns an Accuracy of 2. > > > Is there a way to get the API to be less forgiving with bad addresses? > > No. It does what it does. You need to interpret the results. > Seehttp://code.google.com/apis/maps/documentation/reference.html#GGeoAdd... > for what the Accuracy means; presumably you are looking to reject > results which have an Accuracy of less than 6 to 8 or so. > > Accuracy is available if you use getLocations() instead of getLatLng > (). getLocations() returns a Placemark object holding much more data > than just the > location.http://code.google.com/apis/maps/documentation/reference.html#GClient... -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
