Edit History
Type of Acaena longifolia Phil. [family ROSACEAE]
Date Updated: 14 September 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000002410
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Philippi O, #s.n.
Collection Date
1887/02
Locality
Queñi, prov. Valdivia
Country
Chile (Chile)
Identifications
Type of Acaena longifolia Phil. [family ROSACEAE] (stored under name); Verified by Muñoz C, 1945
Acaena pinnatifida Ruiz et Pavón [family ROSACEAE]; Verified by Marticorena A, 1996
Pages
1
Data last modified
2009-09-14
Date Updated: 17 December 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000002410
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Philippi O, #s.n.
Collection Date
1887/02
Locality
Queñi, prov. Valdivia
Country
Chile (Chile)
Identifications
Type of Acaena longifolia Phil. [family ROSACEAE] (stored under name); Verified by Muñoz C, 1945
Acaena pinnatifida Ruiz et Pavón [family ROSACEAE]; Verified by Marticorena A
[family ]
Pages
1
Data last modified
20090914
Date Updated: 14 September 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000002410
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Philippi O, #s.n.
Collection Date
1887/02
Locality
Queñi, prov. Valdivia
Country
Chile (Chile)
Identifications
Type of Acaena longifolia Phil. [family ROSACEAE] (stored under name); Verified by Muñoz C, 1945
Pages
1
Data last modified
2009-09-14
![Type of Acaena longifolia Phil. [family ROSACEAE]](/fsi/img/size1/alukaplant/sgo/phase_01/sgo0000/sgo000002410.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.