Wierd result when using walking profile

Hi,

I’m testing the docker and I’ve built the graphs with the following config: https://termbin.com/y9jn5

But what I get is the red area in https://i.imgur.com/jkhCeTq.png while the green area is the same result but coming from server api_openrouteservice_org

payload is:

{‘locations’: [[-89.97834274952918, 35.110404896421834], [-89.98140301318266, 35.11016949152541]], ‘range_type’: ‘time’, ‘range’: [120], ‘interval’: 120, ‘location_type’: ‘start’, ‘attributes’: [‘area’, ‘reachfactor’, ‘total_pop’]}

Any idea what am I doing wrong?

Hey,

I just ran the request you provided in the api playground and wasn’t able to reproduce the green output you get from api.openrouteservice.org.

Instead, I got the following result

which looks quite similar to what your own installation yields.

Could you provide the full code you’re using to issue your request?
Unless we’re able to reproduce your issue, there’s not too much we can do…
Best regards,
Jakob

My bad, that was the wrong call, this is the right one:

curl -X POST 'https://api.openrouteservice.org/v2/isochrones/foot-walking' -H 'Content-Type: application/json; charset=utf-8' -H 'Authorization: <API KEY GOES HERE>' -d '{"locations":[[-89.94950156479179,35.154624252617744]],"range_type":"time","range":[120],"interval":120,"location_type":"start","attributes":["area","reachfactor","total_pop"]}}'

Hey,
I ran your request again, and got this:

which has a similar shape as the api-response from your screenshot, but is on a completely different street.

Please make sure that you are indeed using the same request and visualizing the corresponding results when comparing a local setup to api.openrouteservice.org

Best regards,
Jakob

Sorry, I can’t reproduce right now because of OOM errors but the original picture shows the issue. My gut feeling is that my graph takes driving directions into account while the official API doesn’t, the area is approximately the same but the red area is oriented west from the starting point while the official one goes in both directions.

Is there anything in my config that might explain that?

Forgot to mention that I’m 100% sure the request was exactly the same, just sent to two different endpoints (mines and the official one): it was generated by a script.

Ok, I was able to fix the OOM errors and here is the new image that compares my result (in red) and official one in blue) https://i.imgur.com/zEXjp6c.png

The call is the last one I posted:

curl -X POST 'https://api.openrouteservice.org/v2/isochrones/foot-walking' -H 'Content-Type: application/json; charset=utf-8' -H 'Authorization: <API KEY GOES HERE>' -d '{"locations":[[-89.94950156479179,35.154624252617744]],"range_type":"time","range":[120],"interval":120,"location_type":"start","attributes":["area","reachfactor","total_pop"]}}'

My finger is pointed to one-way restrictions (that should be ignored in walking profile, right?).

Ok, maybe it’s not the one-way tag, it seems like the points are snapped to the nearest node (intersection). Sorry, I’m a bit in the dark here, just guessing.