Edit History
Paratype of Psydrax parviflora Bridson subsp. chapmanii Bridson [family RUBIACEAE]
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002682
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Goldsmith, B., #37/67
Collection Date
1967/03
Locality
Chipinga. Chirinda forest.
Country
Zimbabwe (Zimbabwe)
Collection altitude
1097
Identifications
Paratype of Psydrax parviflora Bridson subsp. chapmanii Bridson [family RUBIACEAE] (stored under name); Verified by Bridson, D., 1985/04
Pages
1
Data last modified
2008-05-16
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002682
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Goldsmith, B., #37/67
Collection Date
1967/03
Locality
Chipinga. Chirinda forest.
Country
Zimbabwe (Zimbabwe)
Collection altitude
1097
Identifications
paratype of Psydrax parviflora Bridson subsp. chapmanii Bridson [family RUBIACEAE] (stored under name); Verified by Bridson, D., 1985/04
Pages
1
Data last modified
2008-05-16
Date Updated: 14 May 2006
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC002682
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Goldsmith, B., #37/67
Collection Date
1967/03
Locality
Chipinga. Chirinda forest.
Country
Zimbabwe (Zimbabwe)
Collection altitude
1097
Identifications
Paratype of Psydrax chapmanii Bridson subsp. chapmanii Bridson [family RUBIACEAE] (stored under name); Verified by Bridson, D., 1985/04
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.