Re: [OSRM-talk] Bicycle routing, crossing large roads: how to get information on the roads crossed

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

Re: [OSRM-talk] Per-Direction Node Restrictions

gt; ugly to implement. Sorry. > > On Thu, Oct 6, 2016 at 12:19 AM, Spencer Gardner <spencergard...@gmail.com > > wrote: > >> I started working on this in https://github.com/Project-OSR >>> M/osrm-backend/pull/3009 but it won't be a quick change in the >>>

Re: [OSRM-talk] Per-Direction Node Restrictions

> > I started working on this in https://github.com/Project- > OSRM/osrm-backend/pull/3009 but it won't be a quick change in the > profiles, for sure. > > Cheers, > Daniel J H > > Thanks. Will your changes also allow me to read the tags of other roads approaching the same node? That's the

Re: [OSRM-talk] Per-Direction Node Restrictions

On Tue, Sep 27, 2016 at 5:11 AM, Daniel Hofmann wrote: > 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

[OSRM-talk] Per-Direction Node Restrictions

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