My WebLink
|
Help
|
About
|
Sign Out
PC 022515
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
2010-2019
>
2015
>
PC 022515
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/10/2017 4:45:14 PM
Creation date
8/10/2017 4:27:32 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
2/25/2015
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
He added that it could be an issue because property rights would be taken away from the <br />developer, subject to a lawsuit. He added that the other thing which Chair Allen touched on <br />is that the community gets together and adopts a General Plan: the midpoint density for <br />the site is 81 units; people then invest in property and propose a development based on <br />what the City tells them is appropriate; and then the City changes it later. He pointed out <br />that it makes that case pretty interesting. <br />Ms. Harryman stated that Brian is referring to an inverse condemnation action that could be <br />brought by the property owner. She added that she does not know how that would fare but <br />that it would certainly be the concern. <br />Commissioner Nagler noted that, just coming to learn about this conversation, he thinks <br />Greenbriar and those who came before Greenbriar who tried to build this property have <br />done a terrific job of trying to comply with what is appropriate and feasible and available at <br />the time; and reducing the number of homes to 50 with Measure PP passing is obviously a <br />substantial compromise. He stated that he objected to the idea that there is some measure <br />of fairness that ought to be awarded to Greenbriar because of conditions or past <br />discussions or something that occurred prior to Greenbriar acquiring the property and that <br />somehow is now unfair to impose upon Greenbriar. He noted that that comes with the <br />property, with the discussion and the history, and the discussions with neighbors; all the <br />prior planning commitments and the private agreements between developers are part of the <br />project. He added that he cannot imagine that when Greenbriar purchased the property <br />and the rights to develop it, all these things were not taken into account as a risk benefit <br />calculation on deciding whether or not to put out the money to potentially develop this land. <br />Commissioner Nagler stated that he is making this point, possibly primarily to give himself <br />guidance if nothing else, that the decision is really about what is best for the affected <br />neighborhoods because, in fact, there is going to be some traffic, and there will be one or <br />two neighborhoods affected. He indicated that it appears to him that the Commission's job <br />is to try and do that in a measured way, recognizing current traffic flows, current densities, <br />construction of the streets, probable utilization, traffic patterns, and so forth, and what is <br />allowed under Measure PP. He stated that that is really the question and not whether or <br />not it is fair to the developer or being a slave to prior discussions. <br />3. Measure PP Interpretation <br />Measurinq Slope <br />Mr. Dolan stated that applying a slope averaging methodology, the limit of development <br />changed very little and so there did not seem to be any benefit in this particular case to be <br />less conservative. He added that staff can map a slope map but it will not change much. <br />Chair Allen inquired what the implication of the change is, if it means more homes, less <br />homes or higher homes. <br />PLANNING COMMISSION MINUTES, February 25, 2015 Page 38 of 46 <br />
The URL can be used to link to this page
Your browser does not support the video tag.