Opened 4 years ago
Closed 4 years ago
#20488 closed enhancement (duplicate)
Show cycleway:left|right=opposite_lane
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
Streets where it is permitted to ride bicycles against one-way limits for cars often have lanes marked on the ground or even tracks separated by a kerb.
A simple cycleway=opposite_lane
is not enough to know, which side this is on. CyclOSM works around, by showing lanes/tracks on both sides of the street. That is wrong though.
To the rescue, cycleway:left=opposite_lane
(seems to be hardcoded in JOSM for the tag not specific to side) or cycleway:right=opposite_lane
- mostly depending on country wide rules (left/right-traffic).
Please display the side-specific versions. Taginfo shows, they are just as common as the unspecific version.
Attachments (0)
Change History (2)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Closed as duplicate of #20468.
A late explanation in the other issue makes this one moot. Closing as duplicate, because wontfix cannot be set by me and invalid is also not right.
Rationale: cycleway:left|right=opposite_lane|track|shared_lane|… would be a single tag for oneway:bicycle=no + cycleway:left|right=lane|track|shared_lane|… The availability of the two tags solution to the problem and its wide support by routers, editors and other consumers outweighs the shorthand notation by far. I do not see a reason for supporting this in my favourite editor any more. I'd even go so far as to ignore cycleway=opposite_* just the same, but that is another issue.
See also #20468 which requests to show a warning for this tag.