Flutterby™! : Sharrow placement

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Sharrow placement

2019-03-23 16:39:49.968839+00 by Dan Lyke 0 comments

Because I know it's gonna come up in local discussions, and I've linked to various studies about sharrows killing cyclists before: Manual on Uniform Traffic Control Devices (MUTCD) Chapter 9C on bicycle shared lane marking (sharrow) placement:

04     If used in a shared lane with on-street parallel parking, Shared Lane Markings should be placed so that the centers of the markings are at least 11 feet from the face of the curb, or from the edge of the pavement where there is no curb.

05     If used on a street without on-street parking that has an outside travel lane that is less than 14 feet wide, the centers of the Shared Lane Markings should be at least 4 feet from the face of the curb, or from the edge of the pavement where there is no curb.

California's version of the MUTCD notes:

04     If used in a shared lane with on-street parallel parking, if the effective lane width is 14 feet or greater, Shared Lane Markings should be placed so that the centers of the markings are at least 11 13 feet from the face of the curb, or from the edge of the pavement where there is no curb. If the effective lane width is less than 14 feet, the marking should be centered within the effective lane width. See Figure 9C-108(CA).

05     If used on a street without on-street parking that has an outside travel lane that is less than 14 feet wide, the centers of the Shared Lane Markings should be centered in the travel lane. If used on a street without on-street parking that has an outside travel lane whose width is 14 feet or greater, the shared lane markings should be centered at least 4 feet from the face of the curb, or from the edge of the pavement where there is no curb.

[ related topics: Interactive Drama Pedal Power Bicycling ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.