<html><head></head><body>The latter (after) version matches the traffic signal wiki <a href="http://wiki.openstreetmaps.org/wiki/Tag:highway%3Dtraffic_signals#Tag_all_incoming_ways">http://wiki.openstreetmaps.org/wiki/Tag:highway%3Dtraffic_signals#Tag_all_incoming_ways</a><br>
<br>
It makes sense to me and is the way I prefer.<br>
<br>
Tod<br>
<br>
-- <br>
Sent from my mobile device. Please excuse my brevity.<br><br><div class="gmail_quote">Martijn van Exel <martijnv@telenav.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi all,<br /><br />Here at Telenav we have been looking at complex intersections and we<br />have set about editing some of these intersections in a way we feel<br />represents the situation on the ground better than their original<br />state, and because of that, works better for us. We have received some<br />feedback on our edits so we wanted to take a step back and see what we<br />(as the OSM community) think is the preferred way to map these<br />intersections.<br /><br />So what are we talking about? Intersections like this one, where one<br />or more dual carriageways come together at an at-grade intersection:<br /><br /><a href="https://www.evernote.com/shard/s9/sh/6438c196-bb92-4f66-81dc-9b75186286ba/0e8f07ff527c6a85c0dec426b9b79f1e">https://www.evernote.com/shard/s9/sh/6438c196-bb92-4f66-81dc-9b75186286ba/0e8f07ff527c6a85c0dec426b9b79f1e</a><br /><br />One of my colleagues at Telenav has remapped this intersection as follows:<br /><br /><a
href="https://www.evernote.com/shard/s9/sh/3491f1fe-6afa-4571-bc43-7cb31c9c2625/9dd47d1445fdcf03d3f0bbd93b8e0f92">https://www.evernote.com/shard/s9/sh/3491f1fe-6afa-4571-bc43-7cb31c9c2625/9dd47d1445fdcf03d3f0bbd93b8e0f92</a><br /><br />The main difference, and the source of some feedback we have received<br />over the past few days, is that the dual carriageway roads are<br />straightened out, creating multiple intersection nodes (4 in this<br />case) instead of the original single intersection node that connects<br />all the incoming and outgoing ways. That technique turns out to yield<br />more reliable and correct routing and guidance ('keep left, turn<br />right') through these intersections in our testing. But of course,<br />that cannot dictate how we map as a community, so let's discuss.<br /><br />Some of the feedback we have received about these edits points to a<br />statement on this wiki page:<br /><a
href="https://wiki.openstreetmap.org/wiki/TIGER_fixup#Braided_streets">https://wiki.openstreetmap.org/wiki/TIGER_fixup#Braided_streets</a>: 'It<br />is a reasonable and well-used technique to bring the ways of dual<br />carriageways back to a single point at intersections to facilitate and<br />simplify the mapping of control devices and turn restrictions.' In my<br />mapping across the US, my personal experience has been that this<br />technique is in fact used, but the 'after' technique with straightened<br />out ways is actually much more common. I personally prefer that<br />technique as well - I think it is more pleasing to the eye, represents<br />what is on the ground better, and is and easier to read. So my feeling<br />was that this mapping practice would not be disputed. It turns out I<br />was wrong, so I want to see what the consensus is on mapping<br />intersections of this type - or perhaps there is none and we can work<br />together to get there?<br /><br />Tha
nks,<br
/>Martijn<br />--<br />Martijn van Exel<br />OSM data specialist<br />Telenav<br /><a href="http://www.osm.org/user/mvexel">http://www.osm.org/user/mvexel</a><br /><a href="http://wiki.openstreetmap.org/wiki/User:Mvexel">http://wiki.openstreetmap.org/wiki/User:Mvexel</a><br /><a href="http://hdyc.neis-one.org/?mvexel">http://hdyc.neis-one.org/?mvexel</a><br /><br /><hr /><br />Talk-us mailing list<br />Talk-us@openstreetmap.org<br /><a href="https://lists.openstreetmap.org/listinfo/talk-us">https://lists.openstreetmap.org/listinfo/talk-us</a><br /></pre></blockquote></div></body></html>