Geocode returns multiple coordinates for a single address

openrouteservice
1

Hello,
I’m building an app that geocodes addresses. The issue i have is that some addresses (they’re all in London) return more than one set of coordinates for the same address. In the json response to a structured geocode API call, the coordinates are found here:

"type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          -0.123523,
          51.514816
        ]

But for some addresses, this is repeated (sometimes several times over). This causes problems elsewhere in my code where I end up with more coordinates than I have original addresses.

Why does this happen, and how do I stop it?

Thanks in advance,
Alan Mott

2

Hi @AlanMott ,

please provide the full request (excluding your API key) and response you have issues with or if you are working with sensitive data, create a sample requests where this happens as well.
You could work around this in your code by just using the first entry you get back
Depending on the address it might be
Probably the address you are providing fits multiple entries?

Best regards

3

Thanks. On furher investigation it would seem the addresses themselves are the issue. I’ll keep digging

4

I have the same issue.
I used
https://api.openrouteservice.org/geocode/search?api_key=xxx&text=yyy
https://api.openrouteservice.org/geocode/search?api_key=xxx&text=zzz
within one web session. because I needed to see the coordinates of two addresses, and both time it returned the same two coordinate pairs, in the same order.
Is there a way to send a kind of reset between the two api call so only one (the correct) coordinates are retuned?
So when I send a search request it should not remember the previous requests and repeat those results.
Or if this is a must then if the corresponding address in the search parameter would be added next to the coordinates, then it could also solve my issue.

5

Hey,

we do not cache anything, so these results are probably due to your query.
Could you share the text you used in your two searches?

Best regards