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

[Spencer Gardner]

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 bicycle-oriented folks think about. The solution for my problem was to
implement in pgRouting where I can do additional processing to assign costs
as you've described. It's not the way I'd prefer to do it but until bicycle
routing becomes more sophisticated on other routing platforms that's what
I've settled on.

I don't have the technical expertise to contribute code to OSRM but I'd be
more than happy to share my experience with bicycle network planning with
anyone looking to improve OSRM's handling of bicycles on this and other
questions.

Spencer

On Mon, Dec 23, 2019 at 6:35 AM Richard Fairhurst <richard at systemed.net>
wrote:

> 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 in reality
> the primary road wouldn't be used for routing.
>
> My private cycle.travel fork does something like this in its equivalent
> of process_turn (e.g.
> https://cycle.travel/map?from=51.7546,-1.2612&to=51.7554,-1.2616), though
> it’s a (pretty extensive) fork of 4.9.x so not directly comparable.
>
> Alternatively, you could do some preprocessing to mark intersections,
> depending on the size of your source data. For a different project I wrote
> https://github.com/systemed/intersector which identifies junctions in an
> .osm.pbf. If you were to patch it to output node IDs, then look up those
> node IDs in process_node, you could assign crossing penalties that way.
>
> Richard
> _______________________________________________
> OSRM-talk mailing list
> OSRM-talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osrm-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20191223/f38a9ce2/attachment.html>