My WebLink
|
Help
|
About
|
Sign Out
PC 082714
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
2010-2019
>
2014
>
PC 082714
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/10/2017 4:20:55 PM
Creation date
8/10/2017 4:17:02 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
8/27/2014
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
44
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
C. PUD -25, Mike Meyer /Tim Quinn, Greenbriar Homes, Lund Ranch II <br />Review and provide comments on the Revised Draft Environmental Impact <br />Report (July 2014) for the Lund Ranch II Planned Unit Development, a <br />proposed 50 -lot residential development located at 1500 Lund Ranch Road <br />(end of Lund Ranch Road). Zoning for the property is PUD- LDR/OS <br />(Planned Unit Development — Low Density Residential /Open Space) <br />District. <br />Chair O'Connor recused himself due to a conflict of interest. Commissioner Allen <br />chaired the discussion. <br />Mr. Dolan started by stating that he would like to take this opportunity to repeat the <br />announcement he made earlier regarding the purpose of this hearing, reiterating that it <br />is not a public hearing on the project, but rather, essentially the Planning Commission <br />hosting a meeting where people can submit and give comments on the adequacy of the <br />Environmental Impact Report (EIR). He stated that comments about which alternative <br />is preferred will be useful to staff at the public hearing on the project. <br />Mr. Dolan stated that staff will respond to comments on the EIR in writing and will not be <br />responding to the comments tonight. He indicated that a full, thoughtful, written <br />response on any comment that addresses the adequacy of the EIR will be given, <br />identifying the speaker or the comment, followed by a response. He noted that <br />sometimes the response would be a change in the EIR, and at other times, it is an <br />expansion of some explanation about certain sections of the EIR. He stated that it is a <br />somewhat limited scope and that he recognizes that it is sometimes difficult to <br />distinguish the difference. He asked everyone to do their best to try and focus on the <br />EIR. <br />Marion Pavan presented the staff report and stated that the comments will be <br />addressed in the Response to Comments, which, combined with the Revised Draft EIR, <br />would comprise the Final EIR, which includes revisions to the text as well as a <br />Mitigation Monitoring and Reporting Program which is required by CEQA. He indicated <br />that the EIR is an information document only and addresses environmental impacts, <br />mitigation, impacts that cannot be mitigated, and alternatives. He stated that the <br />purpose of the EIR is to fulfill CEQA requirements by addressing the environmental <br />impacts of the project; it does not constitute approval or rejection of the project. <br />Mr. Pavan stated that approving the Final EIR or finding it complete for CEQA purposes <br />does not compel the City to approve the project; the City can still deny the project. He <br />added that approved Mitigation Measures must be incorporated in the project either as <br />revisions to the design or as part of the Conditions of Approval. <br />Mr. Dolan reminded everyone that written comments are treated exactly the same as <br />comments made tonight. He noted that staff has received a number of written <br />comments, a lot of which are on the project and not on the EIR. He stated that these <br />will be saved and will be evaluated and submitted to the Commission. He added that <br />PLANNING COMMISSION MINUTES, August 27, 2014 Page 37 of 44 <br />
The URL can be used to link to this page
Your browser does not support the video tag.