Specimen Information

Myriophyllum spicatum
Myriophyllum spicatum
(Eurasian watermilfoil)
Plants
Exotic

Specimen ID1684724
GroupPlants
GenusMyriophyllum
Speciesspicatum
Common NameEurasian watermilfoil
StateMN
CountyDakota
LocalityOrchard Lake, Dakota County
Mapping AccuracyAccurate
HUC8 NameLower Minnesota
HUC8 Number07020012
HUC10 NameMinnesota River
HUC10 Number0702001211
HUC12 NameCredit River
HUC12 Number070200121107
Map
+
Collection Day3
Collection Month7
Collection Year2017
Year AccuracyActual
Potential Pathwayunknown
Statusunknown
Reference 1
Ref. Number:24369
Author:Center for Invasive Species and Ecosystem Health.
Date:2019
Title:EDDMapS: Early detection and distribution mapping system
Publisher:The University of Georgia
CommentsEurasian watermilfoil (Myriophyllum spicatum) was observed on July 3, 2017 by a former MnDNR employee and University of Minnesota PhD student. While using a rake to sample Northern watermilfoil (Myriophyllum sibiricum) the student collected the invasive plant. The exact location of the sampling point was noted (see map 1). The presence of this plant was then reported to the MnDNR on July 5, 2017. Suspected plants had 13-17 leaflet pairs, whorls of 4 widely spaced (~3cm) and leaves are limp and collapse out of water -consistent with the biological characteristics of Eurasian watermilfoil (see Photo 1 & 2). Orchard Lake will be added to the Designated Infested Waters list as infested with Eurasian watermilfoil.
Record TypeLiterature
Freshwater/MarineUnknown


Disclaimer:

The data represented on this site vary in accuracy, scale, completeness, extent of coverage and origin. It is the user's responsibility to use these data consistent with their intended purpose and within stated limitations. We highly recommend reviewing metadata files prior to interpreting these data.

Citation information: U.S. Geological Survey. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [4/23/2024].

Contact us if you are using data from this site for a publication to make sure the data are being used appropriately and for potential co-authorship if warranted.

For general information and questions about the database, contact Wesley Daniel. For problems and technical issues, contact Matthew Neilson.