My WebLink
|
Help
|
About
|
Sign Out
PC 08/27/86
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
1980-1989
>
1986
>
PC 08/27/86
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/17/2017 11:04:48 AM
Creation date
4/23/2007 4:27:47 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
8/27/1986
DOCUMENT NAME
PC 08/27/86
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
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
Minutes <br />August 27, 1986 <br />Planning Commission <br />one half acre and larger. Residential projects on land <br />designated Low or Medium Density Residential should propose <br />densities generally consistent with the standards assumed for <br />buildout of the General Plan, as shown in Table II-4. Low or <br />Medium Density projects which propose densities greater than <br />those shown in Table II-4 should be zoned Planned Unit <br />development (PUD) and contain sufficient public amenities to <br />compensate for higher densities. Low and Medium Density <br />Residential projects may propose densities exceeding the maximum <br />on portions of the site provided that four conditions are met: <br />(1) that the property be zoned PUD (2) that the overall density <br />of the entire property not exceed the maximum allowed under the <br />General Plan designation, (3) that any portion of the property <br />not exceed 150% of the maximum allowed under the General Plan <br />designation for Medium Density and no limit for Low Density and <br />(4) that significant public amenities (such as parks, open space <br />or community facilities not shown on the General Plan Map) be <br />included in the project design to compensate for the higher <br />densities. Housing types with such increased densities shall be <br />sited to minimize adverse impacts on adjacent, developed <br />properties. The maximum density of High Density Residential <br />projects shall be determined by the underlying zoning <br />designation. Gross acres shall not include the area of a parcel <br />designated on the General Plan for non-developed uses (such as <br />parks, schools, arroyos, railroad rights-of-way, and other areas <br />designated for public health and safety or other <br />non-residential/commercial/industrial use); areas planned for <br />future streets and thoroughfares shall be included in "gross <br />acres." <br />The Planning Commission supported the added verbiage to take care <br />of existing approved developments as follows: <br />Page II-5, last paragraph: <br />"All existing development and projects receiving PUD approval <br />prior to the adoption of this General Plan shall be considered in <br />conformance with the density provisions of this Plan." <br />The Planning Commission supported the word "western" in place of <br />"eastern" in Program 12.2, page 5 of the staff report. <br />Commissioner Michelotti then asked if it is the intent of Program <br />14.1, page 5 of the staff report, to be a specific plan. Mr. Lee <br />indicated that it is the intent to call for a specific plan. <br />Commissioner Innes didn't see anything in the General Plan tying <br />developments to air quality, noise and traffic standards. <br />Mr. Lee stated that there are City standards for these items <br />already. <br />Commissioner Innes and Mr. Lee then addressed the number of <br />residential and commercial/office/industrial units approved, but <br />unbuilt in the City. Commissioner Innes acknowledged that the <br />impacts of these units are yet to be realized and desired some <br />measure to check the theories used at the time of approval. <br />- 10 - <br />_. _ __ __ _ ___ _ __ . _.,.._~.. ____.~.. _ . _ _ r <br />
The URL can be used to link to this page
Your browser does not support the video tag.