My WebLink
|
Help
|
About
|
Sign Out
CCMIN071596
City of Pleasanton
>
CITY CLERK
>
MINUTES
>
1990-1999
>
1996
>
CCMIN071596
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/26/2010 10:53:45 AM
Creation date
5/13/1999 10:42:48 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
7/15/1996
DESTRUCT DATE
PERMANENT
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).
View images
View plain text
Mr. Roush indicated that although the Minutes are not completed, Council does have a <br />resolution which incorporates staffs understanding of the substance of that motion. If that is <br />not correct, then the text of that part of the General Plan dealing with the Vineyard Avenue <br />Corridor can be changed. Staff has attempted to take the motion and put it into the written form <br />before you. <br /> <br /> Mr. Pico also clarified that there are various references to the Vineyard Avenue Corridor <br />throughout the Plan and Council took action on July 1 on the area based on the item on page <br />2 of the staff report. On July 9, there was a subsequent item that came up in another area that <br />affected the Vineyard Corridor. There has been every effort to be open and give the public the <br />chance to comment on the decisions. <br /> <br /> Ms. Mohr felt that when a specific plan is prepared, there is generally not the kind of <br />restraint like this unit cap. Staff is instructed to consider all the variables for a property and <br />present that to Council for the Council at that point to make a determination on the appropriate <br />number of units. If Council's determination that 150 units are appropriate and that target were <br />not at the beginning of considerations, would we be vulnerable to an accusation of misleading <br />the property owners? <br /> <br /> Mr. Roush said the only risk is that if the target number is not included and a plan were <br />developed with a larger number than 150 units which Council found unacceptable, then a lot of <br />time and money would have been spent on something Council was not interested in. <br /> <br /> Ms. Mohr indicated Council frequently has plans before it with larger numbers than are <br />ultimately approved. <br /> <br /> Ms. Michelotti indicated the original motion was put forth in the correct way to require <br />studies and analysis and then come to some conclusion on the appropriate number of units based <br />on that and give alternatives regarding infrastructure, etc. When the 150 unit cap was added on <br />July 9, it predetermined what the conclusions would be before you have the analysis. <br /> <br /> Mr. Tarvet indicated that every point being raised will be discussed again and potentially <br />there may be different recommendations. This is still in the discussion stage and he requested <br />the public testimony to continue. <br /> <br /> Jan Batcheller, 644 St. Mary Street, indicated General Plans are made to be revised every <br />five years. Is Council trying to set parts of it in stone so future citizens cannot decide their own <br />destiny? She felt it was arrogant to say that the citizens living here today know what is best for <br />the future. The cornerstone of any political document should be flexibility. She referred to <br />comments of some people who desired to have parts of this on the ballot. They say they want <br />to protect their property values. This Council and those people are willing to devalue someone <br />else's property value, for example, the Lemoines, Daphne Christensen, the Vineyard Corridor <br />properties. Where do property rights fit in your picture? The General Plan Steering Committee <br /> <br />07/15/96 <br /> - 10- <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.