|
I'm using the MapQuest Geocoder API for an integrated Maps component in my application. The address "Savelveld 25, 6039 SB, Stramproy" is displayed in America while this is an address in The Netherlands. The coordinates are being generated incorrectly by the API. Input: "Savelveld 25, 6039 SB, Stramproy" Output: { "CoordSets": [ [ { "Lon": "-100.445882", "Lat": "39.78373" } ] ] } The correct output should be: { "CoordSets": [ [ { "Lon": "5.711368", "Lat": "51.200246" } ] ] } Can you please let me know how we can make these coordinates correct in the so ? Is there someone from the development team who can change it into the source code? |
|
Nominatim would find the address, if you delete the space in 6039 SB, example: https://nominatim.openstreetmap.org/ui/search.html?q=Savelveld+25%2C+6039SB%2C+Stramproy but does not find the address if the space is included: https://nominatim.openstreetmap.org/ui/search.html?q=Savelveld+25%2C+6039%20SB%2C+Stramproy The dutch postcode search at https://www.postcode.nl/6039SB/25 shows that Dutch postcodes should be written without a space, but I'm not sure about the definition of postcode patterns in the Netherlands, so this should probably be discussed/asked with the Dutch OSM community at the Dutch mailinglist at https://lists.openstreetmap.org/pipermail/talk-nl or the Dutch forums at https://forum.openstreetmap.org/viewforum.php?id=12 . If both patterns are correct, it would be an issue for nominatim. Regarding the wrong U.S. response by Mapquest: that's sth. you should bring up at Mapquest. |
This is not MapQuest's developer support desk, you should probably contact them.
To make Richards answers clear Mapquest stopped using OSM data directly a long time ago and may not be using any at all at this point in time. At least at times the services were provided by mapbox, but in any case you are completely wrong here and need to talk to mapquest.