How to tag a oneside - both direction cycleway along a oneway street without seperate line?

Langlaeufer · 2022-11-09T11:42:17.590Z

How to tag a single-side both direction cycleway along a oneway street. There is only one cycleway that can be used in in both directions. I don’t want use a separate line because the cycleway is on the sidebord directly beside the road.

When I use the following OSMR and GraphHopper are routing only oneway (OsmAnd does it correct):

oneway=yes
cycleway:right=track
cycleway:right:oneway=no

I can add oneway:bicycle=no (this may solve the routing), but this I would understand this to allow cycling on the road in opposite direction.

cycleway:right=opposite_track sounds lika a oneway cycleway in opposite direction.

Am I misinterpreting the tags or are the routers not yet familiar with the new options?
(Please ignore the sidewalk and if it is segregated ore not - this does not matter for my question.)

Nadjita · 2022-11-09T11:52:17.642Z

My understanding is that oneway:bicycle=no is required for bicycle-traffic to go both ways, because oneway=yes applies to all vehicle traffic in general, not only on the carriageway. cycleway:right:oneway=no doesn’t “lift” the oneway=yes access limitation of the highway in general.

Mateusz_Konieczny · 2022-11-09T15:51:23.253Z

Langlaeufer:

I don’t want use a separate line because the cycleway is on the sidebord directly beside the road.

If it is physically separated from road then separate line is fine.

If it is not physically separated from road then cycleway:right=track is wrong anyway.

Langlaeufer · 2022-11-09T16:13:22.863Z

It is not a cycle lane but there is no more further structural separation than the curb of normal height.
I am aware that I may draw a separate line. But I find the graphical representation (since the path is on a bridge) to be too separating.

But this does not answer my question. The wiki says:

If there is only one cycle track, but it is designated to be used in both directions, add cycleway:right:oneway=no or cycleway:left:oneway=no respectively.

But this seems not to work for the two bicycle router on the OSM website.

Mateusz_Konieczny · 2022-11-09T16:25:42.470Z

Langlaeufer:

But this seems not to work for the two bicycle router on the OSM website.

this elaborate “lets tag this as property of road” tagging schemes often are hard/annoying to support, or not supported and otherwise fiddly

As far as I see it can be argued to be a correct tagging. You can try to check is it present in latest version of router and either report bug in router or ask to update version deployed to OSM website (I faintly remember that it runs with ancient config)

Langlaeufer · 2022-11-11T11:13:07.799Z

I opened an issue for GraphHopper here:

github.com/graphhopper/graphhopper

Routing against oneway on oneside - both direction cycle track.

opened 09:55AM - 11 Nov 22 UTC

closed 10:58AM - 11 Nov 22 UTC

Langlaeufer

It looks like there are problems with routing on cycleway=track against directio…n on oneway streets. Tagging: highway=primary oneway=yes cycleway:right=track cycleway:right:oneway=no (oneway:bicycle=no) Observation: Bicycle routing is only working in the direction of the oneway road. cycleway:right:oneway=no do not show any effect !!! I think this should be enough for 2 direction cycle routing! (oneway:bicycle=no also have no effect but maybe the dataset is still not updated after 2 days.) * https://graphhopper.com/maps/?point=52.423377%2C9.444177&point=52.424113%2C9.451455&profile=bike&layer=Omniscale * https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=52.42365%2C9.44420%3B52.42395%2C9.45180#map=17/52.42313/9.44668

But I guess it was not understud.

And for OSRM here:

github.com/Project-OSRM/osrm-backend

wrong costs for routing on a cycleway=track against oneway direction

opened 10:21AM - 11 Nov 22 UTC

Langlaeufer

Bug Report

Example: http://map.project-osrm.org/?z=17&center=52.422952%2C9.450999&loc=52.4…23383%2C9.444262&loc=52.424067%2C9.451488&hl=en&alt=0&srv=1 Tagging: highway=primary oneway=yes cycleway:right=track cycleway:right:oneway=no (later I added oneway:bicycle=no) Wrong cost for bicycle route -> wrong route: 500m same direction as oneway = 2 min (correct) 500m against oneway = 8 min WRONG! 1000 m (detour) = 7 min ("best" result from OSRM) Additional question: Would cycleway:right:oneway=no interpreted as oneway:bicycle=no or do I have to tag this explicitly?

Mateusz_Konieczny · 2022-11-11T11:17:36.348Z

Langlaeufer:

But I guess it was not understud.

well, it is a good idea to link documentation of tags - especially if their pages do not exist

If this tag is in use and has support among mappers you can document it at https://wiki.openstreetmap.org/wiki/Key:cycleway:right

Langlaeufer · 2022-11-11T11:54:07.409Z

I do not see any sence in having separate wike pages for documentation of cycleway, cycleway:right and cycleway:left.

Mateusz_Konieczny · 2022-11-11T12:00:56.035Z

it may be as simple as page being redirect or having definition and “for full description see page XYZ”

benefit is avoidance of “Where do you see this tagging documented?” answers and better support in various places (taginfo, tag linking from tag lists at OSM Website)

Langlaeufer · 2022-11-11T12:22:54.269Z

Maybe, I misunderstood you at first.
I mean cycleway:left:oneway and cycleway:right:oneway should redirect to cycleway:oneway.

Langlaeufer · 2022-11-11T12:29:17.479Z

Tag:cycleway=track - OpenStreetMap Wiki
Key:cycleway:right:oneway - OpenStreetMap Wiki
Key:cycleway:right:oneway - OpenStreetMap Wiki
https://wiki.openstreetmap.org/wiki/Key:cycleway:oneway

Langlaeufer · 2022-11-13T17:14:16.153Z

At the moment you have to add oneway:bicycle=no for routing against oneway of the carriageway. GraphHopper and OSRM do not evaluate cycleway:*:oneway.