On Fri, Feb 3, 2017 at 7:15 AM, Volker Schmidt wrote:
> Last fall I travelled by bike the ACA Route 66 westbound. Long stretches
> are on freeway/trunk shoulders.
> I think I know how to map shoulders:
> highway=motorway|trunk
> oneway=yes
> shoulder=right
> shoulder:surface= ...
> shoulder:width= ...
> shoulder:smoothness ...
>
> In the case of undivided roads:
> highway= ...
> oneway=no
> shoulder=right|left|both
> shoulder:surface= ... OR shoulder:right:surface= ... OR
> shoulder:left:surface=
> shoulder:width= ... OR shoulder:right:width= ... OR shoulder:left:width=
> shoulder:smoothness ... OR shoulder:right:smoothness= ... OR
> shoulder:left:smoothness=
>
Two questions arise:
>
>
>
> *(1) How to tag the bicycle access:*
> on the highway with bicycle=yes
> or restricted to the shoulder with the lane= tag: lane:bicycle=no|no|yes
> (in case of a two lane-plus-shoulder highway.
> Problem with the bicycle tagging on the shoulder only is that bicycle
> routing algorithms won't route you across access ramps, which are
> implicitly bicycle=no.
> In fact there is even a legal problem there: many freeways have signs:
> "bicycle use shoulder" which you cannot obey at the ramps.
>
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:
lanes=3
oneway=yes
cycleway=lane
motor_vehicle:lanes=yes|yes|no
bicycle:lanes=no|no|designated
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.
> (2) how to tag longitudinal rumble strips,
> (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)
> 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.
> To note that I have encountered rumble-strip-separated shoulders also on
> roads below the rank of trunk or motorway
>
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).
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
