Hydrocharis morsus-ranae
Hydrocharis morsus-ranae
(European frogbit)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

5 results for Hydrocharis morsus-ranae (European frogbit)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
5103 Hydrocharis morsus-ranae Food Web Anecdotal N/A has the potential to negatively impact native plant, fish, and invertebrate communities 37717
5120 Hydrocharis morsus-ranae Food Web Anecdotal N/A fewer snails, crustaceans and insect larvae in EFB mats relative to native; fewer benthic worms and... 37720
8022 Hydrocharis morsus-ranae Food Web Anecdotal N/A As colonies of common frogbit (Hydrocharis morsus-ranae) displace native plants, other... 42436
8023 Hydrocharis morsus-ranae Food Web Anecdotal N/A Dense mats of common frogbit (Hydrocharis morsus-ranae) can inhibit the movement of... 42435
8024 Hydrocharis morsus-ranae Food Web Anecdotal N/A Common frogbit (Hydrocharis morsus-ranae) mats were found to cause a decline in snails... 25392

View all impact types for Hydrocharis morsus-ranae
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 [6/2/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.