Talk:Key:oneway:bicycle

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:

Data from https://taghistory.raifer.tech/, probably too early to call cycleway=opposite obsolete yet -- Emvee (talk) 09:23, 26 January 2020 (UTC)

As taghistory is not updating anymore, some numbers on more actual use:

Date	oneway:bicycle=no	cycleway=opposite
20200720	88 023	54 388

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)

Ooo, nice. My feature request got implemented :) Mateusz Konieczny (talk) 08:36, 7 September 2020 (UTC)

cycleway:left versus cycleway=opposite_*

Just updated the page to indicate it more popular to use cycleway:left=lane or cycleway:left=track instead of cycleway=opposite_lane or cycleway=opposite_track.

The numbers (Sep 2020):

	cycleway:right	cycleway:left	cycleway=opposite_*
lane	111 017	42 862	8 658
track	50 898	18 843	1 761
<taginfo>	link	link	link

So cycleway:left is a factor 5/10 more popular than the cycleway=opposite_* alternatives.

I am wondering if it is a good idea to remove the cycleway=opposite_* alternatives at all.

You are comparing uses of cycleway:right/left for all purposes, with values used solely for tagging bicycle contraflow. Mateusz Konieczny (talk) 08:34, 7 September 2020 (UTC)

I agree with Mateusz.

And there is a misinterpretation :

cycleway:left/right=lane just means there is a lane of the side of the road

cycleway:oneway=no means that cyclist has legal right to go both way

but both doesn’t mean that the left/right lane is the counterflow lane ! For this you can use cycleway:left/right:oneway=-1. --Florimondable (talk) 10:28, 7 September 2020 (UTC)

Note it is oneway:bicycle=no not cycleway:oneway=no. The counterflow lane is always against the normal direction or in some cases bidirectional. In both cases cyclist has the legal right to go both way so (access, to make it for routers easy) oneway:cycleway=no. To detail further the bicycle infrastructure cycleway tags are used and cycleway:left/right:oneway should be only be needed for bidirectional counter flow. -- Emvee (talk) 11:58, 7 September 2020 (UTC)

I’m sorry to say it again, but cycleway:left/right=lane/track has nothing to do with oneway:biycle! It should be removed from the page.--Florimondable (talk) 15:49, 7 September 2020 (UTC)

Yes, I like to keep infrastructure (cycleway) seperate from access (oneway), so from my viewpoint it is logical to look only at cycleway:left/right

You did not put the numbers for cycleway:left=track + oneway:bicycle=no versus cycleway=opposite_track (ref #2) on the page, only those for lane, what are those numbers? Furthermore if you like to go this way I think all valid variants of cycleway=lane/track should be taken into account, cycleway=*, cycleway:left=*, cycleway:right=* and cycleway:both=* -- Emvee (talk) 11:58, 7 September 2020 (UTC)

Counting also cycleway=*, cycleway:left=*, cycleway:right=* cycleway=opposite_lane is still more popular than bicycle=no + cycleway*=lane but bicycle=no + cycleway*=track is almost a factor 3 more popular than cycleway=opposite_track, see the new table below. -- Emvee (talk) 21:24, 14 September 2020 (UTC)

Statistics

As of 19 Sep 2020:

Infrastructure	cycleway=opposite*	oneway:bicycle=no + cycleway*=*
no track/lane	54169	91646 (-6356 -1161 -5184)
lane	8556	6356
shared_lane	N.A.	1161
track	1737	5184

With the Proposal:Deprecate cycleway=opposite family out, same as above but for 22 May 2025:

Infrastructure	cycleway=opposite*	oneway:bicycle=no + cycleway*=*
no track/lane	50837	163065 (-21335 -5461 -9050)
lane	5317	21335
shared_lane	N.A.	5461
track	891	9050