Opened 5 years ago
Closed 5 years ago
#20974 closed defect (wontfix)
Validator reports suspicious tag combination for pedestrian area enclosed by barrier
| Reported by: | jpear1 | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | |
| Keywords: | pedestrian area barrier suspicious | Cc: |
Description
I encountered this issue trying to map a basketball court with a fence around it.
If you create an area with the three tags you need to use to mark a way as a fence and enclosing a pedestrian highway, you get a warning. I'll attach an example.
The three tags are:
highway=pedestrian
area=yes
barrier=fence
I'm pretty sure that this should actually be acceptable. The only warningless solution I can come up with is creating two nearly identical ways, one slightly smaller than the other, and tagging them separately, which doesn't feel very great to me.
I think that the validator should not report the barrier+highway tag as suspicious when the way has area=yes as explicit or implied by something like landuse=*.
Attachments (1)
Change History (4)
by , 5 years ago
| Attachment: | reproduce.osm added |
|---|
comment:1 by , 5 years ago
You need two objects in this situation as at least area=yes is ambiguous.
In my eyes, most primary tags should not be mixed and JOSM does not offer any of these combinations. See also my comment and follow-ups on #20924 about objects without area=*.
comment:2 by , 5 years ago
Ah alright. Thanks for the reply. Apparently I still haven't quite internalized the "One feature, one OSM element" ethos.
comment:3 by , 5 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |



minimal example that generates warning