My WebLink
|
Help
|
About
|
Sign Out
22
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2019
>
061819
>
22
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/12/2019 3:46:43 PM
Creation date
6/12/2019 11:30:17 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
6/18/2019
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
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
necessary on private property to address issues with grades and drainage in some <br /> locations. <br /> Budget Impacts <br /> The total cost of the project is not really affected by the parking configuration preferred, <br /> as each option presented includes the retaining wall, concrete pedestrian walkway, <br /> asphalt paving, lighting, landscaping, etc. The cost calculation for each option is <br /> probably best considered in terms of cost per additional parking space above the 59 <br /> that are in the existing parking lot between Bernal and Abbie. The total cost of the <br /> project, including design, construction, project administration, etc. is estimated to be <br /> $3.2M. As discussed earlier in this report, the proposed design creates an additional 81 <br /> parking spaces, which equates to a cost of approximately $39,500 per space. The <br /> diagonal parking option would create an additional 31 spaces costing approximately <br /> $103,000 each. The mixed 90-degree and parallel parking option would create 48 <br /> spaces which would cost approximately $66,500 for each space. <br /> Staff's Recommendation <br /> The proposed design maximizes parking, while providing a bicycle and pedestrian <br /> concrete walkway that at several pinch points are still the same width as the entire <br /> FHAC parking lot concrete trail, and complies with the eight-foot minimum width <br /> requirements as indicated in the Bicycle and Pedestrian Master Plan, but without the <br /> recommended two-foot buffer on each side of the walkway. <br /> If City Council affirms the goal of the project is to create as much parking as is possible <br /> within this section of the corridor, it is recommended that staff be directed to continue <br /> with the development of the construction plans consistent with the 65 percent design. <br /> Council could also direct that as the design is finalized, staff explore ways to create as <br /> much bicycle/pedestrian width as possible. This is unlikely to result in more than a few <br /> inches, but there may be some items yet to be designed, such as the retaining wall <br /> which has been assumed to have a one-foot width to this point, but could be thinner if <br /> the structural design allows. Depending on the grade difference, landscaping widths <br /> may also be reduced a few inches. Alternatively, the square columns that provide some <br /> design "relief" to the face of the wall at the light poles could be reduced in size to gain a <br /> few inches. Although these changes are unlikely to result in any significant width <br /> increase, staff could report back to City Council with the final dimensions when the item <br /> is presented to Council to approve the construction award. <br /> If City Council determines that parking and bicycle/pedestrian improvements should be <br /> more balanced with respect to the available width for each, it is recommended that staff <br /> be directed to more fully develop the options presented in this report, or other options <br /> Council may wish explored, then report back to City Council for further direction. In this <br /> scenario, all work on the current design will cease. <br /> Page 9 of 10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.