<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>May 6, 2021, 23:36 by ezekielf@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><span class=""><div dir="ltr">Tagging dual carriageway explicitly feels
a bit redundant since we draw two ways, but it would allow a rendering
variation and probably make some other things easier for data consumers.<br></div></span></div></blockquote><div>As someone who invented and started using this tag:<br></div><div><br></div><div>There is no reliable, automatic, known to me way to distinguish between <br></div><div>(1) oneway road<br></div><div>(2) road marked in OSM with oneway=yes and forming two-way dual carriageway<br></div><div><br></div><div>And I wanted this distinction for some purpose, and seemed to be within OSM scope<br></div><div>so I tagged it.<br></div><div><br></div><div>Recently AB Street ( <a href="https://github.com/a-b-street/abstreet">https://github.com/a-b-street/abstreet</a> ) become second known <br></div><div>to me user of that data, also because it aids road processing.<br></div> </body>
</html>