Edit History
Syntype of Streptocarpus ruwenzoriensis Baker [family GESNERIACEAE]
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000930962
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Godman,E. & Godman,C., #371
Collection Date
29.02.1924
Locality
Ruwenzori Mts.
Country
Unknown (Unknown)
Identifications
Streptocarpus glandulosissimus Engl. [family GESNERIACEAE] (stored under name)
Syntype of Streptocarpus ruwenzoriensis Baker [family GESNERIACEAE]
Notes
Indicated as not a type specimen
Pages
1
Data last modified
2007-09-11
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000930962
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Godman,E. & Godman,C., #371
Collection Date
29.02.1924
Locality
Ruwenzori Mts.
Country
Unknown (Unknown)
Identifications
Streptocarpus glandulosissimus Engl. [family GESNERIACEAE] (stored under name)
Syntype of Streptocarpus ruwenzoriensis Baker [family GESNERIACEAE]
Notes
Indicated as not a type specimen
Pages
1
Data last modified
2007-09-11
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000930962
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Godman,E. & Godman,C., #371
Collection Date
29.02.1924
Locality
Ruwenzori Mts.
Country
Unknown (Unknown)
Identifications
Streptocarpus glandulosissimus Engl. [family GESNERIACEAE] (stored under name)
Syntype of Streptocarpus ruwenzoriensis Baker [family GESNERIACEAE]
Notes
Indicated as not a type specimen
Pages
1
Data last modified
2007-09-11
╳
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.