Specimen Information

Myriophyllum spicatum
Myriophyllum spicatum
(Eurasian watermilfoil)
Plants
Exotic

Specimen ID1409874
GroupPlants
GenusMyriophyllum
Speciesspicatum
Common NameEurasian watermilfoil
StateVT
CountyOrange
Localitybackwater area of the CT River approx. 1/2 mile WSW of Reeds Marsh and approx. 1 mile NNE of the village of Ely
Mapping AccuracyAccurate
HUC8 NameWaits River-Connecticut River
HUC8 Number01080104
HUC10 NameGrant Brook-Connecticut River
HUC10 Number0108010402
HUC12 NameLake Morey-Connecticut River
HUC12 Number010801040205
Map
+
Collection Day6
Collection Month9
Collection Year2006
Year AccuracyActual
Potential Pathwayhitch hiker | dispersed
Statusunknown
Reference 1
Ref. Number:29921
Author:Mehrhoff, L.J., J.A. Silander, Jr., S.A. Leicht, E.S. Mosher, and N.M. Tabak
Date:2003
Title:IPANE: Invasive Plant Atlas of New England
Publisher:Department of Ecology and Evolutionary Biology, University of Connecticut
Reference 2
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
Commentsbackwater area of the CT RIver; brook/outlet from Lake Morey (which has a M. spcatum infestation) empties intothis backwater area; plot includes water and some shore area too.;
Record TypeLiterature
Freshwater/MarineFreshwater
Number Collected20-99
Year ClassVegetative


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 [12/9/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.