Edit History
Type of Linostylis fasciculiflora Fenzl ex Sond. [family ACANTHACEAE]
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000931011
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Kotschy,T., #558
Collection Date
1837-38
Locality
Camamil, Choor Abu kuldzi.
Country
Ethiopia (Ethiopia)
Identifications
Dyschoriste nagchana (Nees) Bennet [family ACANTHACEAE] (stored under name)
Type of Linostylis fasciculiflora Fenzl ex Sond. [family ACANTHACEAE]
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), BM000931011
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Kotschy,T., #558
Collection Date
1837-38
Locality
Camamil, Choor Abu kuldzi.
Country
Ethiopia (Ethiopia)
Identifications
Dyschoriste nagchana (Nees) Bennet [family ACANTHACEAE] (stored under name)
Type of Linostylis fasciculiflora Fenzl ex Sond. [family ACANTHACEAE]
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), BM000931011
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Kotschy,T., #558
Collection Date
1837-38
Locality
Camamil, Choor Abu kuldzi.
Country
Ethiopia (Ethiopia)
Identifications
Dyschoriste nagchana (Nees) Bennet [family ACANTHACEAE] (stored under name)
Type of Linostylis fasciculiflora Fenzl ex Sond. [family ACANTHACEAE]
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.