In Oslo we have quite some instances of motor_vehicle:forward = no or motor_vehicle:backward = no on roads, but this is poorly supported by routers in apps. E.g., Organic Maps, Mapy and Magic Earth do not support this tagging, only OsmAnd where you have to pay for CarPlay support.
e.g.,
There’s even an instance of motor_vehicle:forward = delivery
I think this tagging is understandable and does best in transferring the content of the traffic sign to osm. Any alternative tagging with oneway would not represent reality that good. I would not change it just for the router.
I am surprised that this does not work on those routers. I thought dealing with forward/backward and classic access tags would be a basic thing.
Are the routers not doing it because of a bug, do they not want to do it or are they not able to do it? I hope it is the first one and that these bugs can be fixed.
Graphhopper does support the vehicle/motor_vehicle:backward tag since many years and I doubt that this is something that would be hard to implement for other routers. For routers such tags are easy to support if the data is consistent and well documented in the OSM database.
I can’t confirm that, sorry: there’s a road where I couldn’t think of a better tagging than motor_vehicle:forward=permissive, motor_vehicle:backward=private. All routing profiles on osm.org, including GraphHopper, route cars in both directions:
The basic yes/no should work on all routers on OSM.org, I reported to Valhalla 1-2 years ago and they fixed it
I was not aware at the time that the apps like to implement their own custom routing algorithms…
I’ll bring it up with the Norwegian forum, but given how prevalent this type of signage is on the capital city Oslo I think we may have to tag for the router since the apps have not managed to implement it after all these years. Otherwise there’s no way I can use OSM myself, and I can’t recommend it to friends.
It might be good to add the traffic sign itself to the way additionally. This way it remains clear and it makes it easier to find and retag those cases in the future, when hopefully routers can handle this properly.
