Edit History
Type of Acaena euacantha Phil. [family ROSACEAE]
Date Updated: 3 August 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000002399
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Philippi F, #2183
Collection Date
1883/03
Locality
Cordillera de Santiago
Country
Chile (Chile)
Identifications
Type of Acaena euacantha Phil. [family ROSACEAE] (stored under name); Verified by Muñoz C, 1944
Acaena pinnatifida Ruiz et Pavón [family ROSACEAE]; Verified by Marticorena A, 1996
Pages
1
Data last modified
2009-08-03
Date Updated: 17 December 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000002399
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Philippi F, #2183
Collection Date
1883/03
Locality
Cordillera de Santiago
Country
Chile (Chile)
Identifications
Type of Acaena euacantha Phil. [family ROSACEAE] (stored under name); Verified by Muñoz C, 1944
Acaena pinnatifida Ruiz et Pavón [family ROSACEAE]; Verified by Marticorena A
[family ]
Pages
1
Data last modified
40028
Date Updated: 3 August 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000002399
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Philippi F, #2183
Collection Date
1883/03
Locality
Cordillera de Santiago
Country
Chile (Chile)
Identifications
Type of Acaena euacantha Phil. [family ROSACEAE] (stored under name); Verified by Muñoz C, 1944
Pages
1
Data last modified
2009-08-03
![Type of Acaena euacantha Phil. [family ROSACEAE]](/fsi/img/size1/alukaplant/sgo/phase_01/sgo0009/sgo000002399.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.