footways: highlight private ways

[plepe]

From: https://community.openstreetmap.org/t/openstreetbrowser-new-category-pedestrian-footways/6562/14

Derweil stellt sich mir aber noch die Frage, ob es nicht Sinn machen würde, Betretungsverbote (access=private zB) anzuzeigen? In der Gegend sind da ein paar, manche auch mit Gattern verschlossen, nicht unterscheidbar im overlay.

[hungerburg]

Beware that this might inspire future pleas to show surface &c. Access is very visible in OSM-Carto, but the overlay hides that. Carto also shows paving, but not so easy to spot. I might just switch on/off the filter in OpenStreetBrowser as a workaround, when interested in access/surface.

[plepe]

Filter is a good idea. I just published the change (3ee0925).

[hungerburg]

For what I want, this issue is solved. If this was Christmas eve, another filter for surface might be nice. Here how OSM Carto selects, https://github.com/gravitystorm/openstreetmap-carto/blob/aa35c89ec5fa0ae0413d0fb597164c8c5d2c997e/project.mml#L464 - No idea how many consumers consume this, but especially for path, this might be highly wanted information.

[plepe]

Sure, no problem. I added filters for 'surface' and 'smoothness'. For sidewalks mapped on the street (e.g. sidewalk=left or sidewalk:right=yes), a sidewalk:left:surface resp. sidewalk:right:smoothness will be queried.

(Commits f924be0 and ec100aa)

Other ideas?

[hungerburg]

The surface filter might want to match "sidewalk:surface=*" too, regardless of which side :) A grouping into paved/unpaved, like what OSM-Carto does might be nice too. But:

I do not care myselves that much about that, here sidewalk surface is always same as carriageway. This filter though made me stray into outer-urban areas. Footways after all exist there too! Will open separate issue.

[plepe]

Do you have thoughts about using surface as fallback for sidewalk:...:surface? https://community.openstreetmap.org/t/openstreetbrowser-new-category-footways/6562/27

[plepe]

I added sidewalk:surface (9406950) and sidewalk:smoothness.

I grouped paved and unpaved (in the filter available as "<paved>" and "<unpaved>") (ad5a322). Do you think, this is clear enough, or should I add another string (e.g. "all paved")?

[hungerburg]

I think the angle brackets convey very much, that these are not actual tag values but synthesized sets. If they follow the selection of OSM-Carto's, I see not need to further explicate. As OSM-Carto goes slow as molasses, but generally is argued quite precisely and very well founded in data, no objections here.

[plepe]

I followed the list on the Wiki surface page, which is almost identical to the list in OSM Carto.

• OSM Carto includes 'clay' in the unpaved list
• Key:Surface includes 'chipseal', 'stepping_stones' and 'rubber' in the paved list, 'rock' in the unpaved list.

I condensed both lists, so the lists now include all except 'stepping_stones' (which I do not really interpret as 'paved'):
https://github.com/plepe/openstreetbrowser-categories-main/blob/master/footways.yaml#L478-L482