My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CCP 02-26-2001
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2000-2009
>
2001
>
CCP 02-26-2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/8/2007 1:16:32 PM
Creation date
11/13/2006 2:36:10 PM
Metadata
Fields
Template:
General (2)
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
194
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 /> <br />. <br /> <br />. <br /> <br />f{?/% <br /> <br />For one or more queue lengths, the queue length exceeds the storage length, <br />which results in significant upstream traffic impacts. <br /> <br />The following guidelines were applied when conducting the traffic analysis and <br />identifying the need to consider roadway improvements or mitigation measures. <br /> <br />All intersections operating at a LOS E or F as a result of background traffic or <br />Site-generated traffic would be considered for roadway improvement or <br />mitigation measures. <br /> <br />However, not all intersection movements expected to be at a LOS E or F require <br />roadway improvements or mitigation measures. For example, if an individual <br />movement operates at a LOS E or F but has a low volume, the movement would <br />not be expected to significantly decrease the overall operation at the intersection. <br /> <br />Similarly, not all queue lengths that exceed storage lengths necessitate roadway <br />improvements or mitigation measures. For example, if a queue length exceeds the <br />storage length but by only a short distance, the queue would not be expected to <br />have a significant upstream impact. Or if the queue diminishes (clears out) <br />regularly throughout the peak hour, the movement would not be expected to <br />significantly disrupt upstream traffic. <br /> <br />In addition, if an intersection or a specific movement at an intersection warrants <br />consideration for mitigation due to the increased traffic volumes from a <br />development, improvements would be applied only to return the intersection or <br />specific movement back to the existing (background) traffic conditions. For <br />example. if a particular intersection operates at a LOS E under existing conditions <br />and LOS F with development volumes, mitigation measures would be considered <br />to return the intersection to a LOS E condition. Mitigation measures to improve <br />the intersection to an acceptable (LOS D) condition, which would be better than <br />the existing conditions, would not be considered. <br /> <br />Once a specific deficiency is identified that necessitates consideration for a roadway <br />improvement or mitigation measure, the following solutions are evaluated to reduce or <br />eliminate the deficiency: <br /> <br />Optimizing the intersection signal timing, adjusting the intersection phasing, <br />and/or reassigning the lane geometry; <br /> <br />Implementing geometric improvements, including adding through lanes, adding <br />turn lanes or lengthening turn lanes; <br /> <br />Suggesting ways to reduce the number of vehicles that use that intersection or individual <br />intersection movement. Such as directing vehicles to alternate routes or suggesting <br />alternate modes of transportation. <br /> <br />Walgreen's Traffic Impact Study <br />Draft Repon <br /> <br />Traffic Operations Methodology <br />February 07, 2001 <br /> <br />3-3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.