The get_timeseries function grabs all the unique properties found at the variable level along with archive type and publications which may make the table too big (400+ columns).
We already have a get_biblio function for publication, we should create an essentials functions that grab what most people will want and what GeoSeries requires in Pyleoclim:
[x] dataset name
[x] time
[x] value
[x] time unit
[x] value unit
[x] archive type
[x] proxy
[x] proxyGeneral
[x] value name
[x] time name
[x] lat
[x] lon
[x] elevation
[x] depth value
[x] depth name
[x] depth units
Should be accessing both paleo and chron and reuse Lipd terms for the columns
khider
commented
1 year ago
The
get_timeseriesfunction grabs all the unique properties found at the variable level along with archive type and publications which may make the table too big (400+ columns).We already have a
get_bibliofunction for publication, we should create an essentials functions that grab what most people will want and what GeoSeries requires in Pyleoclim:Should be accessing both paleo and chron and reuse Lipd terms for the columns