Edit History
Type of Trichopteryx dobbelaerei DeWild. [family POACEAE]
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000923407
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Dobbelaere, #13
Collection Date
1913
Locality
Katanga.
Country
Congo (Congo)
Identifications
Loudetia arundinacea (Hochst. ex A.Rich.) Steud. [family POACEAE] (stored under name); Verified by Sanchez-Ken
Type of Trichopteryx dobbelaerei DeWild. [family POACEAE]
Notes
Sheet I
Pages
1
Data last modified
2007-09-11
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000923407
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Dobbelaere, #13
Collection Date
1913
Locality
Katanga.
Country
Congo (Congo)
Identifications
Loudetia arundinacea (Hochst. ex A.Rich.) Steud. [family POACEAE] (stored under name); Verified by Sanchez-Ken
Type of Trichopteryx dobbelaerei DeWild. [family POACEAE]
Notes
Sheet I
Pages
1
Data last modified
2007-09-11
Date Updated: 25 September 2007
Herbarium
Natural History Museum (BM), BM000923407
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Dobbelaere, #13
Collection Date
1913
Locality
Katanga.
Country
Congo (Congo)
Identifications
Loudetia arundinacea (Hochst. ex A.Rich.) Steud. [family POACEAE] (stored under name); Verified by Sanchez-Ken
Type of Trichopteryx dobbelaerei DeWild. [family POACEAE]
Notes
Sheet I
Pages
1
Data last modified
2007-09-11
![Type of Trichopteryx dobbelaerei DeWild. [family POACEAE]](/fsi/img/size1/alukaplant/bm/phase_01/bm0007/bm000923407.jpg)
╳
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.