Edit History
Type of Cheilanthes dealbata Pursh [family PTERIDACEAE]
Date Updated: 29 February 2012
Herbarium
Natural History Museum (BM), BM000936626
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
John Bradbury, #s.n.
Locality
America septentrionalis.
Country
United States (United States)
Identifications
Type of Cheilanthes dealbata Pursh [family PTERIDACEAE] (stored under name); Verified by Swan, J.
Pages
1
Data last modified
2012-02-22
Date Updated: 22 February 2012
Herbarium
Natural History Museum (BM), BM000936626
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
John Bradbury, #s.n.
Locality
America septentrionalis.
Country
United States (United States)
Identifications
Type of Cheilanthes dealbata Pursh [family PTERIDACEAE] (stored under name); Verified by Swan, J.
Pages
1
Data last modified
2008-11-04
Date Updated: 22 February 2012
Herbarium
Natural History Museum (BM), BM000936626
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
John Bradbury, #s.n.
Country
United States (United States)
Identifications
Type of Cheilanthes dealbata Pursh [family PTERIDACEAE] (stored under name); Verified by Swan, J.
Pages
1
Data last modified
2008-11-04
Date Updated: 31 March 2009
Herbarium
Natural History Museum (BM), BM000936626
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
John Bradbury, #s.n.
Country
United States (United States)
Identifications
Type of Cheilanthes dealbata Pursh [family PTERIDACEAE] (stored under name)
Pages
1
Data last modified
2008-11-04
╳
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.