Specimen Information

Trapa natans
Trapa natans
(water chestnut)
Plants
Exotic

Specimen ID279632
GroupPlants
GenusTrapa
Speciesnatans
Common Namewater chestnut
StateMA
CountyMiddlesex
LocalityThe Holt, Concord River
Mapping AccuracyAccurate
HUC8 NameConcord River
HUC8 Number01070005
HUC10 NameSudbury River
HUC10 Number0107000501
HUC12 NameHop Brook-Sudbury River
HUC12 Number010700050104
Map
+
Collection Day29
Collection Month8
Collection Year1879
Year AccuracyActual
Potential Pathwayplanted ornamental
Statusestablished
Reference 1
Ref. Number:703
Author:Mills, E.L., J.H. Leach, J.T. Carlton, and C.L. Secor
Date:1993
Title:Exotic species in the Great Lakes: a history of biotic crises and anthropogenic introductions
Journal:Journal of Great Lakes Research
Volume:19
Issue:1
Pages:1-54
Reference 2
Ref. Number:23862
Author:Eaton, R.J.
Date:1947
Title:Lemna minor as an aggressive weed in the Sudbury River.
Journal:Rhodora
Volume:49
Issue:583
Pages:165-171
Reference 3
Ref. Number:27725
Author:Consortium of Northeastern Herberia (CNH).
Date:2023
Title:Herbarium Specimen Data Sharing Portal for CNH
Commentswidely distributed and aggressive in the Concord and Sudbury Rivers. (Ref 2 collection date is incorrect; specimen notes indicates likely from 1879) HUH specimen
Record TypeSpecimen
Earliest Recorddrainage
DisposalHerbarium
Museum Cat NumberNEBC00283769, NEBC00283770
VerifierC.B. Hellquist
Freshwater/MarineFreshwater
Photo
Trapa natans
Trapa natans


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/6/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.