<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Sep 24, 2020, 01:00 by baloo@ursamundi.org:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class=""><div class="" dir="ltr">On Wed, Sep 23, 2020 at 5:56 PM Andy Townsend <<a href="mailto:ajt1047@gmail.com" rel="noopener noreferrer" target="_blank">ajt1047@gmail.com</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div><p><br></p><div>On 23/09/2020 23:01, Paul Johnson
wrote:<br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class=""><div class="" dir="ltr">On Wed, Sep 23, 2020 at 4:37
PM stevea <<a target="_blank" href="mailto:steveaOSM@softworkers.com" rel="noopener noreferrer">steveaOSM@softworkers.com</a>>
wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="">Paul Johnson <<a target="_blank" href="mailto:baloo@ursamundi.org" rel="noopener noreferrer">baloo@ursamundi.org</a>> wrote: <br></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div>> 2. Tagging route information on ways. It's about a
decade too long at this point for ref=* on a way to be
completely disconnected from the entity the tag applies to:
That's why route relations exist. Biggest problem child on
this at the moment: OSM's own tilesets. Let's drop
rendering for ref=* on ways and just render the route
relations already, this and multipolygons are why relations
came to exist in the first place.<br></div><div> <br></div><div> Yes, 100% agreement. I think this is simply pure inertia
(the kind that says "broken process") on the part of
renderers.<br></div><div> <br></div><div> Can anybody (renderer authors included, maybe even
especially) are welcome to offer reasons why "the old
machinery" remains in place? Are there legacy use cases
that remain unclear to the wider community? Please tell us
here, if so.<br></div></blockquote></div></div></blockquote><p>The US is unusual in that it doesn't have a single ref per
section of road. Most places in OSM map what they see on the
ground, and the current OSM Carto rendering works just fine for
them<br></p></div></blockquote><div>Right up until there's more than one kind of route on the way. <br></div></div></div></blockquote><div>???<br></div><div><br></div><div>As far as I can see it also works fine, <br></div><div>see say <a href="https://www.openstreetmap.org/#map=17/50.08717/19.80950">https://www.openstreetmap.org/#map=17/50.08717/19.80950</a> <br></div><div>with ref=A4;7 and ref=S52;7<br></div><div><br></div><div>And in places where this rendering breaks due to large number of refs, rendering<br></div><div>from relations would also break<br></div><div><br></div><div>Rendering from ref on road and ref from relation would be displayed in exactly the same way,<br></div><div>so if current display is bad it would not be fixed by changing to rendering from relations<br></div><div><br></div><div><br></div> </body>
</html>