<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 6/6/20 9:24 AM, Paul Johnson wrote:<br>
<blockquote type="cite"
cite="mid:CAMPM96oNqRvBC2jgX451=Q6h+om8Emw2V_zKisvFH1y=0vT2gQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Sat, Jun 6, 2020 at 8:24 AM Mike Thompson <<a
href="mailto:miketho16@gmail.com" moz-do-not-send="true">miketho16@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>ref: <br>
</div>
<div>The wiki states that these should be ref=FR +
<what is on the sign>. In practice: <br>
</div>
<div>* ref:usfs=FS + <what is on the sign> <br>
</div>
<div>
<div>* ref=FS + <what is on the sign> <br>
</div>
<div>Most of the changesets that added a "ref:usfs" tag
include a very helpful comment that this issue was
discussed on the tagging list at sometime in the past
and that this was the consensus, e.g. [2]. If this
continues to be the consensus, can we change the
wiki? <br>
</div>
</div>
</div>
<br>
</blockquote>
<div><br>
</div>
<div>ref=FS <what's on the sign></div>
<div><br>
</div>
<div>Ultimately consider adding a route relation with
network=US:NSFR:Forest Name:FH/FR as well so we can finally
kill off route tagging on things that are not routes. Not
sure we really need the FH/FR distinction, however, since
within the same forest, they're all the same network: The 2
digit routes are major, the 3 digits are minor (like parking
lots and campgrounds) and the 4 digits are usually only
usable by log trucks and 4x4s. Trails are another matter.</div>
</div>
</div>
<br>
</blockquote>
I prefer ref=FS xxx too. I think the tagging discussion that
suggested ref:usfs was using that for the route relation.<br>
</body>
</html>