Eichhornia azurea
Eichhornia azurea
(anchored waterhyacinth)

7 results for Eichhornia azurea (anchored waterhyacinth)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1666783 CASacramento[No locality information provided]1931 18020163 Lower Sacramentounknown
1398387 MSRankin[no locality given]2005 03180002 Middle Pearl-Strongunknown
1399375 MSRankin[no locality given]2005 03180002 Middle Pearl-Strongunknown
1398634 MSRankin[no locality given]2005 03180002 Middle Pearl-Strongunknown
260617 PRCayeyunnamed pond near Cayey1982 21010005 Eastern Puerto Ricounknown
1669420 TXCameronUnder Hwy. 48 in Brownsville1967 12110208 South Laguna Madreunknown
1399514 VAAugusta[no locality given]2009 02070005 South Fork Shenandoahunknown

Data Disclaimer: Number of records does not imply species abundance. This summary represent collection records only and may not reflect the actual distribution of established populations. 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/25/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.