<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>Apr 5, 2021, 16:40 by mail@jeroenhoek.nl:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On 05-04-2021 16:25, Mateusz Konieczny via Tagging wrote:<br></div><blockquote>Has anyone claimed that railway=preserved should be preserved?<br></blockquote><div><br></div><div>I've asked a mapper whose specialty is maintaining railways in the<br></div><div>Netherlands, and they indicated that the lack of rendering in Carto<br></div><div>holds them back from migrating to the newer standard. Carto has an issue:<br></div><div><br></div><div>https://github.com/gravitystorm/openstreetmap-carto/issues/2615<br></div><div><br></div><div>Would a patch that at least adds the same rendering as<br></div><div>`railway=preserved` for `railway=rail` + `railway:preserved=yes` be<br></div><div>accepted in Carto at this point?<br></div></blockquote><div>Note "Database layout change" part - right now this tag is not in a database<br></div><div>used for rendering :(<br></div><div><br></div><div>So it may require changing in database import definition and deployment will<br></div><div>be definitely delayed and/or more complicated.<br></div><div><br></div><div>Though it is also possible that OSM Carto has no need for yet another barely<br></div><div>distinguishable and unclear rendering difference, maybe railway=preserved<br></div><div>special rendering should be dropped?<br></div> </body>
</html>