Edit History
Isotype of Leptactina senegambica Hook. f. [family RUBIACEAE]
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC003310
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Heudelot, #893
Collection Date
1837
Locality
Rio Pongos.
Country
Senegal (Senegal)
Identifications
Isotype of Leptactina senegambica Hook. f. [family RUBIACEAE] (stored under name)
Notes
"Hooker f. refere apenas o no. de colheita sem indicaçao do Herbário" - E.Martins, 16/2/2004. Syntypus?
Pages
1
Data last modified
2008-05-16
Date Updated: 16 May 2008
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC003310
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Heudelot, #893
Collection Date
1837
Locality
Rio Pongos.
Country
Senegal (Senegal)
Identifications
isotype of Leptactina senegambica Hook. f. [family RUBIACEAE] (stored under name)
Notes
"Hooker f. refere apenas o no. de colheita sem indicaçao do Herbário" - E.Martins, 16/2/2004. Syntypus?
Pages
1
Data last modified
2008-05-16
Date Updated: 17 August 2007
Herbarium
Instituto de Investigação Científica Tropical (LISC), LISC003310
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Heudelot, #893
Collection Date
1837
Locality
Rio Pongos.
Country
Senegal (Senegal)
Identifications
isotype of Leptactina Hook. f. [family RUBIACEAE] (stored under name)
Notes
"Hooker f. refere apenas o no. de colheita sem indicaçao do Herbário"- E.Martins, 16/2/2004. Syntypus?
Pages
1
Data last modified
2007-08-18
╳
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.