Myriophyllum spicatum
Myriophyllum spicatum
(Eurasian watermilfoil)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

4 results for Myriophyllum spicatum (Eurasian watermilfoil)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
8739 Myriophyllum spicatum Infrastructure Anecdotal N/A Dense mats of Myriophyllum spicatum (Eurasian watermilfoil) can reduce water flow or clog... 35275
8740 Myriophyllum spicatum Infrastructure Anecdotal N/A Property owners, lake associations, and local governments incur costs to keep boat channels clear... 35279
8741 Myriophyllum spicatum Infrastructure Anecdotal N/A Waterfront property owners in Michigan spend an estimated $20 million annually to control aquatic... 42531
8742 Myriophyllum spicatum Infrastructure Anecdotal N/A In New York, the annual costs of controlling Eurasian watermilfoil (Myriophyllum spicatum)... 16770

View all impact types for Myriophyllum spicatum
Data Disclaimer: These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the data.

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 [11/21/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.