Halophila stipulacea
Halophila stipulacea
(tropical seagrass)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

5 results for Halophila stipulacea (tropical seagrass)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
9070 Halophila stipulacea Food Web Observational Field In the Mediterranean Sea, Chelonia mydas diets contained 31% of the invasive Halophila... 45858
10054 Halophila stipulacea Food Web Observational Field Fish traps in sea-grass beds with and without Halophila stipulacea showed an increase in... 45834
10062 Halophila stipulacea Food Web Observational Field Juvenile fish Sarpa salpa were observed grazing year-round on Halophila... 45854
10072 Halophila stipulacea Food Web Anecdotal Field Sea turtles, Chelonia mydas, were observed eating the non-native seagrass, Halophila... 46117
10082 Halophila stipulacea Food Web Observational Field Halophila stipulacea has lower nutritional value but higher digestibility than native... 46139

View all impact types for Halophila stipulacea
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. [2025]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [12/18/2025].

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.