My WebLink
|
Help
|
About
|
Sign Out
Home
2020.03.02 CC Packet
Hugo
>
City Council
>
City Council Agenda/Packets
>
2020 CC Packets
>
2020.03.02 CC Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/25/2020 12:58:05 PM
Creation date
2/27/2020 4:12:43 PM
Metadata
Fields
Template:
City Council
Document Type
Agenda/Packets
Meeting Date
3/2/2020
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
90
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
proposed plan will result in impacting wetlands 1 and 2 in their entirety and a portion of wetland 3a. These <br />impacts total 0.5407 acre. <br />The applicant addressed the special considerations as required under 8420.0515 and found that none of the <br />considerations listed would require the application to be denied are require conditional approval. <br />Seauencine <br />The applicant provided two (2) alternatives that would completely avoid all wetland impacts. Both <br />alternatives would not allow the project purpose and/or requirements to be met and were rejected. <br />The initial plan included impacts to the east end of wetland 3 (8,702 sq. ft.). These impacts were eliminated. <br />The applicant also considered further minimizing wetland impacts by moving street c to the west, adding <br />additional stormwater facilities, and eliminating additional lots, but this alternative was rejected due to <br />engineering constraints and further issues related to stormwater runoff. <br />Sequencing flexibility can be applied to both wetlands 1 and 2 under MN Rule 8420.0520 Subp. 7a. A(1) and <br />(2) as these wetlands are currently farmed and the replacement wetland would result in a gain in function. <br />The remaining unavoidable wetland impacts are proposed to be replaced using approved wetland bank <br />credits. <br />Replacement <br />The proposed plan would result in 0.5407 acre of wetland impact after minimization. The applicant is <br />proposing the use of wetland bank credits from bank 1122 and 1601. No bank credits are available in the <br />minor watershed, but both banks are found in the major watershed (Mississippi River-20) and the same Bank <br />Service Area (7). The total amount of wetland credit being applied to this project is 1.0814 acres (2:1 ratio) <br />since the credits are in the same bank service area. <br />Based on the information provided in the Rice Lake Preserve Wetland Permit Application, dated February 7, <br />2020, the request for sequencing and replacement are approved with conditions. <br />' Findings must consider any TEP recommendations. <br />Attached Project Documents <br />® Site Location Map ® Project Plans)/Descriptions/Reports (specify): R CCe Lake Preserve <br />Wetly d Permit Are , l lcation Revised 'FebrLJ F,,., ry 7. 2020 <br />Appeals of LGU Decisions <br />If you wish to appeal this decision, you must provide a written request within 30 calendar days of the date you <br />received the notice. All appeals must be submitted to the Board of Water and Soil Resources Executive Director <br />along with a check payable to BWSR for $500 unless the LGU has adopted a local appeal process as identified <br />below. The check must be sent by mail and the written request to appeal can be submitted by mail or e-mail. <br />The appeal should include a copy of this notice, name and contact information of appellant(s) and their <br />representatives (if applicable), a statement clarifying the intent to appeal and supporting information as to why <br />the decision is in error. Send to: <br />Appeals & Regulatory Compliance Coordinator <br />Minnesota Board of Water & Soils Resources <br />520 Lafayette Road North <br />St. Paul, MN 55155 <br />BWSR NOD Form — November 12, 2019 <br />
The URL can be used to link to this page
Your browser does not support the video tag.