Issue with foot-walking profile in OpenRouteService API decker v8.2.0 isochrones service

Dear OpenRouteService support team,

I am using the OpenRouteService API docker version 8.2.0 locally and have successfully invoked the isochrones service with the profile set to driving-car. However, when I attempt to use the foot-walking profile, the request fails. I have verified that the API and other settings are correct, as the driving-car profile works without issues.

Could you please help me understand why the foot-walking profile might not be working in this version? Are there any specific configurations or dependencies required for this profile?

Here are some details of my setup:

  • docker version: v8.2.0

  • Service: Isochrones

  • Profile working: driving-car

  • Profile not working: foot-walking

Here is a screenshot of the API requests.

I look forward to your assistance. Thank you so much.

Hi @weijing_zhong,

maybe you forgot to enable the profile?
Check http://172.20.10.3:8080/ors/v2/status and look for enabled profiles.

If it’s not there you need to enable it in your configuration (see docs).

Best regards

hi @amandus

Thank you for your response regarding the previous issue; it has been resolved successfully. However, I’ve encountered a new problem while testing with different coordinate points and I am reaching out for further assistance.

When using certain coordinates, some points calculate successfully (as the test 1 shown in the screenshot), but others return an error (like the second test in the screenshot, the coordinates corresponds to Gardens by the Bay in Singapore). The error message is:

“code”: 3099, “message”: “Unable to build an isochrone map.”

Interestingly, when I run the calculation using your web API for the second set of coordinates which returned an error in my deckor, it processes without issue. Could you advise on how to address this problem?

Here are some details of my setup:

  • docker version: v8.2.0
  • Service: Isochrones
  • Profile: foot walking

Thank you for your support, and I look forward to any guidance you can provide.

Best regards,

Hi @weijing_zhong

have you taken a look at our backend documentation yet?

By default ors uses a small pbf file from Heidelberg. (your first test coordinates are in that area) You need to swap out the pbf file and rebuild the graphs for any other area you want to use ors in.

Best regards