When you say "should be avoided" you mean completely discarding a way going over a specific node in a single direction? In that case, we support turn restrictions in the form of `fromWay,viaNode,toWay` you could try.
As in: `no_turn, fromResidential, viaHighwayNode, toResidential` (Relevant: via-way restrictions: https://github.com/Project-OSRM/osrm-backend/issues/2681) Cheers, Daniel J H On Sat, Sep 24, 2016 at 6:16 PM, Spencer Gardner <spencergard...@gmail.com> wrote: > Is there currently a way to treat a node differently based on the way that > is used to access it? I think what I'm after is something similar to the > discussion here: > https://github.com/Project-OSRM/osrm-backend/issues/2652 > > My issue is specific to bicycle routing, though. There are instances where > a node should be avoided on a residential highway because it crosses a high > speed or heavily traveled primary highway. However, the same node is an > acceptable crossing for a cyclist traveling along the primary highway since > they have the right of way. > > Is this possible currently? It doesn't seem like the existing bicycle > profile accounts for it. > > _______________________________________________ > OSRM-talk mailing list > OSRM-talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/osrm-talk > >
_______________________________________________ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
