Edit History
Isotype of Ficus chirindensis C.C.Berg [family MORACEAE]
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC003329
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Goldsmith, B., #23/64
Collection Date
1964/06
Locality
Chipinge. Chirinda Forest.
Country
Zimbabwe (Zimbabwe)
Collection altitude
1097
Identifications
Isotype of Ficus chirindensis C.C.Berg [family MORACEAE] (stored under name); Verified by Berg, C.C., 1965/09
Pages
1
Data last modified
2008-05-16
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC003329
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Goldsmith, B., #23/64
Collection Date
1964/06
Locality
Chipinge. Chirinda Forest.
Country
Zimbabwe (Zimbabwe)
Collection altitude
1097
Identifications
isotype of Ficus chirindensis C.C.Berg [family MORACEAE] (stored under name); Verified by Berg, C.C., 1965/09
Pages
1
Data last modified
2008-05-16
Date Updated: 17 August 2007
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC003329
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Goldsmith, B., #23/64
Collection Date
1964/06
Locality
Chipinge. Chirinda Forest.
Country
Zimbabwe (Zimbabwe)
Collection altitude
1097
Identifications
isotype of Ficus C.C.Berg [family MORACEAE] (stored under name); Verified by Berg, C.C., 1965/09
Pages
1
Data last modified
2007-08-18
![Isotype of Ficus chirindensis C.C.Berg [family MORACEAE]](/fsi/img/size1/alukaplant/lisc/phase_01/lisc0009/lisc003329.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.