In my work, I spend most of my time in areas with restricted access, which means I most of the time can not use openrouteservice to calculate a route leading to these places. I can fully understand that openrouteservice will not calculate a route through a gate tagged “access = no” or similar, since it doesn’t know I have my keycard that will open that specific gate.
Please add an option, maybe under “additional settings”, that would ignore the limitations of access restrictions . Either fully, or in separate levels (ie “ignore access private”, “ignore access NO”, etc").
With the functionality of today, I have to make…
- one route up to the gate, and then
- a second route from inside the gate to the next gate
- a third, fourth… and so on.
This works, since the actuall ROADS are not tagged access=*, only the gates. But it is very annoying to have to create multiple routes, when one route with multiple waypoints would be a much more convenient solution.
(By the way, I accidantly greated an github issue with the same topic first. Was that wrong?