My WebLink
|
Help
|
About
|
Sign Out
12
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2017
>
030717
>
12
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/1/2017 3:00:33 PM
Creation date
3/1/2017 9:51:27 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
3/7/2017
DESTRUCT DATE
15Y
DOCUMENT NO
12
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
179
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
existing through volume of 434 vehicles, Owens Drive is well within the parameters for a <br /> single-lane operation. <br /> An example of a similar design and volume roadway in Pleasanton is Hopyard Road at <br /> Black Avenue. The Hopyard southbound lane design is identical to the existing <br /> eastbound Owens Drive design. Southbound Hopyard Road carries a similar daily <br /> volume of vehicles as eastbound Owens Drive, but carries a greater number of vehicles <br /> in both AM and PM peak hour compared to Owens Drive eastbound. The total <br /> intersection volume at Hopyard Road and Black Avenue (sum of all four approaches) is <br /> also similar to Owens Drive at Willow Road. <br /> Owens Drive Roadway Operation and Delay <br /> Although the traffic analysis showed that a single lane would be adequate given the <br /> existing and future volumes, drivers have experienced an increase in delay with the <br /> Owens Drive roadway reduction. <br /> This increase in delay stems from two separate conditions: <br /> Lane Reduction <br /> The first is an expected outcome of the lane reduction. It does take longer to process <br /> the eastbound vehicles through the intersection with only one lane. At the peak <br /> demand 12-16 eastbound cars may arrive at the intersection. Each car takes <br /> approximately two seconds to move through the intersection. With the single lane <br /> design, the last car (vehicle 16) will take around 32 seconds before it travels through the <br /> intersection. With the previous Owens Drive three lane design, the 16th vehicle would <br /> be sixth in line, as each lane would have five vehicles already waiting. As the sixth car <br /> back, it will take about 12 seconds for vehicle 16 to pass through the intersection. As a <br /> result, the single lane could increase an eastbound motorist delay by up to 20 seconds. <br /> This was shown in the modeling and represents an expected minor increase in delay. <br /> Iron Horse Trail Success <br /> The second reason for increased delay on Owens Drive was the result of the Iron Horse <br /> Trail signalized crossing and the (somewhat unexpected) heavy volume of peak hour <br /> pedestrians and bicyclists activating the crossing. <br /> While it was anticipated that the construction of the traffic signal at the Iron Horse Trail <br /> and the associated Iron Horse Trail improvements would increase the pedestrian and <br /> bicycle volume, the nearly 200 pedestrians/bicyclists in the peak hour is a larger number <br /> of people than expected. This volume of pedestrian/bicycle traffic created a nearly <br /> continuous activation of the Iron Horse Trail crossing. <br /> Each pedestrian activation stops Owens Drive traffic for 30 seconds (the time required <br /> for pedestrians to cross the eastbound lane, the median and the westbound lanes). The <br /> initial signal programming was very friendly to pedestrians allowing them to cross <br /> almost immediately after the button was pressed. This operation was acceptable during <br /> the majority of the day, but in the peak hour, the continuous pedestrian activations were <br /> not allowing sufficient time for the vehicle queues on Owens Drive to clear before <br /> Page 6 of 9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.