My WebLink
|
Help
|
About
|
Sign Out
PC-2004-13
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
RESOLUTIONS
>
2000-2009
>
2004
>
PC-2004-13
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/15/2006 9:32:30 AM
Creation date
3/16/2005 2:37:25 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
RESOLUTIONS
DOCUMENT DATE
2/11/2004
DOCUMENT NO
PC-2004-13
DOCUMENT NAME
PCUP-87
NOTES
VALLEY HUMANE SOCIETY
NOTES 3
5240 NEW BLDG, VARIANCE FOR SETBACK
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).
Show annotations
View images
View plain text
<br />62. Storm drainage swales, gutters, inlets, outfalls, and channels not within the area of a dedicated <br />public street or public service easement approved by the City Engineer shall be privately <br />maintained by the property owners. <br /> <br />63. The design of the on-site storm drainage system shall be subject to the review and approval of <br />the Chief Building Official. The applicant shall work with staff to ensure that measures are <br />taken to avoid drainage from the rear patio area from entering the arroyo, such as installing a <br />gutter at the edge of the patio. <br /> <br />64. Any damage to existing street improvements during construction on the subject property shall be <br />repaired to the satisfaction of the City Engineer at full expense to the project developer. This <br />shall include slurry seal, overlay, or street reconstruction if deemed warranted by the City <br />Engineer. <br /> <br />65. The project developer's contractor and sub-contractors shall obtain an encroachment permit from <br />the City Engineer prior to moving any construction equipment onto the site. <br /> <br />Urban Stormwater Runoff Requirements: <br /> <br />66. The project developer shall install the vegetative filter swale shown on the conceptual landscape <br />plan to intercept and pretreat storm water prior to reaching the storm drain. The design, <br />locations, and a schedule for maintaining the swale shall be submitted to the City Engineer/Chief <br />Building Official for review and approval prior to issuance of building permits. <br /> <br />67. The trash enclosure area shall be completely covered. An area drain shall be installed in the <br />enclosure area, which connects to the sanitary sewer. A structural control such as an oil/water <br />separator or sand filter shall be provided. No other area shall drain into the trash enclosure; a <br />berm shall be installed to prevent such drainage if found necessary by the City Engineer/Chief <br />Building Official. A sign shall be posted prohibiting the dumping of hazardous materials into the <br />sanitary sewer. The project developer shall notify the Dublin-San Ramon Services District <br />(DSRSD) upon installation of the sanitary connection; a copy ofthis notification shall be <br />provided to the Planning Department. <br /> <br />68. The project developer shall sweep or vacuum the parking Jot and sidewalks a minimum of once a <br />month and shall prevent the accumulation of litter and debris on the site. Corners and hard to <br />reach areas shall be swept manually. If sidewalks and/or the parking Jot are pressure washed, <br />debris must be trapped and collected to prevent entry into the storm drain system. No cleaning <br />agent may be discharged into the storm drain. If any cleaning agent or degreaser is used, wash <br />water must be collected and discharged to the sanitary sewer, subject to approval of the Dublin- <br />San Ramon Services District (DSRSD). <br /> <br />69. Bulk construction materials, stored outdoors that may contribute to the pollution of storm water <br />runoff, must be covered as deemed appropriate by the City Engineer/Chief Building Official. <br /> <br />, I <br />
The URL can be used to link to this page
Your browser does not support the video tag.