Eichhornia crassipes
Eichhornia crassipes
(common water-hyacinth)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

8 results for Eichhornia crassipes (common water-hyacinth)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
241063 AZMaricopaArizona Canal, at Price & Baseline Rd.1965 15060106 Lower Saltcollected
241060 AZMaricopaPapago Park1965 15060106 Lower Saltestablished
213711 GACamdenlower reaches of Satilla River, near the seacoast1965 03070203 Cumberland-St. Simonsestablished
213708 GAChathamSavannah River, lower reaches near the seacoast1965 03060109 Lower Savannahestablished
229492 GADougherty/BakerFlint River1965 03130008 Lower Flintestablished
228590 GAMitchell/DecaturFlint River1965 03130008 Lower Flintestablished
228608 GASeminole/DecaturLake Seminole1965 03130008 Lower Flintestablished
234613 TXMadisonMadison County1965 Unknown or N/Aestablished

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.

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 [12/26/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.