My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Minutes - 2020/06/08
MoundsView
>
Commissions
>
City Council
>
Minutes
>
2020-2029
>
2020
>
Minutes - 2020/06/08
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 9:24:29 AM
Creation date
6/23/2020 12:10:48 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Minutes
MEETINGDATE
6/8/2020
Supplemental fields
City Council Document Type
City Council Minutes
Date
6/8/2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
12
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 June 8, 2020 <br />Regular Meeting Page 11 <br /> <br />Council Member Bergeron stated just because this project will pay for itself in a few years does <br />not mean it is the right thing to do. <br /> <br />Council Member Meehlhause reiterated that it was 12 of the property owners that were driving <br />this project. He noted this development could not be built on a wetland. City Administrator <br />Zikmund stated a small wetland was found, but noted this was in the ditch area. He explained Mr. <br />Harstad had no way of knowing the contractor had not done the wetland delineation properly. He <br />indicated there was frustration with the Rice Creek Watershed District and noted the City may take <br />over permitting in the future. <br /> <br />Council Member Hull asked what staff’s recommendation was. City Administrator Zikmund <br />stated staff does not have a recommendation at this time. He understood this was a difficult <br />situation. <br /> <br />Council Member Gunn reported this property was always slated for residential development. She <br />anticipated if the City were to install the road and utilities, including the stormwater pond, this <br />would make the area more inviting for future development. She stated if this project were to move <br />forward only 12 properties should be assessed and not 14. <br /> <br />Council Member Bergeron requested staff repeat the statement regarding the likelihood of another <br />developer picking this project up if the present developer were to back out. Community <br />Development Director Sevald stated it would be difficult to find another developer. He indicated <br />this project has been in the works for the past 20 years and if any one property owner were to back <br />out the entire project would fail. <br /> <br />Council Member Bergeron recalled staff stating something to the effect that “no other developer <br />would touch it” and this could be correct. He stated this may indicate this was not a good place to <br />build. Community Development Director Sevald explained the more property owners that were <br />involved the more challenging it was to get a project through. <br /> <br />Council Member Meehlhause questioned if the City would build the stormwater pond. City <br />Administrator Zikmund reported the City would have a choice, and staff would recommend the <br />City build the pond. <br /> <br />Mayor Mueller estimated if the expense of the pond would be $250,000 or $21,000 per lot for 12 <br />properties or $18,000 if 14 lots were included. She asked if the 12 property owners supported <br />paying this expense. City Administrator Zikmund commented this did not need to be discussed or <br />clarified. He reported Mr. Harstad would do the math and get the estimates for the project. He <br />explained the Council needed to make a determination if this project would be assessed to 12 lots <br />or 14 lots. <br /> <br />Council Member Bergeron commented if the City were to move forward with the 12 lots there was <br />only a $3,000 difference in the price, versus an $18,000 liability for the two lots that do not want <br />to be a part of this project. <br />
The URL can be used to link to this page
Your browser does not support the video tag.