Edit History
Type? of Chenopodium hastatum Phil. [family CHENOPODIACEAE]
Date Updated: 3 August 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000001636
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Gay C, #1325
Collection Date
1836/09
Locality
Prov. Coquimbo
Country
Chile (Chile)
Identifications
Type? of Chenopodium hastatum Phil. [family CHENOPODIACEAE] (stored under name); Verified by Muñoz C, 1945
Chenopodium petiolare Kunth [family CHENOPODIACEAE]; Verified by Marticorena A, 1999
Notes
En carpeta Chenop. Hastatum
Pages
1
Data last modified
2009-08-03
Date Updated: 17 December 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000001636
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Gay C, #1325
Collection Date
1836/09
Locality
Prov. Coquimbo
Country
Chile (Chile)
Identifications
Type ? of Chenopodium hastatum Phil. [family CHENOPODIACEAE] (stored under name); Verified by Muñoz C, 1945
Chenopodium petiolare Kunth [family CHENOPODIACEAE]; Verified by Marticorena A
[family ];
Notes
En carpeta Chenop. Hastatum
Pages
1
Data last modified
40028
Date Updated: 3 August 2009
Herbarium
Museo Nacional de Historia Natural (SGO), SGO000001636
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Gay C, #1325
Collection Date
1836/09
Locality
Prov. Coquimbo
Country
Chile (Chile)
Identifications
Type ? of Chenopodium hastatum Phil. [family CHENOPODIACEAE] (stored under name); Verified by Muñoz C, 1945
Notes
En carpeta Chenop. Hastatum
Pages
1
Data last modified
2009-08-03
╳
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.