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:{E391C6C5-4501-41D5-925D-FE28537E9AE6}
Carex retroflexa Muhlenberg ex Willdenow. Section: [26d] Section 4.0 Phaestoglochin. Reflexed Sedge. Phen: May-Jun. Hab: Dry to mesic forests, especially over base-rich substrates. Dist: ME, MI and IA, south to n. peninsular FL and TX.
Origin/Endemic status: Native
Taxonomy Comments: See Downer & Hyatt (2003).
Synonymy ⓘ: = Ar, ETx1, F, FNA23, GrPl, Il, K1, K3, K4, Mi, Mo1, NcTx, NE, NY, Pa, S, Tat, Tn, Va, Mackenzie (1931-1935); = Carex retroflexa Muhl. ex Willd. var. retroflexa – C, G; < Carex retroflexa Muhl. ex Willd. – RAB, Tx, W, WH3, (also see C. texensis)
Links to other floras: = Carex retroflexa - FNA23
Show in key(s) | Show Carex section in key
Wetland Indicator Status:
- Atlantic and Gulf Coastal Plain: FACU (taxonomic split from wetland indicator species)
- Eastern Mountains and Piedmont: FACU (taxonomic split from wetland indicator species)
- Great Plains: FACU (taxonomic split from wetland indicator species)
- Midwest: FACU (taxonomic split from wetland indicator species)
- Northcentral & Northeast: FACU (taxonomic split from wetland indicator species)
Heliophily ⓘ: 5
Hover over a shape, letter, icon, or arrow on the map for definition or see the legend.
© Gary P. Fleming | Original Image ⭷
© Joey Shaw source | Original Image ⭷
© Joey Shaw source | Original Image ⭷
© Scott Ward | Original Image ⭷
© Joey Shaw source | Original Image ⭷
© Joey Shaw source | Original Image ⭷
© Radford, Ahles and Bell | Original Image ⭷Feedback
See something wrong or missing on about Carex retroflexa? 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.