My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
02-19-2013 Planning Commission Packet
Orono
>
Planning Commission
>
2013
>
02-19-2013 Planning Commission Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/1/2013 3:31:01 PM
Creation date
4/1/2013 3:30:18 PM
Metadata
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.
/
400
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
high quality natural community, 2) a conceptual greenway corridor, 3) steep sloping soils, and 4) <br /> other natural and semi-natural communities. High and medium quality natural community <br /> remnants also have the potential to support rare species. <br /> The inventory did not identify any specific need for proactive management or protection for the <br /> site. The wetland present on the site is not of type or quality to qualify for proactive management <br /> or protection. However, Wetland 1 will benefit from the implementation of a wetland buffer and <br /> stormwater protection. Due to field observed encroachment/invasion of invasive species within <br /> the southeast forested area,the presence of rare species is unlikely. <br /> Figures for all items listed above can be found in Appendix B. For reference,the full Orono <br /> Natural Resources Inventory document is available online at: <br /> http://www.hennepin.us/portal/site/HennepinUS/menuitem.b 1 ab75471750e40fa01 dfb47cc�649 <br /> 8/?v�nextoid=61b2b556b8933210VgnVCM10000049114689RCRD <br /> Review and Revision of DNR MLCCS Data- Current DNR Minnesota Land Cover <br /> Classification System (MLCCS) inventory data for the site was downloaded and reviewed for <br /> accuracy(Figure 3). A revised MLCCS map incorporating KES field observations is provided <br /> in Figure 4..Attached Table 1 outlines in detail DNR data and KES field verified data. <br /> Modifier M 34X has been included, as has the modifier for common buckthorn(M-408). Little <br /> to no garlic mustard was observed on the site. <br /> Data sets are similar in that they both identify ha�eld, grassland, and forest. KES was able to <br /> modify specific land cover boundaries based on known wetland boundaries and field verified <br /> land cover. The most drastic land cover change would be the reclassification of the southeast <br /> corner from an oak forest mesic subtype to a maple basswood forest. KES field verified data also <br /> provides more accurate information regarding invasive species coverage and location. Based on <br /> our assessment,proposed development of the site will not result in any negative impact to <br /> ecological communities (i.e. no modification to a lower level of ecological community quality as <br /> described by the MLCCS M-34X modifier; City Code Sec. 78-1635(6)). The home lots that will <br /> be located near or within the southeast maple basswood forest will likely be located close to the <br /> roadway where the highest concentration of common buckthorn and diseased trees were <br /> observed. <br /> Tree Survey-Tree ID number, diameter breast height(DBH), and species name for trees tagged <br /> during the tree survey are provided in Appendix C. Generally,trees were located within areas <br /> identified as altered forest, conifers, and maple basswood forest on Figure 4; however, some <br /> scattered trees were located in the ha�eld. <br /> Four significant tree stands (STS) are located on the site and are labeled as shown in Figure 5. <br /> These tree stands correspond to areas identified as altered forest, conifers, and maple basswood <br /> forest on the 2012 MLCCS land cover inventory. <br /> Wetland Inventory and Wetland Buffers-A wetland delineation was completed on the site in <br /> 2012 by KES. The report identified one wetland (Wetland 1)within site boundaries.(Figure 2). <br />
The URL can be used to link to this page
Your browser does not support the video tag.