My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 02/08/2005
Ramsey
>
Public
>
Agendas
>
Council
>
2005
>
Agenda - Council - 02/08/2005
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 1:40:16 PM
Creation date
2/7/2005 7:58:24 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
02/08/2005
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
436
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
Councilmember Cook Commented Ms. Pickard's lot is already part of density transitioning from <br />one lot to another. <br /> <br />Michael Gavlin, 15752 Osmium Street, stated his property is north of this proposed development. <br />He does see how this could become a PUD, but this development does seem a little dense <br />compared to the properties to the north. Another issue is along the northern property line there is <br />a tree buffer line and there are gaps inthat, one of which directly affects the property he owns. <br />He would like to see some sort of dense tall evergreens planted there. He would also have <br />concerns with drainage, but knows those will be addressed later. <br /> <br />Will Thompson, 15428 Nowthen Boulevard, stated he is concerned about the increase in future <br />traffic volumes and the safety aSpects. This access will have to tie in with the new CR 5 and he <br />would encourage the developer to keep in mind some upgrades are needed. He stated the traffic <br />is very dangerous at the:intersections in the area of Alpine Drive and CR 5 and needs attention. <br />Whatever is done as far as density reduction will lessen the impacts at these intersections. <br /> <br />June Hampton, 15551 Potassium Street, Stated her concern and question is what will happen to <br />Potassium Street, as it has been stated it will be difficult to move. The residents have no choice <br />and have to stay here, but the builders can make choices. She is appealing to the Council to <br />make the right choice to make this a win/win situation. The builder should make some money, <br />but the residents should be treated fairly toO. <br /> <br />Assistant Public Works Director Olson explained the situation with Potassium Street is not that it <br />is physically not possible; it is difficult due :to the Wetland laws that prohibit filling in wetlands. <br /> <br />Mt'. Hampton stated his concerns with this development are the same as with the previous <br />development regarding the road. <br /> <br />Associate Planner Wald recapped direction from the Council to address the issues of density, <br />benefits to the City for the PUD, the length of the cul-de-sac, the future connection to the south, <br />keeping the tree buffer and completing it along the north side, looking at Potassium Street and <br />the right-of-way, and concerns onthe intersections in the area of Alpine Drive and old CR 5. <br /> <br />Mayor Gamec noted the intersection at Alpine Drive and CR 5 was looked at before and needs to <br />be addressed. <br /> <br />Councilmember Elvig presented a picture of the proposed detached townhomes. He informed <br />the residents these units are attractive and self-contained, they are not like the large townhome <br />structures along Highway 10. <br /> <br />Ms. Fix stated right now there is traffic coming down Radium Street constantly and traffic from <br />the development to the east. In addition there will now be traffic from these two new <br />developments coming down Radium Street :and going out CR 5. She stated the traffic will be <br />blocked up in the morning if there is not another exit to CR 5. <br /> <br />City CounCil/JanUary 25, 2005 <br /> page 13 of 24 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.