Salvinia molesta
Salvinia molesta
(giant salvinia)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

5 results for Salvinia molesta (giant salvinia)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
3476 Salvinia molesta Commerce Observational N/A Commercial activities of the inhabitants of the Sepik River system in Papua New Guinea were... 28402
4518 Salvinia molesta Commerce Anecdotal N/A plants block fishing nets and impede the passage of boats 36455
7618 Salvinia molesta Commerce Anecdotal N/A Thick mats of Salvinia molesta prevent passage of large diesel-powered boats. As a result... 28408
7626 Salvinia molesta Commerce Anecdotal Field Salvinia molesta covered 250km^2 of the water surface of Sepik River in Papua New Guinea.... 28408
9531 Salvinia molesta Commerce Observational Field 18 acres of Salvinia molesta in Florida were treated for a total expenditure of $3,531. 42996

View all impact types for Salvinia molesta
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 [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.