From OpenStreetMap Wiki
Jump to navigation Jump to search

This key and cycleway=opposite

In my eyes oneway:bicycle=no is the same as cycleway=opposite. We should therefore decide which tag we use so that we not always write both. Whether there is a physical bike path is expressed with cycleway=opposite_lane or cycleway=opposite_track.--geozeisig (talk) 09:40, 18 January 2018 (UTC)

I agree that it makes little sense to use both at the same time. That was an ok solution for the transition period, but now that the usage numbers for oneway:bicycle=* have overtaken cycleway=opposite, and developers have had years to implement the change, we should probably stop using cycleway=opposite. --Tordanik 19:45, 19 January 2018 (UTC)
I did not quite notice the history of the story. But cycleway=opposite is rendered on the cycling map, oneway:bicycle=no not. Maybe you should change that first?--geozeisig (talk) 08:27, 20 January 2018 (UTC)
Good news: The cycle map now renders oneway:bicycle=no correctly. Bxl-forever (talk) 22:31, 13 May 2019 (UTC)
I use oneway:bicycle=no for access right (if there is a sign saying so) and cycleway=opposite for the cycle infrastructure : if there is not a track, not a lane but some bicycle logos paint on the ground. If there is nothing on the road I don’t use cycleway (or I might use cycleway=no).--Florimondable (talk) 12:34, 25 February 2020 (UTC)
On the usage of oneway:bicycle=* versus cycleway=opposite, this is how it currently looks like:
oneway:bicycle versus cycleway=opposite
Data from, probably too early to call cycleway=opposite obsolete yet -- Emvee (talk) 09:23, 26 January 2020 (UTC)
More good news, the next version of JOSM will render oneway:bicycle the same as cycleway=opposite, see Changeset 15829 in josm -- Emvee (talk) 21:35, 8 February 2020 (UTC)