My WebLink
|
Help
|
About
|
Sign Out
CCMIN101805
City of Pleasanton
>
CITY CLERK
>
MINUTES
>
2000-2009
>
2005
>
CCMIN101805
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/17/2007 10:56:42 AM
Creation date
10/13/2005 11:47:24 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
10/18/2005
DOCUMENT NO
CCMIN101805
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
33
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 /> Mike Madden, a Pleasanton resident, spoke in favor of retaining the two roundabouts as <br /> they did an adequate job in reducing the speed on that stretch of the roadway. <br /> Chris Peterson, a Ruby Hill resident, pointed out while there is an expressed interest in <br /> the expense to remove the roundabouts, there is also an expressed interest in finding solutions <br /> to make the roundabouts work which will also be costly. She pointed out that large trucks could <br /> not negotiate the roundabouts and go over the middle of the roundabouts. She also pointed out <br /> that a rocky trail would not accommodate a road bicycle. She believed the roundabouts were <br /> not functional for bicyclists and supported the removal of the two roundabouts. <br /> Written communication was provided to Council from David Llewellyn, a Pleasanton <br /> resident, who supported the removal of the two existing roundabouts. He believed Pleasanton <br /> was on the verge of becoming the most traffic signal controlled city in the Bay Area and while it <br /> is positive to have coordinated traffic flow and reasonable speed limits, it has been taken too far. <br /> Mayor Hosterman closed the public comments. <br /> For the sake of discussion, Mayor Hosterman suggested Council bifurcate this matter <br /> and discuss and take action first on the traffic signal controlled crossing at Petronave Lane. <br /> Mr. Brozosky said Old Vineyard Avenue was intended to be a trail with a crossing and <br /> he understood the reason for the traffic signal; however, he expressed his concerns related to <br /> the safety of this signal. He was concerned that if the stop light was red for traffic on Vineyard <br /> going southbound, the next vehicle approaching the hill would not adequately see the backup of <br /> vehicles no matter what type of signage or flashing yellow light was used. He believed the <br /> design of this roadway was different than what was expected. He was hopeful that staff had a <br /> better solution to address this issue. <br /> Mr. Wilson said staff's solution was to try and provide as much advanced notification of <br /> the traffic signal as possible. The solutions are incorporated into the design of the traffic signal, <br /> which is a higher placed signal so people could see it from further back as well as the flashing <br /> yellow beacon. <br /> Mr. Brozosky believed an approaching vehicle would not see the vehicles that are <br /> backed up behind the signal. <br /> Mr. Wilson said staff did not anticipate the signal would turn red that frequently on <br /> Vineyard Avenue and when the signal turns red, there would not be a large backup and if there <br /> was a backup there is adequate site distance for an approaching vehicle. <br /> Mr. Brozosky agreed that the signal would turn red on Vineyard very infrequently unless <br /> the School is built and if the School is built, children coming from the Shadow Cliffs area would <br /> be using the crossing to get to the other side of Vineyard Avenue which would be during heavy <br /> commute hours. <br /> Mr. Sullivan inquired about the speed limit in that area of Vineyard Avenue. <br /> Mr. Wilson said the speed limit in that area of Vineyard Avenue is 40 mph. <br /> Pleasanton City Council 18 10/18/05 <br /> Minutes <br />
The URL can be used to link to this page
Your browser does not support the video tag.