Edit History
Paratype of Vitellariopsis ferruginea F.K.Kupicha [family SAPOTACEAE]
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002860
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Wild, H., #4393
Collection Date
1953/12/15
Locality
Bikita
Country
Zimbabwe (Zimbabwe)
Collection altitude
1067
Identifications
Paratype of Vitellariopsis ferruginea F.K.Kupicha [family SAPOTACEAE] (stored under name); Verified by F.K.Kupicha, 1977
Pages
1
Data last modified
2008-05-16
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002860
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Wild, H., #4393
Collection Date
1953/12/15
Locality
Bikita
Country
Zimbabwe (Zimbabwe)
Collection altitude
1067
Identifications
paratype of Vitellariopsis ferruginea F.K.Kupicha [family SAPOTACEAE] (stored under name); Verified by F.K.Kupicha, 1977
Pages
1
Data last modified
2008-05-16
Date Updated: 6 August 2006
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002860
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Wild, H., #4393
Collection Date
1953/12/15
Locality
Bikita
Country
Zimbabwe (Zimbabwe)
Collection altitude
1067
Identifications
Paratype of Vitellariopsis F.K.Kupicha [family SAPOTACEAE] (stored under name); Verified by F.K.Kupicha, 1977
Pages
1
Data last modified
2006-08-07
![Paratype of Vitellariopsis ferruginea F.K.Kupicha [family SAPOTACEAE]](/fsi/img/size1/alukaplant/lisc/phase_01/lisc0000/lisc002860.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.