My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council - 07/26/2005
Ramsey
>
Public
>
Minutes
>
Council
>
2005
>
Minutes - Council - 07/26/2005
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/24/2025 1:52:22 PM
Creation date
8/8/2005 8:23:17 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council
Document Date
07/26/2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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
be to close the north end of old CR 5 and leave the south end open, as the safer place to turn is <br />from the southern intersection. <br /> <br />Councihnember Jeffrey expressed concern that the south entrance on old CR 5 is so close to <br />Alpine Drive that it creates almost a confusion corner. He stated his recommendation would be <br />lo close the south end of old CR 5 and leave the north end open. He does agree that one of these <br />accesses needs to be closed. <br /> <br />Councihnember Cook stated he does not think that either of these accesses will work well. <br />I lowevcr, he will work with either one of these accesses and the Quicksilver extension, as long <br />as it will be a temporary situation, with something better to be worked out in the future. <br /> <br />Councilmcmber Strommen commented Will Thompson might work with the City with some of <br />his property for the access. <br /> <br />Will Thompson, 15248 Nowthen Boulevard, stated there are a few things he would need to <br />consider in terms of their long term plans for the property, but something could likely be worked <br />()ut with the City regarding the access. <br /> <br />Mayor Gamec noted a decision needs to be made tonight, and negotiations would put a <br />stumbling block into this. <br /> <br />Councihnember Elvig commented it is a good point that neither of these are good exits from CR <br />5. However, the Quicksilver extension would mitigate traffic coming from the new <br />neighborhood to the old neighborhood, and from that standpoint closing down the south access <br />would help to mitigate that. Although the proposal from Mr. Thompson may be good, they are <br />talking about this being temporary, and ideally Potassium Street would be a frontage road to <br />come out to Alpine Drive. This discussion with Mr. Thompson looks as though they would start <br />to look at two new accesses, as opposed to one new access and shutting down another. He does <br />not l<now time wise that they can entertain that possibility at this point. <br /> <br />Councihnember Strommen suggested the south end of old CR 5 be left open and the north end <br />closed, and at a future point the City negotiate with Mr. Thompson to move or reconfigure the <br />south end. She noted this might be the way to get the access through Quicksilver and get what is <br />needed done tonight. <br /> <br />Councilmember Pearson stated he still has problems with Potassium Street, which should be <br />centered on the property line. It is not right that one property owner sacrifices frontage for the <br />benefit of the one along side of them. There are some nice trees, and going to the east will ruin <br />those yards, while the trees on the west are not as good. The wetland is not even a wetland in his <br />opinion, the swamps have changed and the water has slowly crept up in there; the area used to be <br />a cornfield and hay meadows. He would be willing to move ahead with this if the road is moved <br />to the west and centered on the property line. <br /> <br />Mayor Skogquist questioned if the City would be paying for the Quicksilver extension, since it <br />will be eliminated in the future. <br /> <br />City Council / July 26, 2005 <br /> Page 9 of 35 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.