Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)
Plants
Exotic

5 results for Potamogeton crispus (curly-leaf pondweed)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
3492 Potamogeton crispus Competition Experimental Laboratory Potamogeton crispus inhibited the growth of the cyanobacteria, Anabaena variabilis, via... 33998
8847 Potamogeton crispus Competition Anecdotal N/A Potamogeton crispus (curly-leaf pondweed) is tolerant of many ecological conditions... 35288
8848 Potamogeton crispus Competition Anecdotal N/A Potamogeton crispus (curly-leaf pondweed) germinates in the fall and survives the winter. 35289
8849 Potamogeton crispus Competition Anecdotal N/A Potamogeton crispus (curly-leaf pondweed) germinates in autumn. This growth habit, along... 35289
8850 Potamogeton crispus Competition Anecdotal N/A Potamogeton crispus (curly-leaf pondweed) can outcompete native species for light and... 28861

View all impact types for Potamogeton crispus
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/6/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.