My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5.2. SR 07-24-2000
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2000 - 2010
>
2000
>
07/24/2000
>
5.2. SR 07-24-2000
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:33:49 AM
Creation date
6/28/2004 1:21:40 PM
Metadata
Fields
Template:
City Government
type
SR
date
7/24/2000
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
118
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Locally, the standard width of a residential street in a new subdivision is 37-feet (measured back-of- <br />curb to back-of-curb). This allows two 8-foot travel lanes plus the mandatory 20-foot travel lane for' <br />emergency and large vehicles. A 29-foot width is allowed on low volume streets with a parking <br />prohibition on one side. The standard residential speed limit is 25 MPH. <br /> <br />A traffic calming program is also in place. Traffic calming is typically imposed with road humps <br />and otherwise unneeded STOP signs. A review of streets already inflicted with traffic calming <br />measures has shown that even 29-foot streets with two-sided parking have problems with excessive <br />traffic volumes or speeds. <br /> <br />The concern with traffic calming has led to a proposed policy allowing 29-foot streets with two-sided <br />parking as a new standard. Although developers are supportive of the lower construction costs and <br />larger lots resulting from the narrower streets, they believe that 29-feet is too narrow and usually <br />design 32-footers instead. The realtors report that potential homeowners are uncomfortable with <br />such narrow streets. <br /> <br />Traffic surveys have shown that the average travel speeds are about equal for the 29 and 32-foot <br />streets (e.g, 28 MPH) and the emergency services seem more willing to accept them. The 85th <br />percentile for the standard street design is 30 MPH. In Kuna, neither the trash truck drivers nor the <br />parcel delivery services have expressed a concern with 32-foot streets. We did find that some drivers <br />will park on the sidewalk if they think that the streets are too narrow. Either vertical curbs or small <br />planter strips can prevent this from happening. <br /> <br />Street Alignment <br /> <br />Similar to the narrower street sections, a curvilinear street alignment reduces the driver's sight <br />distance and tendencies to speed. Long straight streets seem to encourage speeding. A review of <br />streets already inflicted with traffic calming measures did not give us a clear picture of the effect of <br />street alignment. There are too many other variables to isolate that one design feature. <br /> <br />The local traffic calming program calls for road humps a minimum of 600-feet apart. With 600-feet <br />then as the goal for a maximum sight distance, the desired street curve radius was set at 350-feet. <br />Although a smaller radius would reduce speeds even further, developers had more difficulty <br />designing their subdivisions. The 350-foot goal seems to be an acceptable compromise between <br />speed control and ease of design. Intermediate tangent roadway sections of less than 600-feet appear <br />to provide the needed results. <br /> <br />Traffic surveys have shown that although 85th percentile of 27 MPH speed is very close to the 25 <br />MPH signed speed limit, the curved street appears to have stopped the number of drivers exceeding <br />the speed limit by more than 10 MPH. Because there are minimal problems with speeding, the 37- <br />foot street sections are acceptable with this design. <br /> <br />Chokers and Islands <br /> <br />Traffic chokers and median islands are alternative methods of restricting the width of both the travel <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.