Penalize turns onto ways with restricted access: fees, customers

[daniel-j-h]

In #3721 @karenzshea implemented a penalty for turns onto restricted ways (think destination routing, hov ways, etc.). This makes sure we prefer alternative routes but we can still route you there if you really want to go there.

There is currently a discussion going on about zoos and other areas where customers have acces and / or you have to pay a fee for entry.

http://lists.openstreetmap.org/pipermail/talk-de/2017-February/113797.html

It would be great to support those tags (and maybe more?) in the same way.

• https://wiki.openstreetmap.org/wiki/Tag:access%3Dcustomers
• http://wiki.openstreetmap.org/wiki/Key:fee

cc @karenzshea

[daniel-j-h]

@bhousel just mentioned we should do the same for highway=track.

[daniel-j-h]

Same with the toll=* tag (and related namespaced tags). Note there are "except" tags. Also fee tags.

[TheMarex]

highway=track

There are some implications on data size that I think are worthwhile for ignoring this road-class for now.

[tyrasd]

highway=living_street does imply a no-transit restriction in some countries, e.g. Austria.

[daniel-j-h]

Adding amenity=weighbridge and similar weigh station tags.

[MichalPP]

is there a way to make profile.restricted_penalty different for different source and target ways? do I have a complete list of tags on source and target ways?

eg penalize left furn from primary & lanes > 1 to anything is duration+30

(looks like no: https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md )

[daniel-j-h]

@MichalPP

• Here we apply the turn penalty in the turn function
• Here we bind the C++ turn to the Lua environment
• Here is the C++ turn type

As you can see the turn object in the turn function does not know about tags anymore.
That said, we played around with passing more information to the turn function:

• Improve Turn Function #2912
• Road Priorities: Stop Signs, Give Ways #3009

but this got de-prioritized.

Feel free to pick this up or help out here if it fits your needs.
We need to make the turn function smarter, for sure.

[MichalPP]

well, my C skills are really small.

if the turn in process_turn(profile, turn) function had a turn.source (listing all tags on source way), turn.target (listing all tags on target) and turn.node (all tags on the node the turn is on), it would fulfill all my dreams :)

another use case is than in hiking routing, penalize turns from marked route to an unmarked path. or in car profile, add a small penalty when changing to lower class highways so that shortcuts through residential areas are avoided (even though they are not destination only)

[github-actions]

This issue seems to be stale. It will be closed in 30 days if no further activity occurs.