My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2005/04/25
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2000-2009
>
2005
>
Agenda Packets - 2005/04/25
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:47:35 PM
Creation date
7/31/2018 1:12:38 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
4/25/2005
Supplemental fields
City Council Document Type
City Council Packets
Date
4/25/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.
/
214
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).
Show annotations
View images
View plain text
Mounds View City Council April 11, 2005 <br />Regular Meeting Page 8 <br /> <br />time where they need to make decisions on what they are going to do with their property. He 1 <br />stated it was his suggestion to grant a waiver for the coming year and ask them to come back 2 <br />to report in a year on the status, and hopefully there will be something in front of them to look 3 <br />at by way of a proposal, and they could take another look at it. He didn’t feel anybody was 4 <br />going to suffer if there wasn’t a connection made for the next year. 5 <br /> 6 <br />Council Member Flaherty asked if he was the same Mr. Nelson that was in contact with James 7 <br />Hesberg back in 1994 for this same subject. 8 <br /> 9 <br />Mr. Nelson stated it was brought up then, and there was a decision made on behalf of the City 10 <br />not to require the connection at that point. 11 <br /> 12 <br />Council Member Flaherty asked if there was any background on what happened. 13 <br /> 14 <br />Director Ericson stated that a search had been made of the records, and there is nothing that 15 <br />exists in writing. 16 <br /> 17 <br />Council Member Flaherty stated that the issue isn’t going to go away, and it’s been 11 years 18 <br />since it was first brought up. 19 <br /> 20 <br />Council Member Gunn stated it was seven years ago. 21 <br /> 22 <br />Council Member Flaherty stated that Mr. Nelson was involved for the past 11, and it goes 23 <br />back to 1986. He stated there is a lot of correspondence over the years saying they need 24 <br />to hook up to sewer and water. He stated he’s sure the water is clean and the wells are working 25 <br />fine, but the City Code was specifically drawn up for the betterment of the City to make things 26 <br />like this don’t get out of hand. He stated he was curious what happened in the previous 11 years. 27 <br />He asked if they thought the City was going to go away. 28 <br /> 29 <br />Mr. Nelson stated that the issue of 11 years going by without the issue being raised indicates 30 <br />an agreement was reached in 1994 not to require it. If there had been a requirement it had to be 31 <br />done within the next month or a year, that would have triggered some action from the City. 32 <br /> 33 <br />Council Member Thomas asked Mr. Ericson how many other properties had been required to 34 <br />connect up to the sewer since this Code was in place in 1992. 35 <br /> 36 <br />Director Ericson stated there were 20 or 30 properties that had to be connected as a result of 37 <br />the 1992 ordinance, and this is the one remaining property that does not have access to sewer and 38 <br />water. He stated there are five other properties in the City where they don’t have access to 39 <br />sewer or water, and the Code does grant an exception for that. 40 <br /> 41 <br />MOTION/SECOND. Thomas/Gunn. To move on Option No. 3. 42 <br /> 43 <br />Council Member Thomas stated she believed they need to offer some time for this simply to 44 <br />welcome development, and she would hate to rule out the phone call that could happen this 45
The URL can be used to link to this page
Your browser does not support the video tag.