My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2011_0926
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2011
>
CC_Minutes_2011_0926
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/11/2011 12:00:49 PM
Creation date
10/11/2011 12:00:40 PM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
9/26/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
62
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
Regular City Council Meeting <br /> Monday, September 26, 2011 <br /> Page 19 <br /> Mayor Roe confirmed that assumption; noting that whatever development oc- <br /> curred it would have an impact that would be cost-associated with that develop- <br /> ment and according to this plan; and further clarified that while there may be few- <br /> er vehicle trips on the actual property, the calculation methodology indicated that <br /> there would be 98 touches on various improvements in the area as a baseline. <br /> City Engineer Debra Bloom concurred with Mayor Roe's description, clarifying <br /> that the network trips were based on PM peak hour and worst case scenarios; con- <br /> firming that the peak period was based on 10% of the overall 24-hour period, not <br /> a cumulative full day; and varied based on land use. <br /> While respecting the City's desire to get good development into Roseville, Mr. <br /> Dorso opined that the entire effort to develop the Twin Lakes area had been a <br /> prime example of government at its worst. In his particular situation, Mr. Dorso <br /> noted that he paid $186,000 in annual property taxes for his parcel; reviewed the <br /> history of the City evicting his tenant and reimbursing the tenant for relocating, <br /> with the entire development then falling apart due to the City not him. Mr. Dorso <br /> opined that that the development fee would not be sustained in court versus a tra- <br /> ditional assessment method; and questioned if this actually had increased the val- <br /> ue of his land, and opined that it had most likely decreased its value for develop- <br /> ment purposes. <br /> Based on his proposed development for a 144,000 square foot medical facility and <br /> remaining residential use, Mr. Dorso questioned the assumptions for internal trips; <br /> and his estimated $2 million in developer fees under this calculation method, <br /> when the property was only worth a maximum of$3 million in today's market, <br /> with the development fee representing 66% of the value of his property; and his <br /> inability to even get a curb cut on the back of his property. <br /> Mr. Dorso also questioned the provision that he only had 180 days after adoption <br /> of this ordinance to hire a consultant, approved by the City, to assess the network <br /> trips if he contested the City's consultant or engineer's study; and questioned the <br /> cost to the City for such a study and how much more money he would have to <br /> spend to test that theory. <br /> Mayor Roe offered to have staff provide that cost information to Mr. Dorso; how- <br /> ever, he clarified that the study was for the entire Twin Lakes Redevelopment <br /> Area and would therefore be more than a parcel-specific study. <br /> Mr. Dorso noted that he would be spending additional money in going through the <br /> City's appeal process and then court; and questioned the legality of the City at- <br /> tempting to say that he couldn't go to court until having completed the 180 day <br /> appeal process. Mr. Dorso opined that it was questionable how he could success- <br /> fully negotiate a voluntary agreement when he had no power to negotiate; and <br /> questioned the intent of this City Council and their successors in good faith nego- <br />
The URL can be used to link to this page
Your browser does not support the video tag.