<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <br>
    <br>
    <div class="moz-cite-prefix">On 13/01/2022 21:41, Brian M.
      Sperlongano wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMrfQx1TZUyBLcefX7VqSv2bRxeoWtNsBc_qeuJ51=OwcyanYA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Thu, Jan 13, 2022 at 4:21
            PM Dave F <<a href="mailto:davefoxfac63@btinternet.com"
              moz-do-not-send="true" class="moz-txt-link-freetext">davefoxfac63@btinternet.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> On 13/01/2022 18:30, Brian M. Sperlongano wrote:<br>
              <blockquote type="cite">
                <div dir="ltr">
                  <div class="gmail_quote">
                    <div dir="ltr" class="gmail_attr">On Thu, Jan 13,
                      2022 at 1:16 PM Dave F via Tagging <<a
                        href="mailto:tagging@openstreetmap.org"
                        target="_blank" moz-do-not-send="true"
                        class="moz-txt-link-freetext">tagging@openstreetmap.org</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"><br>
                      I'm intrigued by your Point 3.<br>
                      Please provide a link to it in OSM & details
                      of your rendering (Github, <br>
                      website?).<br>
                      <br>
                      DaveF<br>
                    </blockquote>
                    <div><br>
                    </div>
                    <div>The example is in the github link that Minh
                      provided:</div>
                    <div><a
                        href="https://github.com/ZeLonewolf/openstreetmap-americana/issues/79"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true"
                        class="moz-txt-link-freetext">https://github.com/ZeLonewolf/openstreetmap-americana/issues/79</a></div>
                  </div>
                </div>
              </blockquote>
              <br>
              Thanks for that, but it provides no info about this new
              rendering. You mentioned Opentilemaps. Is that what
              they're using?<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>This is getting deeper than the tagging list probably
            cares about, but yes, this renderer is using an OpenMapTiles
            / mapLibre vector tile stack, and the new version of
            OpenMapTiles that was released this month adds support for
            concurrent road route relations.  The behavior of
            OpenMapTiles with concurrent road route relations is that
            each way contains a list of routes that the way is a member
            of (regardless of role).  The front end renderer then takes
            that data and uses it to draw one or more highway shields. 
            The issue that prompted this discussion was that in a few
            places, shields were appearing on ramps TO a highway rather
            than just ON a highway.  This is because those ramps TO the
            highway were added to the road route relation.</div>
          <div><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>
              <blockquote type="cite">
                <div dir="ltr">
                  <div class="gmail_quote">
                    <div>I've just added a couple comments describing
                      the possible technical solutions to this issue as
                      well at the link one of the objects in question on
                      the map, which I'll also paste here:</div>
                    <div><a
                        href="https://www.openstreetmap.org/way/587338079"
                        target="_blank" moz-do-not-send="true"
                        class="moz-txt-link-freetext">https://www.openstreetmap.org/way/587338079</a></div>
                  </div>
                </div>
              </blockquote>
              <br>
              Cheers. That way is an 'exit from', not a 'link to' so it
              shouldn't be a member of the VT 15 relation. The roads
              heading to the V 15 should be included with link roles.</div>
          </blockquote>
          <div><br>
          </div>
          <div>You've contradicted yourself here.  First you say that
            way shouldn't be a member of the relation, and then you say
            it "should be included with link roles".  So it's not clear
            whether you favor including the ramps (with link roles) or
            whether you favor not making them members of the route
            relation. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Those roads are *oneway*. The one heading *away* from the route
    shouldn't be included because it's *not* a link *towards* the route
    relation.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMrfQx1TZUyBLcefX7VqSv2bRxeoWtNsBc_qeuJ51=OwcyanYA@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <div> </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div> However, this is a developer, not OSM database
              problem. They should have filter rules to remove any data
              they're not interested in. <br>
              <br>
              Your Point 3 - When you say 'Remove relation <code>link</code>
              memberships from the map' do you mean from their 
              rendering or OSM database? If the latter, I disagree.</div>
          </blockquote>
          <div><br>
          </div>
          <div>As a community renderer author, I feel that we have a
            special responsibility to:</div>
          <div>1. Render correctly when data is entered in correctly</div>
          <div>2. Render incorrectly when data is entered in incorrectly</div>
          <div><br>
          </div>
          <div>Intentionally rendering bad data badly provides
            appropriate feedback to the community resulting in better
            data for all users in the end.  I would necessarily take a
            different approach on a commercial product, where I would
            attempt to suppress mis-tagging rather than expose it.</div>
        </div>
      </div>
    </blockquote>
    <br>
    It appears there's nothing wrong with the OSM database in this case,
    All that's required is a couple of lines on your code to filter the
    data you don't require.<br>
    <br>
    DaveF<br>
  </body>
</html>