My WebLink
|
Help
|
About
|
Sign Out
Home
Search
10-02-2017 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2017
>
10-02-2017 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2018 2:23:41 PM
Creation date
3/14/2018 12:14:46 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
10/02/2017
Council Meeting Type
Work Session Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
171
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
<br /> <br />Step 1: Request for intersection control evaluation <br />This request can come from either a resident, the City Council, the Traffic Safety <br />Committee, or from staff observation of a particular intersection. If a request is made <br />from a resident, a signed petition of more than 80% of the households within a 300' <br />radius of the intersection, must accompany the request. <br /> <br />Step 2: Data collection <br />This step in the procedure involves collecting the data necessary to evaluate the proposed <br />intersection control. The data required for each phase is listed below. <br />• Average Daily Traffic Volume data <br />• Traffic speed by approach <br />• Vehicle classification (number of trucks, etc.) <br />• Pedestrian volumes crossing all approached during peak periods <br />• Intersection topographic information <br />• Detailed crash data <br />• Detailed site visit viewing the intersection operations for the peak hours of <br />a typical day <br /> <br />Step 3: Initial evaluation <br />An initial evaluation of the intersection should be completed to determine if a detailed <br />intersection control study should be performed. This evaluation is something that can be <br />applied with minimal data (i.e., ADT traffic volumes, accident history and roadway <br />geometrics). This procedure is as follows: <br /> <br />A. Minimum traffic volume: If the daily (ADT) traffic volume approaches <br />the intersection on each leg adds up to more than 1,000 vehicles in a day, <br />the intersection is a candidate for an intersection control study <br />(EB+WB+NB+SB = 1000+) or, <br />B. Accident history: If there are more than two reported crashes per year in <br />the previous two years or, three accidents in the previous 12 month period, <br />of a type that is correctable with stop sign control (i.e. right angle or <br />turning in front of another vehicle), an intersection is a candidate for an <br />intersection control study. <br /> <br /> If the intersection does not meet these requirements no further study will be completed <br />without direction from the City’s Traffic Safety or City Council. A letter to the resident <br />requesting the information, outlining the findings will be sent by the City Engineer. This <br />letter will include the City’s policies for appeal of the engineer’s decision. <br /> <br />Step 4: Intersection Control Study <br />If the initial evaluation concludes that an intersection control study is necessary, the <br />following procedures will be followed to determine which type of traffic control is <br />required. <br /> <br />A. Intersection operation analysis: This would involve analyzing the <br />operation of the intersection using the current version of the Highway <br />Capacity Manual to determine the Level of Service and potential delays on <br />specific approaches. This analysis can be conducted for either a two-way <br />or four-way stop sign controlled intersection. <br />
The URL can be used to link to this page
Your browser does not support the video tag.