<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>It’s unlikely that any current routing engine will take change into account. Most current routing data consumers frankly suck.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Though that is no reason to not map accurate data.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The turn restriction relation has a higher chance of working, but again, may if not all routing data consumers either don’t support ways as via, or multiple via, or both.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But again, that is no reason to not map accurate data.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For proper lane tagging I would very very strongly suggest using JOSM and the “Lane and road attributes” map style, which does a very good job of visualizing all these :lanes tags, including change:lanes.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='mso-fareast-language:EN-AU'>From:</span></b><span lang=EN-US style='mso-fareast-language:EN-AU'> iansteer@iinet.net.au <iansteer@iinet.net.au> <br><b>Sent:</b> Saturday, 5 March 2022 14:40<br><b>To:</b> talk-au@openstreetmap.org<br><b>Subject:</b> Re: [talk-au] "Don't split ways if there is no physical separation"<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>Thanks for the tip about the “change” tag.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>So here is what I’ve done – does it sound right?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>- in the section where the slip lane joins the 2-lane through road (where lanes=3), I have added: “change:lanes=not_right|not_left| ” <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>(this hopefully means that the left hand lane cannot change lanes to the right, and the middle lane cannot change lanes to the left)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>- then in the next section where turn left and right slip lanes are added (where lanes=5), I have added” “change:lanes= |not_right|not_left|| ”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>(which hopefully means: the left slip lane can do as it pleases, the 2<sup>nd</sup> lane (the left-most of the 3 through lanes) cannot change right, the middle of the 3 through lanes cannot change left, and the other 2 right-most lanes can do as they please)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>I’d be very interested to see what a routing engine does at the point where the slip lane joins the 2 through lanes. That is, does it associate the slip lane with the left-most of the through lanes and hence know a vehicle can’t jump from the slip lane to the centre lane at the instant – or do the lanes go into a “melting pot” with no association? Similarly where lanes=3 changes to lanes=5 where the turn left and right slip lanes are added.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Ian<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>