[PATCH] Stop whitelisting footway=*, and add footway=separate to blacklist candidates for sidewalk=*

[JeroenHoek]

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.

Issues

There are two minor issues with the current validation approach I would like to resolve.

footway=separate is missing

The validator checks for left, right, both, none, and no. separate is missing from this list.

Whitelist blocks all other possible footway values except for three

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.

Patch

In the attached patch:

• A check for footway=separate is added.
• The whitelist for footway=* is removed.

Are there any issues I am overlooking or reintroducing with this patch?

[skyper]

According to #21242, sidewalk=none should be replaced by sidewalk=no, so JOSM is correct with the special treatment.

[anonymous]

Really? This isn't reflected in the current documentation of sidewalk=*. I'm not seeing any recent mention on the Taggin-ML either.

I'm not opposed to deprecating sidewalk=none, but was this discussed somewhere else than on the Taggin-ML and the wiki-page for sidewalk=*?

[JeroenHoek]

(Comment by me.)

[anonymous]

Now OSM Wiki discussion appeared: ​https://wiki.openstreetmap.org/wiki/Talk:Key:sidewalk#Is_sidewalk.3Dnone_valid.3F

[mkoniecz]

that was me, sorry