Tue, 09/01/2015 - 09:27
#1
Why API always retuns geocode for invalid address?
Hi,
It seems that API always returns some geocode despite of invalid address supplied.
For exapmle:
https://www.mapquestapi.com/geocoding/v1/address?key={YOUR_KEY}&thumbMaps=false&location=wrongstreet+wrongtown
returns {lat=39.390897, lng=-99.066067} ????
I would realy expect "Address Not Found" response.
Is there any option needs to be set to get Address Not Found" response?
Thanks
I find this is NOT true. Quite the opposite. I find if there's even the slightest mistake in the address information, the API will not return best guess, or next closest coordinates. It always defaults to somewhere in the mid Atlantic or the waters off the coast of Nigeria! I am very disappointed with the performance of this API and, based on this experience, would never opt to use any paid service plan.
Example:
409 W Green St, Athens, Alabama. MapQuest returns 0,0.
W Green St, Athens, Alabama. MapQuest returns 0,0.
Green St, Athens, Alabama. MapQuest returns 34.804549,-86.971170.
Athens, Alabama. MapQuest returns 34.804549,-86.971170.
BUT... 409 Green St W, Athens, Alabama. MapQuest returns 34.801025,-86.974119 (The true address coordinates)
So if MapQuest can't find a precise street address, the city and state do not exist. Isn't that just special?
I get L1AAA at 34.801315,-86.973495 for http://www.mapquestapi.com/geocoding/v1/address?key=KEY&location=409%20W...
Can you post the requests to www.mapquestapi.com that return 0,0?