My WebLink
|
Help
|
About
|
Sign Out
Home
Search
10-10-2022 City Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
2022
>
Searchable Packets
>
10-10-2022 City Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/12/2022 7:32:43 PM
Creation date
12/12/2022 2:13:48 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
10/10/2022
Council Meeting Type
Regular
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.
/
316
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
Response: The ACD-10-22 main trunk and BR2 will be protected with a minimum 20' <br />easement that extends out from the top of the ditch bank. Additional buffer and <br />easement width will be evaluated as part of the rezoning and preliminary plat review. <br />Comment 13. How will the vegetation and water conservation be enhanced in the disturbed <br />waterways in the project boundaries? <br />Response: The private ditches within the Project Site will have a minimum 10' vegetated <br />no mow buffer around them and the public drainage ditches on site will have a <br />mimimum 20' easement around them to protect them. A series of stormwater basins <br />are proposed on site that are subject to stormwater requirements from the City of Lino <br />Lakes, Rice Creek Watershed District, and the MPCA National Pollutant Discharge and <br />State Disposal System to pre -treat water running off from the surrounding development <br />before it is discharged into any receiving waters. This will improve the water quality of <br />the ditches since they currently receive direct runoff from the sod farm without any pre- <br />treatment. <br />Comment 14. Where in the EAW report can we find information from the MN Dept of <br />Agriculture, the Dept of Hydrogeology or Climatology regarding the sequela of years of <br />accumulation of fertilizers and pesticides from the sod farm land upon our disturbed soil, <br />ground water, and well water? <br />Response: The EAW's purpose is to focus on the environmental impacts of the proposed <br />development. The existing condition of the property as a sod farm is in compliance with <br />the MN Department of Agriculture guidelines and regulations. The MN Department of <br />Agriculture would be the regulatory agency to contact for this information. <br />In addition, the developer is completing a Phase II Environmental Site Assessment (ESA) <br />that will document site contamination and next steps. If contaminated soils are present <br />that do not meet residential reuse requirements they will be hauled offsite and <br />disposed of per MPCA guidelines. Dust BMPs will be in place during construction to <br />minimize the potential for dust <br />Comment 15. In 1977 the Carl Street residents were assured there would be no Carl St <br />connection and the cul-de-sac would remain. In 1986, 2006, and now, despite the developer's <br />original concept plan where Carl Street is not mentioned as a variable, would you please clarify <br />as to why Carl Street is repeatedly targeted for change, negatively affecting our property <br />values, safety, well-being, wildlife, creek, and vegetation? <br />Response: The Carl Street connection will be a policy decision from the City Council <br />based on sound engineering judgment. The Carl Street connection has been identified as <br />a through connection in several planning documents (2040 Comprehensive Plan Future <br />Roadway System Figure 6-13, Lino Lakes 2030 Transportation Comprehensive Plan <br />Future Roadway System Figure 6-12, 2001 Lino Lakes Transportation Plan) and right of <br />way was platted from 4th Avenue to Sunset Avenue originally in 1977. <br />16 <br />
The URL can be used to link to this page
Your browser does not support the video tag.