Default bicycle profile ignoring turn restrictions?
osmuser63783 opened this issue · comments
Describe the bug
This relates to the routing profile "Bicycle (GraphHopper)" on https://www.openstreetmap.org which I assume is the default bicycle profile in this repository, but please direct me elsewhere if I'm in the wrong place. I was also able to reproduce this on https://graphhopper.com/maps/
The bug (or feature request?) is that the bicycle profile doesn't seem to take into account turn restrictions.
To Reproduce
Here is an example: https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=55.95428%2C-3.18766%3B55.95415%2C-3.18729
More examples can easily be found using Overpass.
Expected behavior
Normally I would expect a restriction with restriction=no_right_turn to apply to bicycles unless it also has except=bicycle. That's because in the jurisdictions I know, the no right turn traffic sign applies to all vehicles, including bicycles.
I've also seen semicolon-delimited values such as except=bicycle;motorcycle. There's also restriction:bicycle, restriction:hgv etc. which could ideally be supported (restriction:bicycle honoured, but restriction:hgv, restriction:motor_vehicle etc. ignored).
System Information
Current version of GraphHopper on https://graphhopper.com/maps/, not sure which version that is
Screenshots & Logs
GraphHopper Maps link. Expected result: this here is a reasonable alternative.
This is already possible with the routing engine, but not (yet) deployed on GH Maps. We are planning to deploy this in the future but when exactly is unknown.
(The priority for this was/is low as one could get off the bike and cross the street.)
That would be great, thanks. There isn't always a pedestrian crossing and there may be multiple lanes so if you're in moving traffic and you've positioned yourself in the inner lane to turn, then by the time you realise the turn isn't possible, it's often too late.