Data Errors in mapquest nomatim vs the openstreetmap instance

5 posts / 0 new

Mon, 04/20/2020 - 08:35

davidbuchmann

When i search for 3945 Gampel on the openstreetmap data, i get the correct coordinates: https://nominatim.openstreetmap.org/search.php?q=3945%2C+switzerland&pol...

The same on mapquest gives me no results http://open.mapquestapi.com/nominatim/v1/search.php?key={KEY}&accept-language=de&format=json&addressdetails=0&countrycodes=ch&country=ch&q=3945

When searching for "Gampel" in the mapquest nomatim, i get results for 3940 which in reality would be the zip code of Steg-Hohtenn, a place nearby but not the same place.

Why is the data different? I understood that the nomatim service on mapquest would provide the same data as openstreetmap.org has.

Tue, 04/21/2020 - 22:01

MQBrianCoakley

The MapQuest version of

The MapQuest version of Nominatim is not up to date and can produce different results. This is not unexpected.

Wed, 04/22/2020 - 06:31

davidbuchmann

i had understood only the

i had understood only the code version would be different, not the data set. (i would assume data and application are separate updates, but that was just a guess)

do you know how frequently MapQuest updates nomatim (interested in the data, not the nomatim server application)?

Wed, 04/22/2020 - 07:14

(Reply to #3)

MQBrianCoakley

The data is years old at this

The data is years old at this point, with no concrete plan to update the data. It was basically sunset a couple years back.

Wed, 04/22/2020 - 07:52

(Reply to #4)

davidbuchmann

well that is good to know. i

well that is good to know. i did not see a warning anywhere that this is the case. would be nice if mapquest would put that in a large red box onto the documentation - i only started using this last year and did not notice any such warning.