My WebLink
|
Help
|
About
|
Sign Out
Home
Search
05-01-2017 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2017
>
05-01-2017 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/8/2018 10:58:52 AM
Creation date
5/2/2017 10:44:10 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
05/01/2017
Council Meeting Type
Work Session Regular
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
270
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 />Topographic Conditions: <br /> <br />The topographic conditions of the intersections are the physical features in the area, <br />including: <br /> <br /> • The grade of each approaching roadway <br /> • Location and size of adjacent buildings or structures <br /> • Angle of the intersection <br /> • Geometrics (number of lanes) of the intersection <br />• If a school, park or major pedestrian generator is located in the area <br /> <br />Intersection Control Policies: <br />When developing policies for stop sign controlled intersections, the traffic conditions and <br />topographic conditions are used in the analysis procedure. Additional, non-technical <br />factors may also be considered during the analysis procedure. Therefore, engineering <br />judgment is utilized when evaluating the appropriate intersection control. <br /> <br />Analysis Procedure: <br />The procedure for evaluating the need and location of stop sign control can be found in <br />the Minnesota Manual on Uniform Traffic Control Devices (MnMUTCD), Section 2B-5 <br />and 2B-7. Based on those warrants, the following two-way and all-way stop sign <br />installation procedures should be followed: <br /> <br />Step 1: Request for intersection control evaluation <br />This request can come from either a resident, the City Council, or from staff <br />observation of a particular intersection. If a request is made from a resident, a <br />signed petition of more than 80% of the households within a 300' radius of the <br />intersection, should accompany the request. <br /> <br />Step 2: Data collection <br />This step in the procedure involves collecting the data necessary to evaluate the <br />proposed 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 <br />hours of a typical day <br /> <br />Step 3: Initial evaluation <br />An initial evaluation of the intersection should be completed to determine if a <br />detailed intersection control study should be performed. This evaluation is <br />something that can be applied with minimal data (i.e., ADT traffic volumes, <br />accident history and roadway geometrics). This procedure is as follows:
The URL can be used to link to this page
Your browser does not support the video tag.