Thanks @troy, got it!
As I mentioned earlier in this thread, enabling control over the GraphHopper’s location index requires some adjustment to our backend. I will look into it, you can track the progress in #712.
Cheers,
Andrzej
Absolute legend @andrzej !
I’ll be lurking in the Github issue, keen to see how it all gets implemented - it’ll make for a bit of good Java learning 
Appreciate all the quick responses and willingness to help!
Cheers,
Troy
Hi, maybe I am wrong, but I think you can change the “index.high_resolution” parameter in openrouteservice/src/main/java/org/heigit/ors/routing/RoutingProfile.java and it should be passed on to GraphHopper. “index.max_region_search” is not specified however and would need to be changed in the GH maven repository, I think.
Actually, we already have a solution to this waiting to be merged into the master branch: https://github.com/GIScience/openrouteservice/pull/713
This might be another example affected by this problem:
https://maps.openrouteservice.org/directions?n1=46.491371&n2=8.336375&n3=13&a=46.506785,8.306866,46.491317,8.351096&b=1c&c=0&k1=en-US&k2=km
I stumbled across it when trying to do bicycle routing over the Nufenen Pass in Switzerland.
Thank you for your feedback! This is a different problem caused by a conditional access restriction: the road is closed Oct-Jun. We don’t support time-dependent routing on our production server yet, but you can get a preview of the functionality which is underway on the project demo server.
Hi!
I discovered OpenRouteService a couple of days ago (but already got excited about it!) so please forgive me if this is a dumb question.
I’m also running into the “Could not find point” issue, whatever radius I set (even -1).
The thing is, it happens with a position that is not so far from a road: [6.3642845,44.9997218]
I even tried on https://maps.openrouteservice.org/ and it says it’s about 7km away (see screenshot)
I’ve tried locations nearby:
- 6.366684, 45.002392: failed
- 6.366985, 45.005305: worked, even with a radius of “only” 6km => so it really isn’t because it’s “lost in the middle of nowhere”
So there is “bermuda triangle” around the first location I’m trying to reach.
Is there anything I could do? (except doing programatically what I described above: to empirically try locations nearby until it works…)
Thanks