My WebLink
|
Help
|
About
|
Sign Out
ORD 1866
City of Pleasanton
>
CITY CLERK
>
ORDINANCES
>
1801 - 1900
>
ORD 1866
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/30/2023 4:24:07 PM
Creation date
9/25/2002 9:48:47 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
ORDINANCES
DOCUMENT DATE
9/3/2002
DOCUMENT NO
ORD 1866
DOCUMENT NAME
PONDEROSA HOMES
NOTES
PUD-18
Tags
Ordinance
Description:
Ordinance
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
35
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
139. <br /> <br />Storm drainage swales, gutters, inlets, outfalls, and channels not within the area of a <br />dedicated public street or public service easement approved by the City Engineer shall be <br />privately maintained by the property owner. The developer shall install a structural control. <br />such as an oil/water separator, sand filter, or approved equal on the site to intercept and <br />pretreat storm water prior to reaching the storm drain. The design, locations, and a schedule <br />for maintaining the separator shall be submitted to the City Engineer/Director of Building <br />Inspection for review and approval prior to issuance of building permits. The structural <br />control shall be cleaned at least twice a year: once immediately prior to October 15 and once <br />in January. The developer shall enter into a maintenance agreement for the oil/water <br />separator prior to issuance of an occupancy permit for any portion of this development. The <br />developer shall label all on-site storm drain inlets with the wording, "No Dumping -- Drains <br />to Bay" using City-approved methods and materials. <br /> <br />140. <br /> <br />The developer shall design an on-site stormwater pretreatment and collection system that <br />includes, to the maximum extent feasible, on-site water pretreatment facilities, including <br />bioswales, micro-detention areas, permeable pavement, etc. The final layout and design of <br />these facilities shall be submitted for review with the review and approval of the Planning <br />Director and City Engineer prior to the approval of the final map. The goal shall be to <br />provide on-site pretreatment for a minimum of 85% of the project site. Bubbleup <br />pretreatment shall be used for pretreating water from the house roof leaders and lot area <br />drains and shall empty into the concave-shaped, turf planter strip. Additionally, the use of <br />permeable paving in the cabana club parking area shall be used, if feasible. <br /> <br />141. <br /> <br />The developer shall design and construct a storm drain system, (sized to include the entire <br />drainage basin between the project and Stanley Boulevard) along the east side of Martin <br />Avenue from Mohr Avenue to connect to the existing pipe stub-out located at the northern <br />end of Martin Avenue. The developer shall negotiate with Kaiser to obtain an easement for <br />the installation of the storm drain line and/or portions of a bioswale along the buffer area <br />between Martin Avenue and the Kaiser/Zone 7 property. The proposed design of these <br />improvements shall be subject to the review and approval of the Planning Director and City <br />Engineer. The developer may request pro-rata reimbursement from other benefiting <br />properties for the storm drain line/bioswale. <br /> <br />Development Plan Lapsing <br />142. This development plan shall be of no further validity and the project developer shall be <br /> required to submit the same or new development plan for City approval prior to development <br /> of the site in the event that the project developer fails to record a final map within two (2) <br /> years of this PUD Development Plan. <br /> <br />City Council Page 30 of 32 August 20, 2002 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.