<div dir="ltr"><div>As someone who renders <a href="https://roadcurvature.com/map/">a driving-focused map</a> of [the most twisty] roadways, I specifically have done exactly what Volker describes (looking at highway=crossing nodes only). <br></div><div><br></div><div>To provide an example, my renderer walks down each vehicle-legal way and demotes the curviness weighting for a distance in each direction whenever it encounters a highway=crossing node on that way (or nodes with highway=stop, highway=traffic_signals, barrier=traffic_calming, etc). This particular map doesn't care about the geometry of footways, sidewalks, paths, or buildings, so it can look at a much reduced data-set of just vehicle-specific highways. If highway=crossing nodes aren't available and crossings are only indicated on intersecting ways, then I'd have to add a preprocessing step to build a list of all nodes that are members of a highway=crossing way and then add that to the list of nodes tagged with highway=crossing. I guess it's not an impossible task, but it is much more simple to just look at nodes that are also members of the vehicle-accessible highway ways.</div><div><br></div><div>I know OsmAnd can be configured to alert drivers of upcoming crossings (and stop signs), but do not know if that router works only with nodes on the ways of the current route or also does matching on crossing ways.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 15, 2020 at 1:06 PM Volker Schmidt <<a href="mailto:voschix@gmail.com">voschix@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I don't know what the routers need, to be honest.</div><div>I have adopted the approach happily because of the frequent two-stage approach. First the main road is mapped with foot/bicycle crossings as nodes , and at a later stage someone else may add the foot/cycleway details - I did not occur to me that there may be an advantage in removing at that stage the already existing crossing node. <br></div><div>I would also naively assume, that a car-only router does not need to inspect any of the foot/cycleways in the map, and can use the highway=crossing nodes as an indication to add small delays inthe routing.</div><div>Anyone in the router business listening in on this conversation?<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 15 Oct 2020 at 17:39, Jmapb via Tagging <<a href="mailto:tagging@openstreetmap.org" target="_blank">tagging@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 10/13/2020 6:30 PM, Kevin Kenny
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">On Tue, Oct 13, 2020, 17:41
Volker Schmidt <<a href="mailto:voschix@gmail.com" target="_blank">voschix@gmail.com</a>>
wrote:<br>
</div>
</div>
<div dir="auto"><br>
</div>
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div>I changed the crossing to the way we do it in many
parts of Europe, i.e. a crossing node <u>and</u> a
crossing way. This was described as an option on the
highway=crossing wiki page until it was changed on
07:52, 3 October 2020by user <a href="https://wiki.openstreetmap.org/wiki/User:Emvee" title="User:Emvee" rel="noreferrer" target="_blank">Emvee</a>
by addng the diagram and its description.<br>
</div>
<div><span></span>
</div>
<div>If you don't like it, please change it back - I
used it in place of a longish explanation.<br>
</div>
</div>
</div>
</blockquote>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Both of those are better, thanks! The routers
that I use for testing seem to be aware of crossings without
crossing nodes, so I too often forget to tag them.</div>
</div>
</blockquote>
<p>I've always been surprised to see a
footway=crossing/cycleway=crossing way with the intersection node
tagged as highway=crossing. There's only a single physical
crossing, so this seems contra to the one-feature-one-element
rule.</p>
<p>A highway=crossing node makes sense in an area without mapped
footways/cycleways. But if the crossing ways are mapped, routing
software will need to examine the intersection node and scan the
properties of all highways intersecting there. It seems to make
tagging the node itself redundant.</p>
<p>Are there really routers that require the node be tagged as well?<br>
</p>
<p>Jason<br>
</p>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>