My WebLink
|
Help
|
About
|
Sign Out
PC 062806
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
2000-2009
>
2006
>
PC 062806
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/5/2017 3:24:27 PM
Creation date
7/12/2007 9:42:15 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
6/28/2006
DOCUMENT NAME
PC 062806
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
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
~. In response to an inquiry by Commissioner Fox regazding the traffic report and the <br />number of students who walk on the street, Mr. Tassano replied that would be between <br />30-40 students. The volume of traffic would increase from 700 to 900. Consideration <br />was made in 2000 that the property owner was not favorable to any development or <br />modification at that time. Traffic Engineering and the Public Works Deparhnent, <br />however, prefen•ed to have the sidewalk. <br />In response to an inquiry by Commissioner Fox regarding the landscape maintenance <br />between the sidewalk and the street, Mr. Grubstick replied that the City maintained the <br />area. <br />Ms. Decker added that generally, homeowners associations were required to maintain <br />these landscaped azeas. There is no common azea for maintenance at this time. A <br />Maintenance Association would probably be formed for the stormwater pre-treatment <br />swales on the internal azea, and the landscape azea could be added to that scope of <br />responsibility. <br />In response to an inquiry by Chairperson Arkin regazding the mitigations for the removal <br />of the heritage trees, Ms. Decker replied that page 10 contained a condition requiring the <br />developer to comply with the recommendations of the tree report and that no tree shall be <br />removed other than those specifically designated by those on the approved plans. Trees <br />could be planted as a mitigation. <br />~~ Chairperson Arkin inquired whether the environmental review was accurate because it <br />was delayed due to the rezoning issue. He expressed concerns that the environmental <br />document appeared to be inadequate because the biotic survey was done on one day after <br />a heavy rainfall. He questioned if this was an accepted standazd and believed that more <br />work needed to be done. He voiced an interest in the survey being peer-reviewed at the <br />very least and believed that the project may need an Environmental Impact Report (EIR). <br />Ms. Harryman noted that the list of animal species known to occur on the site were listed <br />in Appendix A, and the plant species were not included due to the low diversity. <br />A discussion on the distinction between an EIR, a Negative Declazation, and a Mitigated <br />Negative Declaration ensued. <br />Ms. Decker noted that EIRs were done as a result of a level of significance of <br />environmental impact. She noted that this site did not have those particulaz adverse <br />effects that could not be mitigated according to the criteria for "threshold of significance" <br />as identified in the Negative Declaration and the biotic survey, for example. The <br />biologists felt that as a service of this report, it was assumed that impacts would be <br />focused with buildings, access roads, and other infrastructure. Minor modifications of <br />locations of this development would not require a reassessment of project impact. The <br />Initial Study process determined that a Negative Declazation would be adequate and <br />mitigation measures, if any impacts were determined, could be conditioned and mitigate <br />any concerns about the site. <br />PLANNING COMMISSION MINUTES June 28, 2006 Page 20 of 26 <br />
The URL can be used to link to this page
Your browser does not support the video tag.