You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The annotation process looks at the oneway tag to determine if a road is available in one direction only, mapping all travel directions to the same segment.
There is also the tag oneway:bicycle to tag roads that are oneway for cars, and bidirectional for bikes. We should use that, if available, to ignore oneway tags. See: https://wiki.openstreetmap.org/wiki/Key:oneway:bicycle
We might also want to consider not caring at all about those tags, as bikers tend to ignore oneway streets anyway, or there might be a dedicated bike lane in reverse direction. Either way, there are probably few overtaking events in the reverse direction (as cars aren't travelling there), but for biker's road usage statistics, this is a valuable information to have and we should not discard it, or assume travel in the "forward" direction even if GPS indicates the reverse.
When a cyclist is ignoring a "oneway" tag and gets overtaken by a motorized vehicle as evidenced by a recorded overtaking event, he certainly wasn't the only one to ignore it... But my guess would be that often these events are evidence of close passages of head-on traffic as is common in oneway streets and a cyclist pressing the button to record that the passage felt too close to be comfy.
cyclist pressing the button to record that the passage felt too close to be comfy
Yeah but that is contradicting the meaning of the button, i.e. "passed on the left, from behind (while moving)", which is the kind-of definition we've been using until now. We don't record oncoming traffic, and we also don't decide whether to press or not to press the button based on how safe the overtaking event felt, but we record all events that occur.
As I said, we should not assume all bikers to travel down the oneway street in forward direction, as we're also able to do statistics that are not about overtaking events on the data:
but for biker's road usage statistics, this is a valuable information to have and we should not discard it
The FACE script now interprets both oneway and oneway:bicycle to derive separate permissions for motorized vehicles and bicycles.
Further, now the permissions for bicyclist are used for mapping the GPS trajectory to existing OSM ways. Before, the permissions of motorized vehicles were used - so this was indeed wrong. This should only make a difference for streets which are unidirectional for cars and bidirectional for bicycles.
Also, now the "junction"="roundabout" tag is interpreted, as this implies a one-way street.
What remains open is how to handle odd situations where bicycle and/or cars ignore unidirectional restrictions.
Activity
gluap commentedon Oct 16, 2021
When a cyclist is ignoring a "oneway" tag and gets overtaken by a motorized vehicle as evidenced by a recorded overtaking event, he certainly wasn't the only one to ignore it... But my guess would be that often these events are evidence of close passages of head-on traffic as is common in oneway streets and a cyclist pressing the button to record that the passage felt too close to be comfy.
opatut commentedon Oct 19, 2021
Yeah but that is contradicting the meaning of the button, i.e. "passed on the left, from behind (while moving)", which is the kind-of definition we've been using until now. We don't record oncoming traffic, and we also don't decide whether to press or not to press the button based on how safe the overtaking event felt, but we record all events that occur.
As I said, we should not assume all bikers to travel down the oneway street in forward direction, as we're also able to do statistics that are not about overtaking events on the data:
FlorusCiphersmith commentedon Dec 10, 2021
The FACE script now interprets both
onewayandoneway:bicycleto derive separate permissions for motorized vehicles and bicycles.Further, now the permissions for bicyclist are used for mapping the GPS trajectory to existing OSM ways. Before, the permissions of motorized vehicles were used - so this was indeed wrong. This should only make a difference for streets which are unidirectional for cars and bidirectional for bicycles.
Also, now the
"junction"="roundabout"tag is interpreted, as this implies a one-way street.What remains open is how to handle odd situations where bicycle and/or cars ignore unidirectional restrictions.