There are a few old tickets that discuss this:
https://github.com/Project-OSRM/osrm-backend/issues/96
https://github.com/Project-OSRM/osrm-backend/issues/477
https://github.com/Project-OSRM/osrm-backend/issues/592
Ultimately, what needs to happen is we need to make the `turn_function`
smarter
I've tried it as well. no success...
similar case is for pedestrian (crossing a major, unroatable road; or
a railway; or a river with no bridge)
wheelchair users, strollers
or nordic skiing users crossing a car road
a next step would be to have a custom penalty on a node, toll booth,
stop sign,
Unfortunately, I don't have a good solution to offer, but I wanted to add
my two cents. I did a ton of research on this exact problem a couple of
years ago and virtually none of the open source routing platforms I came
across were properly equipped to handle it. It seems to be an issue that
only
Jeroen Hook wrote:
> Is there another way to find out what type of road(s) I am crossing?
I think the easiest solution would be to allow bicycles on your
highway=primary, but set it to be a restricted access road (or just to have a
really high cost). That way you’d still call process_turn, but
Hello,
I am looking into a bicycle routing problem and need some help on how to
access certain information from within the bicycle profile.
The routing problem may be summarized as follows. Two routes are
available; one of these crosses a large road (say, highway=primary),
with an uncontrolled
