<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div>16 Jan 2020, 02:22 by 61sundowner@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class="">On 16/1/20 12:08 pm, Paul Allen wrote:<br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">On Thu, 16 Jan 2020 at 00:49, Joseph Eisenberg
<<a href="mailto:joseph.eisenberg@gmail.com" rel="noopener noreferrer" target="_blank">joseph.eisenberg@gmail.com</a>>
wrote:<br></div><div class=""><blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex" class=""><div>I'm one of the
maintainers of the Openstreetmap-carto style, but I<br></div><div> think the community should make tagging decisions based on
what works<br></div><div> best for mappers and what makes logical sense, without
worrying what a<br></div><div> particular renderer will do.<br></div></blockquote><div><br></div><div>Ummm, but what makes sense depends upon what
popularly-used renderers<br></div><div>do, especially if there are two ways of doing things
which renderers treat<br></div><div>differently. If I map things that standard carto doesn't
show, I can't spot<br></div><div>my mistakes.<br></div></div></div></blockquote><p><br></p><p>If the 'standard map' starts rendering 'disused=yes' the same way
as 'disused:*=*' (presently not rendered) then what? <br></p></blockquote><div>Then standard map style will be fixed to<br></div><div>remove this bug.</div> </body>
</html>