My WebLink
|
Help
|
About
|
Sign Out
SR 05:276
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2005
>
SR 05:276
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/13/2005 12:44:11 PM
Creation date
9/30/2005 3:06:29 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT DATE
10/4/2005
DESTRUCT DATE
15 Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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 /> Vineyard Avenue Resurfacing and Narrowing East of Bernal Avenue <br /> The 1996 General Plan shows Vineyard Avenue from Bernal Avenue to a point 4,000' to the <br /> east as a 4-lane divided road. The Vineyard A venue Corridor Specific Plan included the <br /> possible narrowing of Vineyard Avenue to two lanes between Bernal Avenue and Montevino <br /> Drive as part of the traffic calming plan to reduce cut-through traffic and noise near <br /> surrounding neighborhoods. The plan also included the repaving of this section of Vineyard <br /> Avenue with new materials that help reduce traffic noise. <br /> In February of 2003, City Council approved the temporary striping of Vineyard Avenue as a <br /> 2-lane roadway with improved median areas for traffic exiting Touriga Drive and increased <br /> pedestrian safety. This test was recommended by staff so that feedback could be gathered <br /> from the community prior to beginning design work on the roadway overlay and landscaped <br /> median project. <br /> The majority of comments received by traffic staff support the existing 2-lane Vineyard <br /> A venue operation with comments that this layout has reduced traffic noise and has improved <br /> egress from Touriga Drive. Staff has not noticed any increase in queuing or congestion with <br /> the 2-lane roadway striping, and vehicle speeds have been reduced slightly even with the <br /> removal of the 4-way stop at Montevino Drive. If City Council determines that staff should <br /> proceed with the design of a 2-lane Vineyard A venue rubberized asphalt resurfacing project <br /> with wide landscaped medians at this time, staff has selected a consultant subject to City <br /> Council approval, and staff will work with local residents to refme the median design to <br /> optimize traffic flow, vehicle and pedestrian safety, and aesthetics along the corridor. <br /> Vineyard Avenue resurfacing options: <br /> 1) Wait until the General Plan Update is completed to determine if a 2 or 4-lane roadway <br /> is preferred. <br /> 2) Proceed with resurfacing the full roadway width with rubberized asphalt, but stripe <br /> roadway as 2-lanes with no raised median. There will be throw-away costs for <br /> removing the new rubberized asphalt in the median areas when the landscaped medians <br /> are constructed. <br /> 3) Preserve the right of way for four lanes, but resurface the street with rubberized asphalt <br /> with one lane in each direction and construct a wide landscaped median. This allows <br /> the savings from reducing the paved area to be spend on constructing the landscaped <br /> medians, eliminating throw-away costs. There will be some additional costs to mitigate <br /> drainage issues with the wider medians. <br /> 4) Resurface one lane in each direction and wait until the General Plan update is <br /> completed to decide on the size of the median, and number of lanes. Additional costs <br /> are expected, due to having to grind the existing surface so that the new pavement does <br /> not block drainage from the inside of the road. <br /> 5) Proceed with resurfacing the full roadway width with rubberized asphalt, stripe the <br /> roadway with two lanes in each direction and construct a standard landscaped median. <br /> SR:05:276 <br /> Page 8 of9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.