<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 6/12/2016 3:43 PM, Bryce Nesbitt
wrote:<br>
</div>
<blockquote
cite="mid:CAC9LFPeEOT+jSKmZayeA9S8ywyU1hMcWBHXcfttFher_27vGaw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">One of the great things about OSM, is
that it shows the informal social trails, cut through routes
and fence gaps.</div>
<div class="gmail_extra">One of the bad things about OSM, is
that it shows the informal social trails, cut through routes
and fence gaps.</div>
</div>
</blockquote>
<br>
+1<br>
<blockquote
cite="mid:CAC9LFPeEOT+jSKmZayeA9S8ywyU1hMcWBHXcfttFher_27vGaw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I've been mapping these highway=path,
informal=yes. I feel that <b>access=no</b> is <b>inappropriate</b>
in most cases,</div>
<div class="gmail_extra">as these trails are often fully legal
to travel on and in many cases tolerated by land managers
(note 1).</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">However: I'm disturbed by the knowledge
that when I map highway=path, informal=yes the majority of the
rendering tools will show it as a peer to a highway=path,
official=yes. I often try adding width=1 ft or some other
indication of a lesser status: but that usually misses the
point. The trails are different <i>because</i> they are not
created or maintained by the land manager, not because of any
true physical characteristic.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Thus, there's a rendering fix for this
issue. But quite frankly a totally new highway</div>
<div class="gmail_extra">tag would be a very direct route to
affecting the rendering nearly everywhere.</div>
</div>
</blockquote>
<br>
And that would make more problems .. the same as the conflict
between highway=path and highway=footway<br>
<br>
-1<br>
<br>
Making more tags to 'solve' a rendering issue may only result in the
renders resolving the new tag teh same as the previous tag, despite
the best efforts of tag definitions. <br>
</body>
</html>