Opened 8 years ago
Closed 8 years ago
#10896 closed defect (fixed)
Validator rule: change needed for junction=yes
| Reported by: | sommerluk | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | 14.12 |
| Component: | Core validator | Version: | |
| Keywords: | Cc: |
Description
If you apply junction=yes on an OSM way without a “highway” key, the validator (before uploading to OSM) throws an error message: “junction without highway”. While this is fine for the “junction” key in general (junction=roundabout and so on), for the specific case of junction=yes this should not be checked (or, even better, do the opposite: throw an error if junction=yes and a “highway” key are on the same element).
Attachments (1)
Change History (10)
comment:1 Changed 8 years ago by
| Owner: | changed from team to sommerluk |
|---|---|
| Status: | new → needinfo |
comment:3 Changed 8 years ago by
| Owner: | changed from sommerluk to team |
|---|---|
| Status: | needinfo → new |
If you want, I can produce a “clean” .osm file just for demonstration (not taken from OSM database)…
comment:4 Changed 8 years ago by
| Milestone: | → 14.12 |
|---|
it's perfect thanks! Okay I didn't know this form of tagging.
comment:5 Changed 8 years ago by
| Component: | Core → Core validator |
|---|
Replying to sommerluk:
(or, even better, do the opposite: throw an error if junction=yes and a “highway” key are on the same element).
Would be wrong on nodes (e.g. highway=traffic_signals, junction=yes)
comment:6 follow-up: 7 Changed 8 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
In 7905/josm:
comment:7 Changed 8 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:8 Changed 8 years ago by
Woups. I was pretty sure the syntax [key!=value] implied the presence of key, looks like I'm wrong.
can you please attach (or link) a real-world example? Thanks.