My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CCP 04-14-2003
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2000-2009
>
2003
>
CCP 04-14-2003
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/8/2007 1:18:20 PM
Creation date
11/14/2006 2:35:14 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.
/
156
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 />Mr. Todd Mohagen <br />Mr. Tom Jacobson <br /> <br />-5- <br /> <br />March 7, 2003 <br /> <br />TRAFFIC ANALYSES <br /> <br />. <br /> <br />Level of Service <br /> <br />Capacity analyses were performed using the methodology presented in the 1997 Highway <br />Capacity Manual (HCM) for the existing and proposed conditions for the County Road <br />ElPine Tree Drive intersection and for the proposed exit-only drive onto County Road E. <br />Capacity Analysis results are presented in terms of level of service (LOS), which ranges <br />from A to F. The LOS is based on the extent of vehicle delay at the intersection. Level <br />of service A represents the best intersection operation, with very little delay for each <br />vehicle using the intersection. Level of service F represents the worst intersection <br />operation, with excessive delay. Level of service D or better operation is considered <br />acceptable in the Twin Cities area. <br /> <br />The capacity analyses were conducted for the p.m. peak hour. The level of service for <br />the County Road ElPine Tree Drive intersection for the existing conditions is a LOS B <br />and does not change with the proposed site development including the exit-only drive on <br />County Road E. The LOS for the proposed exit-only drive is a level of service D, which <br />is acceptable in the Twin Cities area. <br /> <br />Thus, an exit-only driveway can be provided to County Road E without causing any <br />traffic delay difficulties. <br /> <br />e <br /> <br />Oueue Length Analysis <br /> <br />Approximately 170 feet is available for stacking vehicles between Pine Tree Drive and <br />the proposed driveway. This separation is farther than the 150 feet distance between Pine <br />Tree Drive and the Wells-Fargo drive-through exit. <br /> <br />During the survey on Tuesday, February 18, 2003, we noted that a maximum of eight <br />vehicles were stopped in one eastbound lane west of Pine Tree Drive. This translates to a <br />queue of 160 feet. The average longest queue length for each traffic signal cycle was 100 <br />feet. The traffic volume increase due to the bank is very limited. Therefore, upon <br />completion of the bank, the worst case situation is the queue length may increase by one <br />vehicle. Thus, the maximum post-development queue length would be 180 feet with an <br />average queue length of a 120 feet. The 170 feet of queue space available with the <br />proposed driveway is greater than the average queue length and is almost the same length <br />as the maximum queue length. Thus, we have determined that only on rare occasions <br />will the queue of the eastbound vehicles on County Road E extend west to the proposed <br />driveway. Given the rare nature of this situation we believe that no serious interference <br />will occur between the driveway and the queue of eastbound traffic on County Road E. <br /> <br />Safety Analvsis <br /> <br />Accident information for the years 2000, 2001, and 2002 was collected on County Road <br />E from the Highway 51 East Ramp to Lexington Avenue, including the accidents at the <br />intersection of Pine Tree Drive but not the intersections at the Highway 51 East Ramp or <br />Lexington Avenue. For the three year period, a total of27 accidents were reported along <br /> <br />e <br />
The URL can be used to link to this page
Your browser does not support the video tag.