There is a lot of data about places to visit in my database. My users choose the places to visit and create a route for themselves. Some points in this route may be too far from the road for transportation (such as monumental trees, waterfalls in the forest). In this case, I cannot create a route and I cannot find which point I am having trouble reaching.
In this case, is it possible to display something like Google Maps, such as drive to this point, then walk?
It would be great if I could do this, if not, how can I follow a path?
Your ideas and suggestions are very valuable to me. Thanks in advance.
you can use the snap endpoint to check wether the place is reachable within the default snapping radius of 350m and if not try to generate a foot-walking route there from somewhere in the vicinity.
Thank you for your answer. But I’m asking to understand fully. In this case, I need to create a snap control for each added point and, depending on the situation, a walking route and combine all possible routes to produce a result. Am I understanding correctly?
If true, is there an example code block (can be in any language) regarding this issue?
If there are many dots, won’t this cause a performance problem?
A route consists of at least 5-10 points.
that’s 10.000k locations per day. Hopefully this will be enough?
You can produce code examples for this endopint with our API documentation
(see link in above post) → click example code button
There is also the radius parameter, where you can increase the snapping distance for points not snapped with the initial range. I think the internal limit is something of 2000m so for really remote points you have to figure out a different solution.
Regarding the logic, that’s something you need to figure out for your use case yourself
Thanks, I installed ORS on my own server but I couldn’t configure it completely. I increased the limit but it still works as 350m. I couldn’t find what I’m doing wrong.
Also, the configuration phase (ORS indexing on bicycle and walking paths etc.) takes too long, I can’t see which phase it is at. That’s why I can only use vehicle routing.
If I share my YML file, can you help me find the error?
we can certainly try - please share your docker compose file as well if you’re using that or detail your setup if you don’t.
Please also strip both the docker compose and the ors-config.yml files of anything not used.
What do you mean by
The openrouteservice needs to build routing graphs on startup, which can indeed take quite some time. However, times for different profiles should be roughly comparable.
Limiting the openrouteservice to the area needed will probably speed up the process considerably.
Also, the ors logs should report on what profile is currently being built, so you should be able to see at least that.
thanks for truncating your files - could you paste them with the existing indentation? Otherwise its very hard (or maybe even impossible) to tell what is going on…
going by the log, it looks like the openrouteservice is successfully building graphs. I don’t know what you are building, but 30 minutes is not a lot of time for a single profile to build - for something with a pbf size of ~300MB, I’d expect that.
