<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 14, 2021, 08:57 by sfkeller@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><blockquote>So you want to use railway=rail;preserved ?<br></blockquote><div><br></div><div>For example.<br></div><blockquote><div>> Coming back to the proposal: Deprecating railway=preserved strenghtens the use of railway:preserved=yes<br></div><div> And that is why I am supporting it.<br></div></blockquote><div><br></div><div>"railway:preserved=yes" is only half of a boolean, containing only<br></div><div>"yes / true - no use of "no".<br></div><div>Help that OSM database does not get detrimented by such tags.<br></div><div>Don't miss out +30 years of data modeling as explained in the<br></div><div>Namespace wiki page [1].<br></div></blockquote><div>I consider railway:preserved=yes as highly preferrable to<br></div><div>railway=rail;preserved<br></div><div><br></div><div>It is much easier for mappers, editors, data processing,<br></div><div>documentation and basically everything else to handle it.<br></div><div><br></div><div>In addition treating railway tag is single valued has a long tradition.<br></div><div><br></div><div>I also see no problem with half of a boolean anyway.<br></div><div><br></div><div>And at last in theory it can be actually used with no value<br></div><div>in cases where it is beneficial to record it explicitly, similar<br></div><div>to oneway=no.<br></div><div><br></div><div>(and that is with ignoring that railway=rail;preserved would<br></div><div>break nearly all existing data consumers, starting from <br></div><div>JOSM mappaint, through iD presets, Default Map Style<br></div><div>and ending on Osmand)<br></div> </body>
</html>