Edit History
Type? of Quercus rhombica Sarg. [family FAGACEAE]
Date Updated: 12 June 2025
Herbarium
Tulane University Herbarium (NO), NO0109884
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
R. S. Cocks, #4706
Collection Date
1917/09/20
Locality
Alabama; [Dallas County] Hatcher place, Sardis
Country
United States (United States)
Identifications
Type? of Quercus rhombica Sarg. [family FAGACEAE] (stored under name)
Quercus laurifolia Michx. [family FAGACEAE]; Verified by W. H. Duncan
Notes
Possible isotype
Pages
1
Data last modified
2014-04-29
Date Updated: 22 August 2014
Herbarium
Tulane University Herbarium (NO), NO0109884
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
R. S. Cocks, #4706
Collection Date
1917/09/20
Locality
Alabama; [Dallas County] Hatcher place, Sardis
Country
United States (United States)
Identifications
Type? of Quercus laurifolia Michx. [family FAGACEAE] (stored under name); Verified by W. H. Duncan, 1977
Quercus rhombica Sarg. [family FAGACEAE]
Notes
Possible isotype
Pages
1
Data last modified
2014-04-29
Date Updated: 6 June 2014
Herbarium
Tulane University Herbarium (NO), NO0109884
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
R. S. Cocks, #4706
Collection Date
1917/09/20
Locality
Alabama; [Dallas County] Hatcher place, Sardis
Country
Unknown (Unknown)
Identifications
Type? of Quercus laurifolia Michx. [family FAGACEAE] (stored under name); Verified by W. H. Duncan, 1977
Quercus rhombica Sarg. [family FAGACEAE]
Notes
Possible isotype
Pages
1
Data last modified
2014-04-29
╳
We're sorry. You don't appear to have permission to access the item.
Full access to these resources typically requires affiliation with a partnering organization. (For example, researchers are often granted access through their affiliation with a university library.)
If you have an institutional affiliation that provides you access, try logging in via your institution
Have access with an individual account? Login here
If you would like to learn more about access options or believe you received this message in error, please contact us.