search

openskope / Datasets

Dataset descriptions and metadata used to build Elasticsearch database
0 stars 0 forks source link

First column in downloaded timeseries CSV file should in time units #9

Closed jterstriep closed 6 years ago

jterstriep commented 6 years ago

Originally submitted by @tmcphillips

Currently the first column of a downloaded CSV file is titled ‘index’, and the values correspond to the zero-based index of each time point in the series rather than to the time (e.g. year) at that time point. For data sets that are known to be in time units of years, the first column should be named 'year', and the values should reflect the year corresponding to each point in the time series. For the full PaleoCAR run the values in the year column should run from 1 to 2000 (currently the first column is titled 'index' and the values range from 0 to 1999).

If the requests to the timeseries service are posed in terms of years (e.g. by including 'timeResolution=year&timeZero=1' as part of the query line for the PaleoCAR data set), the CSV field in the response from the service automatically will satisfy the above requirements.

jterstriep commented 6 years ago

Add the above parameters and I'm now getting an error in the graph generation.

tmcphillips commented 6 years ago

Make sure the time range in requests is in terms of years when timeResolution=year.

jterstriep commented 6 years ago

The webapp needs to be updated to use years rather than index. The PaleoCAR dataset has been updated.