<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>Oct 18, 2020, 09:44 by tagging@openstreetmap.org:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On 15/10/2020 17:36, Jmapb via Tagging wrote:<br></div><blockquote><div>I've always been surprised to see a footway=crossing/cycleway=crossing<br></div><div>way with the intersection node tagged as highway=crossing. There's<br></div><div>only a single physical crossing, so this seems contra to the<br></div><div>one-feature-one-element rule.<br></div><div><br></div><div>A highway=crossing node makes sense in an area without mapped<br></div><div>footways/cycleways. But if the crossing ways are mapped, routing<br></div><div>software will need to examine the intersection node and scan the<br></div><div>properties of all highways intersecting there. It seems to make<br></div><div>tagging the node itself redundant.<br></div><div><br></div><div>Are there really routers that require the node be tagged as well?<br></div></blockquote><div>Routers do not need highway=crossing to detect crossings, every node<br></div><div>where 3 or more ways connect is a crossing.<br></div></blockquote><div>Note that there are multiple cases where 3 or more ways connect without<br></div><div>it being a crossing.<br></div><div><br></div><div>Even after "any case where 3 or more ways connect, with at least one being<br></div><div>a road and at least 2 being a footway/path/cycleway/footway" amendment<br></div><div>not all of them will be crossing (footway joining terminal node of road,<br></div><div>two footways joinining road on one side etc).<br></div><div><br></div><div>Crossing may be in situation where just one footway line joins road.<br></div><div><br></div> </body>
</html>