#19714 closed enhancement (fixed)
[PATCH] Visually differentiate barrier=city_wall left and right sides
Reported by: | gaben | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | 20.09 |
Component: | Internal mappaint style | Version: | latest |
Keywords: | Cc: |
Description
According to the wiki:
"Behaves same as natural=cliff, that is no crossing as left-right are different height. Lower side on right side of way direction.."
Currently, in JOSM, the left and right sides are not differentiated visually.
Attachments (1)
Change History (19)
follow-up: 3 comment:1 by , 4 years ago
comment:3 by , 4 years ago
Replying to skyper:
Needs to be added for special handling to the revert way action, too.
Oh, I didn't see your comment.
follow-up: 7 comment:5 by , 4 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
I don't know how to exclude the special case when two_sided=yes is tagged.
comment:6 by , 4 years ago
Milestone: | → 20.08 |
---|
comment:7 by , 4 years ago
Replying to Klumbumbus:
I don't know how to exclude the special case when two_sided=yes is tagged (regarding the way reverse warning).
Probably an extra check around here: https://josm.openstreetmap.de/browser/josm/trunk/src/org/openstreetmap/josm/actions/corrector/ReverseWayNoTagCorrector.java?rev=16939#L58
It would be ugly but could work.
comment:9 by , 4 years ago
Please explain what needs to be done (also related to the other tags of the tag corrector).
comment:10 by , 4 years ago
So far the code only checks for single tags, only, but in cases of barrier=city_wall
together with two_sided=yes
there should be no warning. So we need the possibility to exclude this combination.
comment:11 by , 4 years ago
Milestone: | 20.08 → 20.09 |
---|
follow-up: 13 comment:12 by , 4 years ago
I did a bit of research. Although the two_sided=yes
attribute used mostly only on city_walls but also on guard_rails, walls, kerbs and a few more. City_wall has over 4k, others <100 occurrences. I have a patch for city_wall only. Is it enough?
follow-up: 14 comment:13 by , 4 years ago
Replying to gaben:
I did a bit of research. Although the
two_sided=yes
attribute used mostly only on city_walls but also on guard_rails, walls, kerbs and a few more. City_wall has over 4k, others <100 occurrences. I have a patch for city_wall only. Is it enough?
Think patches are always welcome. Is it possible, to exclude two_sided=yes
, in general, no matter what the additional tags are? Are there any use cases where reverting the way directions is a problem?
by , 4 years ago
Attachment: | 19714v1_(WIP).patch added |
---|
Ignore directional ways which have two_sided=yes tag
comment:14 by , 4 years ago
Summary: | Visually differentiate barrier=city_wall left and right sides → [PATCH] Visually differentiate barrier=city_wall left and right sides |
---|
Replying to skyper:
Is it possible, to exclude
two_sided=yes
, in general, no matter what the additional tags are?
Absolutely. It's the easiest solution :)
Are there any use cases where reverting the way directions is a problem?
The patch only affects ways, which are directional + have two_sided=yes
tag. So probably not a problem.
comment:16 by , 4 years ago
Ah sorry, the ticket reference in the comment got an extra 0 at the end :(
-// two_sided=yes is a special (documented) barrier=city_wall attribute, see #197140 +// two_sided=yes is a special (documented) barrier=city_wall attribute, see #19714
source:trunk/src/org/openstreetmap/josm/actions/corrector/ReverseWayNoTagCorrector.java?rev=17023#L62
Needs to be added for special handling to the revert way action, too.