My WebLink
|
Help
|
About
|
Sign Out
Home
Search
10/14/2002 Council Minutes
LinoLakes
>
City Council
>
City Council Meeting Minutes
>
2002
>
10/14/2002 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/6/2015 2:15:28 PM
Creation date
2/5/2015 2:24:13 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Minutes
Meeting Date
10/14/2002
Council Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
29
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
COUNCIL MINUTES OCTOBER 14, 2002 <br />. Councilmember Carlson wanted to clarify that it remained uncertain as to whether or not that property <br />was subject to lease or not and she wanted this point noted. <br />• <br />• <br />City Planner Smyser stated he did not know for certain, but he would be surprised because the property <br />was so small. <br />Councilmember Carlson referenced page 8, the bottom paragraph of section B, "The proposed site <br />configuration is intended to minimuze disruption to sensitive species." She indicated this is why she <br />asked about other development on that site, because here that statement is being made and is in <br />reference to what the DNR was concerned about, the heron rookery and cattail marsh and their <br />response. <br />Councilmember Carlson stated on page 12, top of the page, the western portion of the site is in the <br />floodplain and she wished to clarify whether it was also correct that it is within the 1,000 foot <br />shoreline ordinance? <br />City Planner Smyser responded by stating the shoreland ordinance covers 1,000 feet from the ordinary <br />high water level of the lake. As noted previously, he believed the ordinary high water level •is 884.7 so <br />1,000 feet from that is included in the shoreland overlay zone. That does not mean that nothing can be <br />built in that zone. It just means the shoreland regulations cover that. So, yes, the flood plain is within <br />the shoreland zone, he indicated. <br />Councilmember Carlson state she had concerns about sewer and water not reaching this area before <br />development. If the Council were going to be approving a single family residential area there it would <br />not be allowed. On page 15, she noted thatelevated raM field mounds will be necessary because of the <br />lower soils being somewhat poorly drained. She 'inquired as to how many mounds would be requierd, <br />and what size and how will they be landscaped in? <br />Mr. Walt Trishonhower, SRF Consulting,, stated the question was regarding number of mounds. There <br />would be one mound, that we ave indica t on the plan. <br />Councilmember Carlson indicated she was asking, because the word "mounds" indicates a plural. She <br />inquired as to how large will that one mound be to be able to handle that size system? Mr. <br />Trishonhower responded he believed that would be approximately 50,000 square feet. <br />Councilmember Carlson expressed surprise and stated that City Planner Smyster had made that same <br />comment on the height of the building being 80 feet earlier in the report. She inquired as to whether <br />that mound would be landscaped in with the rain gardens, then. Mr. Trishonhower stated the mound <br />area cannot be touched according to MPCA guidelines. <br />Councilmember Carlson stated her next question related to the size of the mound because it has to do <br />with (per page 17) solid waste, hazardous waste and storage tanks. It states that 140% of the proposed <br />church is estimated to generate approximately 140% of the current church's solid waste amounts. Now <br />the current church is 1,400 seats, the proposed church is 2,100 with a possible 700 is 2,800. Exactly <br />16 <br />
The URL can be used to link to this page
Your browser does not support the video tag.