<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">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">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">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">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. </div><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><br></div><div>So the decision space here is quite simple. If there is a community consensus that roads which connect to a route, but aren't on a route, should be included in a route relation, then OpenMapTiles has a responsibility to exclude that data when marking which roads are part of a route (and I would have a PR posted quite quickly to accomplish this).</div><div><br></div><div>However, if we agree that such roads should NOT be part of a road route, then my intent would be to continue rendering them in that wrong location, in order to give feedback to mappers that there is a problem in the data.</div></div></div>