My WebLink
|
Help
|
About
|
Sign Out
Home
2009_0817_Packet
Roseville
>
City Council
>
City Council Meeting Packets
>
2009
>
2009_0817_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/9/2012 3:07:03 PM
Creation date
8/20/2009 4:01:33 PM
Metadata
Fields
Template:
General
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
161
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. Hall, at the request of Mayor Klausing clarified their preferences and understanding of <br />discussions and negotiations with staff: <br />. The cost of the road was to be borne by the developer <br />• No specific conversation on the cost of the turnaround <br />. Location as proposed on public park land was clearly a result of the meetings between the <br />developer and the City's landscape architect, and park representatives <br />• Since there is a benefit to the developer in saving trees along the eastern border and not <br />having units look down on a turnaround, if the park sees a benefit in creating a gateway <br />via that turnaround, Mr. Hall agreed that the developer would be willing to pay for the <br />turnaround. <br />Councilmember Roe clarified that the developer was willing to pay for the turnaround, but <br />preferred to see it on park property. <br />Mr. Hall concurred; noting the developer's position that they'd already given substantially to this <br />proj ect, through paying for a park road that they had given up other development potential for <br />that roadway; and in agreeing to pay park dedication fees on top of that. Mr. Hall asked for some <br />compromise on the part of the City by locating the turnaround off their land. <br />Discussion ensued regarding road width; emergency vehicle turnaround if parking was allowed <br />on-street for park overflow parking; buffer between the park and development; existing parking <br />through existing warehouse parking lot and long-term use; additional 10-15 parking spaces in <br />parking lot without additional tree removal; length of road requiring a turnaround; review of the <br />tree inventory for the property (i.e., Siberian Elms, Box Elders, Cottonwoods); and mitigation of <br />tree loss through replanting with more desirable trees. <br />Further discussion included defining road width based on where the turnaround is located. <br />Councilmember Pust opined that if the access road were built off the developer` s turnaround, <br />part of a new Master Plan for Langton Park may not consider that as a good option, thus creating <br />the need to consider the issues separately. Councilmember Pust opined that the turnaround <br />should be contained on the developer's property, on Lot 1. <br />Mayor Klausing expressed his preference to keep the road narrower at twenty-six feet (26'). <br />Councilmember Willmus indicated his openness to either on their land or park property. <br />Mayor Klausing expressed a preference to maintain a narrow roadway with a turnaround. <br />Councilmember Ihlan offered no opinion on this issue. <br />Councilmember Roe opined that the turnaround could be located half on each property. <br />Klausing moved, �llmus seconded, that the road width be maintained at twenty six feet (26 ) <br />and that the turnaround be located at a point close to the connection with the parking lot; with <br />the turnaround to be constructed at the developer's cost, on City park lanc� <br />Councilmember Pust spoke against the motion; opining that the turnaround should be on the <br />developer's property. <br />Councilmember Roe indicated that his preference in locating the turnaround would be to keep it <br />as far north in the park land as possible; while still allowing for the connection to the parking lot; <br />and spoke in opposition to this motion unless modified. <br />
The URL can be used to link to this page
Your browser does not support the video tag.