Edit History
Isotype of Vahlia capensis (L. f.) Thunb. subsp. vulgaris Bridson [family VAHLIACEAE]
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002332
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Davies, R.M., #2029
Collection Date
1956/06
Locality
Sebungwe, near Kariyangwe.
Country
Zimbabwe (Zimbabwe)
Collection altitude
609
Identifications
Isotype of Vahlia capensis (L. f.) Thunb. subsp. vulgaris Bridson [family VAHLIACEAE] (stored under name); Verified by D. B., 1973/07
Pages
1
Data last modified
2008-05-16
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002332
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Davies, R.M., #2029
Collection Date
1956/06
Locality
Sebungwe, near Kariyangwe.
Country
Zimbabwe (Zimbabwe)
Collection altitude
609
Identifications
isotype of Vahlia capensis (L. f.) Thunb. subsp. vulgaris Bridson [family VAHLIACEAE] (stored under name); Verified by D. B., 1973/07
Pages
1
Data last modified
2008-05-16
Date Updated: 14 May 2006
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002332
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Davies, R.M., #2029
Collection Date
1956/06
Locality
Sebungwe, near Kariyangwe.
Country
Zimbabwe (Zimbabwe)
Collection altitude
609
Identifications
Isotype of Vahlia vulgaris (L. f.) Thunb. subsp. vulgaris Bridson [family VAHLIACEAE] (stored under name); Verified by D. B., 1973/07
Pages
1
Data last modified
2006-05-15
╳
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.