On Jan 27, 8:50 am, Fred Wilson <[email protected]> wrote: > Greetings, > > When I use the ShowAddress() function, it does not fail when using a > fake/invalid address. > > For instance: > "12344 W. Thereisnostreet St., Dallas, TX" returns coords 32.802955, > -96.769923 > > "12344 W. Thereisnostreet St., Dallaz, TX" returns coords 31.9685988, > -99.9018131 > > Both of these addresses are invalid. > > The first address uses a fictional street name. The second misspells > the name of the City as well as having the invalid address. > > Is there a way to get the API to be less forgiving with bad addresses? > > Finally, > "12344 W. Thereisnostreet St., Dallas, TZ" returns NULL. Only by > using an invalid State abbreviation was I able to get the API to > return NULL. > > Any help is appreciated!
The API Geocoder is not an address validator. It does its best to return a location for the query you give it and tells you how accurate it was: http://code.google.com/apis/maps/documentation/reference.html#GGeoAddressAccuracy Your first query returns: [ 0 ]: Dallas, TX, USA (32.802955, -96.769923) "Accuracy": 4 [Town (city, village) level accuracy.] http://www.geocodezip.com/example_geo2.asp?addr1=12344%20W.%20Thereisnostreet%20St.,%20Dallas,%20TX&geocode=1 Your second query returns: [ 0 ]: Texas, USA (31.9685988, -99.9018131) "Accuracy": 2 [Region (state, province, prefecture, etc.) level accuracy.] http://www.geocodezip.com/example_geo2.asp?addr1=12344%20W.%20Thereisnostreet%20St.,%20Dallaz,%20TX&geocode=1 And your third query returns no result because all parts of the address are invalid. -- Larry -- 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.
