<div dir="ltr"><div>Hi Paul <br></div>Thanks for the quick reaction - I knew you would reply.<br><div><div><div class="gmail_extra"><div class="gmail_quote"><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_extra"><div class="gmail_quote"><span class="gmail-"><div><br></div></span><div>Well, the shoulder wouldn't count as a lane (a bicycle lane would, however).  Not quite sure how to tag the bicycle use shoulder case (though I am aware that it is extremely common in the US), but if it were an actual, bicycle-only lane instead, assuming three lanes on a side with the right lane being bicycle only, and signage indicating that bicycles must use the bicycle lane:</div><div><br></div><div>lanes=3</div><div>oneway=yes</div><div>cycleway=lane</div><div>motor_vehicle:lanes=yes|yes|no</div><div>bicycle:lanes=no|no|designated</div></div></div></div></blockquote><div> </div><div>This does not reflect the real situation, which is the presence of an emergency stop lane for motor vehicles, which may be used by bicycles. It is different from a dedicated cycle lane, which is what your tagging describes.  I have seen and ysed a number of bicycle lanes in the US that "deserve" your tagging. <br></div><div>The shoulder=yes tag is being used a lot in combination with bicycle=yes<br><a href="http://overpass-turbo.eu/map.html?Q=%2F*%0AThis%20has%20been%20generated%20by%20the%20overpass-turbo%20wizard.%0AThe%20original%20search%20was%3A%0A%E2%80%9Cshoulder%3Dyes%20and%20bicycle%3Dyes%E2%80%9D%0A*%2F%0A%5Bout%3Ajson%5D%5Btimeout%3A25%5D%3B%0A%2F%2F%20gather%20results%0A(%0A%20%20%2F%2F%20query%20part%20for%3A%20%E2%80%9Cshoulder%3Dyes%20and%20bicycle%3Dyes%E2%80%9D%0A%20%20node%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A%20%20way%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A%20%20relation%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A)%3B%0A%2F%2F%20print%20results%0Aout%20body%3B%0A%3E%3B%0Aout%20skel%20qt%3B">http://overpass-turbo.eu/map.html?Q=%2F*%0AThis%20has%20been%20generated%20by%20the%20overpass-turbo%20wizard.%0AThe%20original%20search%20was%3A%0A%E2%80%9Cshoulder%3Dyes%20and%20bicycle%3Dyes%E2%80%9D%0A*%2F%0A%5Bout%3Ajson%5D%5Btimeout%3A25%5D%3B%0A%2F%2F%20gather%20results%0A(%0A%20%20%2F%2F%20query%20part%20for%3A%20%E2%80%9Cshoulder%3Dyes%20and%20bicycle%3Dyes%E2%80%9D%0A%20%20node%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A%20%20way%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A%20%20relation%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A)%3B%0A%2F%2F%20print%20results%0Aout%20body%3B%0A%3E%3B%0Aout%20skel%20qt%3B</a><br><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 class="gmail_extra"><div class="gmail_quote"><div><br></div><div>This may seem overkill to some people, but I'm aware of quite a few places where there's multiple bicycle lanes, where the bicycle lane is not the curb lane, and other arrangements that would otherwise just mess up lane guidance if you omit this and I've found fun edge cases in almost as many places as I've found bicycle lanes.</div></div></div></div></blockquote><div><br></div><div>That is OK, but, as I said , is different from the cases I am describing<br></div><div> </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 class="gmail_extra"><div class="gmail_quote"><span class="gmail-"><div> </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><div><div><div></div>(2) how to tag longitudinal rumble strips, <br>(situated between motorized-traffic lanes and shoulders, example: [1], not the "sleeping policeman" type that goes across the road nd which is normally tagged as traffic_calming=rumble_strip on a node of the highway)<br>To tag their presence is important because they represent an augmented protection of cyclists on the shoulder from cars invading the shoulder by mistake, i.e. reduced risk of being killed.<br></div>To note that I have encountered rumble-strip-separated shoulders also on roads below the rank of trunk or motorway</div></div></div></blockquote><div><br></div></span><div>I'm not quite sure how necessary it is at this point.  The kind of example you have provided is being phased out in favor of strips with gaps in them so bicyclists can get on and off the shoulder without dealing with the rumbles, or eliminated on roads with a narrow hard shoulder.  In both cases, for the reason for that is that not taking bicycles into account does more harm than good.  This is true even on routes that are normally closed to bicyclists except when police tell you to use it anyway (like Interstate 70 in Kansas). </div></div></div></div></blockquote><div>My point maybe was not clear enough: I would like to tag the longitudinal rumble strips, independently of whether they are continuous or interrupted, because I want to be able to classify route sections according to their level of bicycle safety. If I have a stretch of motorway with a shoulder, this same stretch is safer for bicycle use when a rumble strip is present than when it is not, because it reduces the risk of a motor vehicle invading the shoulder. <br></div><div><br></div><div><br></div><div>Volker <br></div></div><br></div></div></div></div>