<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 21/05/2020 10:50, Mateusz Konieczny
via Tagging wrote:<br>
</div>
<blockquote type="cite" cite="mid:M7qd-Ke--3-2@tutanota.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<br>
<div>Similarly anyone creating<br>
</div>
<div>highway=footway + danger="you will be shot" + "access=no" +
foot=yes"<br>
</div>
<div>should probably switch to pickpocketing, telemarketing or
other less harmful activity.<br>
</div>
<br>
</blockquote>
<p>While "danger" isn't a much used tag (and I'm sure wasn't a
serious suggestion here -
<a class="moz-txt-link-freetext" href="https://taginfo.openstreetmap.org/keys/danger#values">https://taginfo.openstreetmap.org/keys/danger#values</a> ), sometimes
"foot=yes" is correct and other tags need to be taken into
account. I've used the area around
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/way/431056034">https://www.openstreetmap.org/way/431056034</a> as an example of that
before. Here "foot=yes" is correct - there is a legal right of
access. "<a title="The wiki description page for the sac_scale
tag" href="https://wiki.openstreetmap.org/wiki/Key:sac
scale?uselang=en-GB">sac_scale</a>=demanding_alpine_hiking" also
makes sense here I think.</p>
<p>I take Frederik's reference to Andy Allan's point about "a
multi-billion-dollar-revenue organisation that were rendering
anything with a highway tag the same as their most minor road
style" but frankly there's simply no solution to that - presumably
"highway=dangerouspath" (to make up a nonsensical value) or
<a class="moz-txt-link-freetext" href="https://taginfo.openstreetmap.org/tags/highway=via%20ferrata">https://taginfo.openstreetmap.org/tags/highway=via%20ferrata</a> would
still get shown as a "road".<br>
</p>
<p>Map styles need to be clear about what they're showing and what
they're not showing and people using maps need to be able to read
maps so that they understand what they're being told. This isn't
really a tagging issue, unless OSM mappers aren't using
appropriate other tags when they should (sac_scale,
trail_visibility, surface, etc.)</p>
<p>Best Regards,</p>
<p>Andy</p>
<p><br>
</p>
</body>
</html>