Changes between Initial Version and Version 1 of Ticket #21235
- Timestamp:
- 2021-08-21T09:22:58+02:00 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #21235 – Description
initial v1 1 To resolve #10851, #10976, #15439, and #19389 the validator checks if ways have footway=* set with one of the values typically used for sidewalk=*. This seems to be a fairly common mistake, so it's good to have a warning here. 1 To resolve #10851, #10976, #15439, and #19389 the validator checks if ways have `footway=*` set with one of the values typically used for `sidewalk=*`. This seems to be a fairly common mistake, so it's good to have a warning here. 2 2 3 3 == Issues == … … 9 9 The validator checks for `left`, `right`, `both`, `none`, and `no`. `separate` is missing from this list. 10 10 11 === Treat `no` and `none` equally ===11 === Doesn't treat `no` and `none` equally === 12 12 13 13 The validator treats `none` in a different manner as the rest; giving users the suggestion to use `sidewalk=no` instead. Currently the documentation on the wiki and TagInfo (https://taginfo.openstreetmap.org/keys/sidewalk#values) show that these are now treated as synonyms, with no preference for one or the other. It doesn't seem necessary for JOSM to have a preference one way or another, especially if mappers are simply using what other local mappers do. 14 14 15 === Stop whitelisting other`footway` values ===15 === Whitelists all other possible `footway` values === 16 16 17 17 While the above values are clear examples of misstagging, `footway` is not an invalid key, and is used to provide a refining of `highway=footway`. The validator acknowledges this for `access_aisle`, `crossing`, and `sidewalk`, but excludes everything else. This seems too strict compared to the other rules — we don't whitelist values for `highway=*` for example. Mappers can (and do) create new values, and some are gaining broader acceptance. This check seems superfluous with the checks for values that probably mean `sidewalk=*` in place.


