<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I actually mentioned the issue in Milano. <br>
    </p>
    <p>Essentially traffic_sign, traffic_sign:forward and
      traffic_sign:backward need to be treated as "object" tags as
      things are now.<br>
    </p>
    <p>See pages 29 and 30
      <a class="moz-txt-link-freetext" href="https://drive.google.com/open?id=1LVmZIaEvd1K7mYVqDLnrhC5-jHLHy0lQ">https://drive.google.com/open?id=1LVmZIaEvd1K7mYVqDLnrhC5-jHLHy0lQ</a><br>
    </p>
    <p>And I should note that iD has "plot" as such a key which is
      equally mysterious, but I couldn't quite convince myself to
      include in the list.</p>
    <p>Simon<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 28.09.2018 um 04:51 schrieb Bryan
      Housel:<br>
    </div>
    <blockquote type="cite"
      cite="mid:AF1A4661-6ECC-4196-81B4-00F87F140CDA@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Hey Tagging List!
      <div class=""><br class="">
      </div>
      <div class="">While reviewing a pull request to add Traffic Sign
        presets to iD, I came across a tagging issue with how traffic
        sign directions are tagged.<br class="">
        <div class="">
          <div class="">The details are here <a
              href="https://github.com/openstreetmap/iD/pull/5333"
              class="" moz-do-not-send="true">https://github.com/openstreetmap/iD/pull/5333</a> and
            relevant guidance on the OSM wiki is quoted below:<span class="Apple-tab-span" style="white-space: pre;"> </span></div>
        </div>
      </div>
      <div class=""><br class="">
      </div>
      <div class="">
        <blockquote type="cite" class=""><b class="">Traffic sign as a
            separate node</b></blockquote>
        <blockquote type="cite" class=""><a
href="https://wiki.openstreetmap.org/wiki/Key:traffic_sign#As_a_separate_node"
            class="" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:traffic_sign#As_a_separate_node</a><br
            class="">
        </blockquote>
        <blockquote type="cite" class="">Create a separate node beside
          the road at the position of the actual sign... You can use
          the `direction=*` tag to describe the facing orientation of
          the sign by using an angle or cardinal direction.<br class="">
        </blockquote>
        <div class=""><br class="">
        </div>
        ^ This is ok!  iD supports `direction=*` and will even render a
        view cone at higher zooms so mappers can see which direction it
        points.</div>
      <div class=""><br class="">
        <blockquote type="cite" class=""><b class="">Traffic sign along
            a way</b></blockquote>
        <blockquote type="cite" class=""><a
href="https://wiki.openstreetmap.org/wiki/Key:traffic_sign#As_part_of_a_way"
            class="" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:traffic_sign#As_part_of_a_way</a><br
            class="">
        </blockquote>
        <blockquote type="cite" class="">Create a new node within the
          relevant way next to the sign... You can
          use `traffic_sign:forward=*` to specify that this sign affects
          vehicles moving in the same direction as the OSM way. The
          opposite direction can be tagged
          with `traffic_sign:backward=*`. Formerly the `direction=*` key
          has also been used to describe the affected direction. But its
          common meaning has changed to Relative to Geographic North.<br
            class="">
        </blockquote>
        <br class="">
      </div>
      <div class="">^ This is the problem.  The wiki says we are
        supposed to do something like `traffic_sign:forward=US:R1`, and
        we can't really do that. A preset needs to be based on a
        "toplevel" tag
like `traffic_sign=*` not `traffic_sign:forward=*` or `traffic_sign:backward=*` (remember
        seamark? many of their tags have this issue too, where they put
        a value in the key part, and so we can’t turn it into a preset).<br
          class="">
        <br class="">
        So instead what we’ve decided to do is:  Support a tag
        `traffic_sign:direction` which works exactly the same as the
        existing and well supported `traffic_signals:direction`</div>
      <div class=""><br class="">
      </div>
      <div class="">See <a
          href="https://wiki.openstreetmap.org/wiki/Key:traffic_signals:direction"
          class="" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:traffic_signals:direction</a></div>
      <div class="">iD already has support for
         `traffic_signals:direction=forward/backward`</div>
      <div class=""><br class="">
      </div>
      <div class="">To keep things simple, we'll do the same thing for
        traffic signs:<br class="">
        `traffic_sign:direction=forward/backward`<br class="">
        <br class="">
      </div>
      <div class="">Thanks,</div>
      <div class="">Bryan</div>
      <div class=""><br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>