Eichhornia crassipes
Eichhornia crassipes
(common water-hyacinth)
Plants
Exotic

4 results for Eichhornia crassipes (common water-hyacinth)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1685323 MNHennepinThree Rivers Park District employee noted 120 different locations with the plant adjacent to the cattail fringe. Locations of plants were on the west end of Pike Lake by the community dock and three homeowners docks?.2016 07010206 Twin Citiesunknown
1685325 MNRamseyOfficial location of occurrence was in the western most pond below Indian Mounds Park2016 07010206 Twin Citiesunknown
1685324 MNRamseyPond is one block to the SW of Applewood Preserve.2016 07010206 Twin Citiesunknown
1397591 MNRamseySmall wetland to the north of paved trail, Charles Perry Park, City of Arden Hills2013 07010206 Twin Citiesunknown

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 [11/21/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.