My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
4.3.A. SR 02-14-2011
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2011 - 2020
>
2011
>
02-14-2011
>
4.3.A. SR 02-14-2011
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/11/2011 8:45:27 AM
Creation date
2/11/2011 8:43:59 AM
Metadata
Fields
Template:
City Government
type
SR
date
2/14/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
6
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
The attached figure shows the existing sight distances for drivers on Xavier Street who are <br />attempting to make a left turn to go west on 193` Avenue. The red line identifies the <br />current (1 /31 /11, after snow was removed) sight distances for both a driver stopped at the <br />stop bar and a driver who pulls ahead to the edge of the traveled lane. Similarly, the blue <br />lines identify the sight distance during the summer, when there is no snow limiting the line <br />of sight. In all cases the sight distance is less than the required 400-feet for this intersection. <br />The Minnesota Manual of Uniform Traffic Control Devises (MMUTCD) provides <br />`Guidance' and `Options' for the use of a 4-way stop to control intersections. The traffic <br />levels and vehicle speed have remained nearly the same now as they were during the traffic <br />study completed in May 2010, thus, not meeting the warrants according to the `Guidance' of <br />the manual. The `Options" described in the MMUTCD allow for the installation of a 4-way <br />stop if there is: <br />A) The need to control left-turn conflicts; <br />B) The need to control vehicle/pedestrian conflicts near locations that generate <br />high pedestrian volumes; <br />C) Locations where a road user, after stopping, cannot see conflicting traffic and <br />is not able to reasonably safely negotiate the intersection unless conflicting <br />cross traffic is also required to stop; and/or <br />D) An intersection of two residential neighborhood collector (through) streets <br />of similar design and operating characteristics where Multi-way stop control <br />would improve traffic operational characteristics of the intersection. <br />Based on this review, both Options A and C support the installation of a 4-way stop at this <br />intersection. I recommend the traffic control at this intersection be changed to a 4-way stop <br />condition in accordance with the standards set forth by the MMUTCD and the MnDOT <br />Road Design Manual. <br />Being this intersection is on the State Aid system and was installed using State Aid funds, I <br />have discussed this potential modification with the District State Aid Engineer. The State <br />does not have any objections with the installation of a 4-way stop in this location. <br />In discussing this change with the street department, the sign modifications can be <br />completed by city staff. The changes would include the removal of the pedestrian crossing <br />signage and replacement with stop and stop ahead signs placed in accordance with <br />MMUTCD layouts. The street department will remove and inventory the pedestrian <br />crossing signs for reuse elsewhere on the system in the future. The costs associated with the <br />signing modifications will be $451 and come from the street maintenance sign budget. <br />In addition to the new signage at and in advance of the intersection, temporary `traffic <br />control change ahead' signs will be placed to warn motorists of the change. These signs will <br />be left in place for a few months or until motorists get used to the change. The police <br />department will also be asked to spend some time near the intersection to help raise <br />awareness of the traffic control change. <br />N:\Public Bodies\City Council\Council RCA\Agenda Packet\02-142011\Engineering Update.docx <br />
The URL can be used to link to this page
Your browser does not support the video tag.