My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Public Works Committee - 11/20/2001
Ramsey
>
Public
>
Minutes
>
Public Works Committee
>
2000 - 2009
>
2001
>
Minutes - Public Works Committee - 11/20/2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/18/2025 9:34:23 AM
Creation date
6/6/2003 11:27:17 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Public Works Committee
Document Date
11/20/2001
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
13
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. Preston replied that it would be somewhat more expensive, however if the existing roadway <br />were to remain there would be damages associated with those impacted businesses. Each <br />proposed location has different items that would increase the costs. <br /> <br />Councilmember Zimmerman inquired if there will be any rough estimates on what each option <br />would cost. <br /> <br />Mr. Preston replied that the process of preparing costs would not differentiate between the <br />locations. <br /> <br />Councihnember Hendriksen stated that he has thought that the large sweeping crossings would <br />be more appropriate for the new bridge crossing. <br /> <br />Mr. Preston reviewed a system interchange. <br /> <br />A discussion was held regarding the location of the multi-mogul site in which Mr. Issacson <br />indicated that the City needs to select the location for a multi-mogul site. <br /> <br />Councilmember Hendriksen stated that the City has been struggling with what to do with the land <br />between Highway #10 and the railroad tracks for years and he felt that it did make a lot of sense <br />for the City to acquire the property at this time because it will be very expensive to do so in the <br />future if they wait. <br /> <br />Case #2: <br /> <br />Investigation of Dirty Water Complaint Expressed at the October 16, 2001 <br />Public Works Committee Meeting <br /> <br />City Engineer Olson stated that last month the City received a letter regarding the clarity of <br />municipal water in the Wood Pond Hills subdivision. The purpose of this case was to discuss the <br />background of rusty water complaints, explain some of the causes, explain the City's current <br />processes to ensure clean water, and discuss alternatives that could curb the frequency of these <br />types of complaints. All of Ramsey's municipal wells have elevated levels of iron and <br />manganese typical to the aquifers utilized for municipal water supply throughout the Twin City <br />area. The combination of these high levels and operational changes result in rust or discolored <br />water in the system. Throughout normal operation, the velocity of the water flowing through the <br />pipes is relatively low and the longer the water remains in the pipes, the more chance the iron and <br />manganese particles have to precipitate out. While the water towers provide storage to meet <br />demand, it also provides water pressure so that water comes out of a faucet when the water is <br />turned on. This pressure is directly relational to the elevation difference between the water in the <br />tower and the house, and results in the iron and manganese particles being "pressed" to the inside <br />of the pipes. Generally, the flow patterns are defined by the use and demand of the system. Put <br />another way, the direction the water flows is established and altered by each new addition, <br />change, or hookup to the system. In Ms. Hunter's case, the supply of water was most likely <br />coming from Water Tower #1 during normal operation. As discussed at the last Public Works <br />Committee, staff consulted with Bolten & Menk. They have a modeling software called <br /> <br />Public Works Committee/November 20, 2001 <br /> Page 10 of 13 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.