Hygrophila polysperma
Hygrophila polysperma
(Indian swampweed)

5 results for Hygrophila polysperma (Indian swampweed)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
3143 Hygrophila polysperma Competition Experimental Laboratory Hygrophila polysperma out-competed Ludwigia repens in biomass growth in tank... 31299
7075 Hygrophila polysperma Competition Experimental Laboratory Hygrophila polysperma has outcompeted Hydrilla verticillata, another... 32661
7076 Hygrophila polysperma Competition Observational Field In contrast to the competitive ability of Hygrophila polysperma observed in the... 42130
7077 Hygrophila polysperma Competition Observational Field Sampling on the San Marcos River, TX found that Hygrophila polysperma was one of the... 22751
7078 Hygrophila polysperma Competition Anecdotal N/A Hygrophila polysperma may form dense single species stands that often do not provide ideal... 31293

View all impact types for Hygrophila polysperma
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.


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 [7/16/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.