[Tagging] Do we still need cycleway=opposite?

Martin Koppenhoefer dieterdreist at gmail.com
Sun Mar 17 11:21:30 UTC 2019

sent from a phone

> On 17. Mar 2019, at 10:50, Markus <selfishseahorse at gmail.com> wrote:
> I support discouraging cycleway=opposite. This tag gets too often
> confused with cycleway=opposite_lane.

cycleway=opposite specifies a track (=distinct bicycle carriageway) whose position and direction are opposite to the direction you would expect (e.g. it is left for right traffic jurisdictions), right? Shouldn’t this be either cycleway:left, :right or :both? The meaning depends on the road being oneway or not?
Would you add it in case the track is explicitly mapped? In other words, is it a property of the road and independent from an explicitly mapped cycleway, or is it either or?

Or does it include both, tracks and lanes? There is also some usage of opposite_track.

IMHO the default should be cycleway=no 

Cheers, Martin 

More information about the Tagging mailing list