Opened 7 years ago
Last modified 2 years ago
#17172 new enhancement
[WIP PATCH] turn:lanes and lanes should match
| Reported by: | taylor.smock | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | latest |
| Keywords: | mapcss lanes lanes-tagging | Cc: |
Description
We should ensure that lanes equals turn:lanes when turn:lanes exists. This also applies to the forward and backward variants.
Attachments (1)
Change History (6)
by , 7 years ago
| Attachment: | turn_lanes.patch added |
|---|
follow-up: 4 comment:1 by , 6 years ago
| Keywords: | lanes lanes-tagging added |
|---|
Be careful, there could be more turn:lanes than lanes if there is a bicycle lane.
True is that the number of turn:lanes should be equal or higher than lanes but that is true for all *:lanes-tags
comment:2 by , 6 years ago
The other thing to consider is that, pursuant the lanes specification, half-lanes are not counted. I'll have to rework this patch sometime for that.
comment:3 by , 6 years ago
| Summary: | [PATCH] turn:lanes and lanes should match → [WIP PATCH] turn:lanes and lanes should match |
|---|
follow-up: 5 comment:4 by , 2 years ago
Replying to skyper:
Be careful, there could be more
turn:lanesthanlanesif there is a bicycle lane.
True is that the number of
turn:lanesshould be equal or higher thanlanesbut that is true for all*:lanes-tags
Apparently the strict equality check found its way into JOSM at some point via a different patch, but I’m not sure when: #21725.
comment:5 by , 2 years ago
Replying to 1ec5:
Replying to skyper:
Be careful, there could be more
turn:lanesthanlanesif there is a bicycle lane.
True is that the number of
turn:lanesshould be equal or higher thanlanesbut that is true for all*:lanes-tags
Apparently the strict equality check found its way into JOSM at some point via a different patch, but I’m not sure when: #21725.
No, JOSM core is correct but the plugin turnlanes-tagging is damaging data.
mapcss checks for bad data