My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Public Works Committee - 10/18/2005
Ramsey
>
Public
>
Minutes
>
Public Works Committee
>
2000 - 2009
>
2005
>
Minutes - Public Works Committee - 10/18/2005
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/17/2025 3:03:48 PM
Creation date
3/7/2006 11:17:18 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Public Works Committee
Document Date
10/18/2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
7
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
City Engineer Jankowski replied any new development would be required to demonstrate that it <br />can handle its own stormwater runoff. <br /> <br />Assistant Public Works Director Olson advised there is a drainage and utility easement on the <br />adjacent property to the west and the wetland behind this property is City owned. <br /> <br />Acting Chairperson Cook stated if this pond is within the drainage and utility easement and is not <br />going beyond the ponding expected, he would look towards denying this and ensuring that the <br />elevation of the runoff is at the correct level. <br /> <br />Motion by Acting Chairperson Cook, seconded by Councilmember Olson, to recommend that the <br />City Council deny the request to remove the existing drainage pond. <br /> <br />Further discussion: Mayor Gamec inquired if the Weiss' have use of the property under the <br />easement. City Engineer Jankowski replied the easement allows use of the property, with the <br />City ensured the right to utilize the easement for drainage. Assistant Public Works Director <br />Olson advised there is a restriction in drainage and utility easements against retaining walls. <br />This restriction is difficult to catch because permits are not required for construction of retaining <br />wails. Acting Chairperson Cook suggested the issue of retaining walls in easements should be <br />revisited at some point, as there have been retaining walls built in several drainage easements. <br /> <br />Motion carried. Voting Yes: Acting Chairperson Cook, Councilmember Olson and Mayor <br />Gamec. Voting No: None. Absent: Chairperson Elvig. <br /> <br />Further discussion: Mayor Gamec recommended the liability issue be determined in this case, <br />as well as other cases throughout the City where drainage ponds are located within easements on <br />private property. Public Works Director Kapler indicated staff will research this issue and report <br />to Mr. and Mrs. Weiss and the City Council. <br /> <br />Case #2: <br /> <br />Consider Replacement of Existing Yield Sign with a Stop Sign at Marmoset <br />and 154th Lane <br /> <br />City Engineer Jankowski stated an email request has been received from Colleen Fischer for the <br />replacement of the yield sign for 154th Lane with a stop sign at its intersection with Marmoset <br />Street. He reviewed the following information regarding the request: <br /> <br />· Accident history: A review of the Police Department records dating back to 2000 show <br /> no reported accidents at this intersection. <br />· Traffic: Traffic counts were taken in the 24 hour period between Wednesday, October 12, <br /> 2005, and Thursday, October 13, 2005. The results of this traffic volume study show 194 <br /> vehicles per day on the north leg; 71 vehicles per day on the west leg; 98 vehicles per day <br /> on the east leg; and 195 vehicles per day on the south leg. <br />· Sight distance: There is an adequate sight distance for the northbound and eastbound <br /> approaches into this intersection. There is a large evergreen tree located on the northeast <br /> comer of the intersection, which impacts the visibility between approaching southbound <br /> <br />Public Works Committee / October 18, 2005 <br /> Page 3 of 7 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.