/ as wrong surface multi-value

[Marc-marc-marc]

Deprecated OSM Tag(s)

surface=value1/value2

Replacement OSM Tag(s)

surface=value1;value2

Link to OSM Wiki page

https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator

Further Information

No response

[matkoniecz]

Note that surface=value1;value2 does not really work either and is seems to be typically result of badly performed merges.

[Marc-marc-marc]

not only, also due to :

• bad value, for ex gravel;sand for compacted
• incomplete schema for example surface=concrete:lanes is incomplete for cargo bikes because the bike will ride in the middle of the 2 concrete strips and so some add the information of the central surface. there is also surface=asphalt-grass-asphalt which probably means the same thing although I haven't gone to look at the satellite views yet

but all this doesn't prevent using the right separator so that they can be more easily understood and detected when needed

[matkoniecz]

I would rather flag both of problematic. And I would not assume that gravel;sand is compacted - it may be as well surface=gravel road with a stretch which is surface=sand

[tyrasd]

dirt/sand

It would probably already help to reduce the usage of this particular combination, if we would filter out such values from the taginfo suggestions in the (surface) combo field.

For the existing cases of such tags (and also surface=…;…[^1]): That's probably best handled at external QA tools, isn't it?

[^1]: I saw some (presumably) valid use cases where e.g. a playground is mapped that has multiple different surfaces inside. Although the wiki is not very explicit if that's a valid way to tag.

[Marc-marc-marc]

dirt/sand

It would probably already help to reduce the usage of this particular combination, if we would filter out such values from the taginfo suggestions in the (surface) combo field.

indeed. how to do that ?