Intro:
Stems:
Leaves:
Inforescence:
Flowers:
Fruits:
Comments:
Height:
plant sale text:
bloom table text:
description:
stems:
leaves:
inflorescence:
flowers:
fruits:
comments:
cultural notes:
germination code:
native range:
https://fsus.ncbg.unc.edu/main.php?pg=show-taxon-detail.php&lsid=urn:lsid:ncbg.unc.edu:taxon:{5CBC57FD-81AA-429A-8587-8031246B3668}
Eleocharis macrostachya Britton. Large Spikerush. Phen: Jul-Oct. Hab: Wet ditches, marshes, shorelines. Dist: QC to AK south to WV, AL, MS, TX, CA, and Mexico; South America. Mapping is especially conjectural.
Origin/Endemic status: Native
Synonymy ⓘ: = Ar, ETx1, FNA23, GrPl, Il, K1, Mex, Tx; < Eleocharis palustris (L.) Roem. & Schult. – C, K3, K4, Mo1
Links to other floras: = Eleocharis macrostachya - FNA23
Wetland Indicator Status:
- Atlantic and Gulf Coastal Plain: OBL (taxonomic split from wetland indicator species)
- Eastern Mountains and Piedmont: OBL (taxonomic split from wetland indicator species)
- Great Plains: OBL (taxonomic split from wetland indicator species)
- Midwest: OBL (taxonomic split from wetland indicator species)
- Northcentral & Northeast: OBL (taxonomic split from wetland indicator species)
Heliophily ⓘ: 9
Hover over a shape, letter, icon, or arrow on the map for definition or see the legend.
© Eric Keith, some rights reserved (CC BY-NC), uploaded by Eric Keith source CC-BY-NC, permission granted to NCBG | Original Image ⭷
© Scott Ward | Original Image ⭷
© Eric Keith, some rights reserved (CC BY-NC), uploaded by Eric Keith source CC-BY-NC, permission granted to NCBG | Original Image ⭷
© Eric Keith, some rights reserved (CC BY-NC), uploaded by Eric Keith source CC-BY-NC, permission granted to NCBG | Original Image ⭷
© Paul Marcum source | Original Image ⭷
© Scott Ward | Original Image ⭷
© Matt Reala, some rights reserved (CC BY-NC), uploaded by Matt Reala source CC-BY-NC, permission granted to NCBG | Original Image ⭷Feedback
See something wrong or missing on about Eleocharis macrostachya? Let us know here: (Please include your name and email if at all complicated so we can clarify if needed.) We greatly appreciate feedback, and will include updates from you in our next webapp update, which can take a few months.