My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 05/01/2003
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2003
>
Agenda - Planning Commission - 05/01/2003
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:30:47 AM
Creation date
6/4/2003 10:28:49 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
05/01/2003
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.
/
395
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
Item 12 Mitigation Element. <br /> <br />Wetland Sequencing - Minnesota Rules 8420, also known as the Wetland Conservation <br />Act (WCA), requires specific steps ("sequencing") be taken when evaluating mitigation <br />for unavoidable wetland impacts. The WCA requires that wetland impacts be avoided, if <br />possible. If wetland avoidance cannot be accomplished, impacts to wetlands need to be <br />minimized. Finally, any wetland impacts that can not either be avoided or minimized to <br />the extent possible, must be mitigated though wetland replacement. The wetland <br />replacement must mitigate all wetland functions and values lost as part of the wetland <br />impact. <br /> <br />The degradation present on site allows the applicant to evaluate sequencing flexibility in <br />their mitigation plan. It also allows the Technical Evaluation Panel (TEP) the <br />opportunity to be flexible on the sequencing provisions of the WCA rule. This process <br />may only be applied in the event the wetlands on-site are degraded to the point where <br />replacement of the wetland would result in a gain in functions and values. This is an item <br />that will be considered by the TEP during the permitting process. <br /> <br />Wetlands located on site are described in the Wetland Delineation Report (Appendix A), <br />and are discussed in Item 10. With a few exceptions, wetlands located within the <br />boundaries of the RTC are either cropped or are of low quality. These wetlands have <br />marginal functions and values due to their low vegetative diversity, partial drainage and <br />lack of connectivity to other nearby wetlands and natural areas. Sequencing is addressed <br />as follows: <br /> <br />Avoidance: The better quality portions of existing wetlands are generally avoided. This <br />includes ali ofwetlands B, C and D. <br /> <br />Minimization: The mix of development proposed as part of the RTC requires that retail, <br />commercial and residential land use blocks are a minimum size with adequate <br />infrastructure to service them. The focus of minimization has been to incorporate as <br />much of existing wetland area into a central greenway corridor, thereby lowering overall <br />wetland loss across the project site. To avoid indirect impacts to remaining wetlands, <br />each of the development blocks will incorporate a treatment train of stormwater best <br />management practices designed to improve water quality and lower wetland bounce <br />magnitude and duration. Currently, row cropping occurs into the wetlands. The RTC <br />will incorporate wetland buffers wherever practical. <br /> <br /> I <br /> i <br /> I <br /> I <br /> I <br /> I <br /> I <br /> I <br />! <br />I <br />I <br />I <br />I, <br />Ii <br /> <br />Wetland Replacement: The LRRWMO Stormwater Management Plan provides that the <br />following may be eligible for wetland replacement credits: <br /> <br />36 <br /> <br />· Creation of"new" wetland - Rules, Sub-part 11; <br />· Addition of"public value" Rules, Sub-part 6; <br />· "Public value" restoration from invasive species to permanent native, non- <br /> invasive species - Rules, Sub-part 8; and <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.