<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Thanks for diving in.   If it's a very minor unimproved road and not
    clearly service, I usually tag it track.   I would suggest adding
    some indication of road quality.   If it's an improved gravel road,
    I consider surface=gravel sufficient.   If it's rougher than an
    improved gravel road, surface=unpaved (in my area the surface is
    usually a mix of dirt, rocks, gravel, so unpaved seems best),   and
    smoothness=very_bad (high clearance), or horrible (4wd) 
    [<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Key:smoothness">https://wiki.openstreetmap.org/wiki/Key:smoothness</a>], or 
    4wd_only=yes .   <br>
    <br>
    The USFS motor vehicle use maps (MVUM) are very useful. <br>
    <br>
    I think most of the road signs say FS, and most of the tags in my
    area use FS, but the wiki
(<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/United_States_roads_tagging#National_Forest_Road_System">https://wiki.openstreetmap.org/wiki/United_States_roads_tagging#National_Forest_Road_System</a>)
    says to use FR .   I don't know the history, or if it really
    matters.  If someone is reading a map & it says FR or FS, they
    probably won't even notice.<br>
    <br>
    Keep this in mind when getting frustrated with the tiger data, I
    think we would have next to nothing if it didn't get imported.<br>
    <br>
    Brad<br>
    <br>
    <div class="moz-cite-prefix">On 7/19/20 5:50 PM, Dave Swarthout
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKWFYhXNb36nrpvZoqBfBdF38mZX1aegmoiHDVm2uja=VBYi-Q@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Mike, welcome to the real world. Tiger street data
        is better than nothing but not much. It's positionally
        inaccurate and many roads are wrongly classified. a rough guide
        at best. I do use the Tiger Roads 2019 overlay to add names to
        streets and roads though. The names are reasonably accurate in
        my experience.<br>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jul 20, 2020 at 5:57
          AM Mike Thompson <<a href="mailto:miketho16@gmail.com"
            moz-do-not-send="true">miketho16@gmail.com</a>> wrote:<br>
        </div>
        <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 dir="ltr"><br>
            </div>
            <br>
            <div class="gmail_quote">
              <div dir="ltr" class="gmail_attr">On Sun, Jul 19, 2020 at
                4:49 PM <<a href="mailto:tj-osmwiki@lowsnr.net"
                  target="_blank" moz-do-not-send="true">tj-osmwiki@lowsnr.net</a>>
                wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex"> For<br>
                roads that appear to be public access (e.g. to go to a
                lake) but are<br>
                obviously even more minor than tertiary roads I label
                highway=unclassified.<br>
              </blockquote>
              <div>highway=unclassified are for roads that connect small
                towns, or for "local traffic", while access to a lake
                could be considered "local traffic", I would think it
                would be better if these would be highway=service, or
                highway=track.<br>
              </div>
              <br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">
                <br>
                The US Topo map gives forest road references so I add
                ref FS xxxx.<br>
              </blockquote>
              <div>That is what I have been doing as well. Some are
                recommending that they be made into route relations,
                which I am starting to do. <br>
              </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">
                <br>
                TIGER seems to be at best very coarse, at worst
                fictional.<br>
              </blockquote>
              <div>+1 </div>
              <div><br>
              </div>
              <div>Mike<br>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          Talk-us mailing list<br>
          <a href="mailto:Talk-us@openstreetmap.org" target="_blank"
            moz-do-not-send="true">Talk-us@openstreetmap.org</a><br>
          <a href="https://lists.openstreetmap.org/listinfo/talk-us"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-us</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <br>
      -- <br>
      <div dir="ltr" class="gmail_signature">
        <div dir="ltr">Dave Swarthout<br>
          Homer, Alaska<br>
          Chiang Mai, Thailand<br>
          Travel Blog at <a href="http://dswarthout.blogspot.com"
            target="_blank" moz-do-not-send="true">http://dswarthout.blogspot.com</a></div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-us mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-us">https://lists.openstreetmap.org/listinfo/talk-us</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>