Didymosphenia geminata
Didymosphenia geminata
(didymo)
Algae
Cryptogenic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

5 results for Didymosphenia geminata (didymo)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
4883 Didymosphenia geminata Infrastructure Anecdotal N/A Didymosphenia geminata can clog water filters and hydro plants. 37327
9751 Didymosphenia geminata Infrastructure Anecdotal N/A Nuisance algae including Didymosphenia geminata thrive in and clog canal systems which are... 30501
9752 Didymosphenia geminata Infrastructure Anecdotal N/A Didymosphenia geminata can block water filters, hydropower canals, and pipelines. 43374
9753 Didymosphenia geminata Infrastructure Anecdotal N/A Didymosphenia geminata can block water filters, hydropower canals, and pipelines. 43371
9754 Didymosphenia geminata Infrastructure Anecdotal N/A Didymosphenia geminata can foul water intakes. 37329

View all impact types for Didymosphenia geminata
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/28/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.