xCO2 data not contained in backfill data
Hi Claas,
Thanks for the feedback. All of the data available via the API is in minutes -- so when you are passing an interval to the /timeseries endpoint, the interval is in minutes (e.g. interval = 1 is 1 data point per minute; interval = 60 is 1 data point per hour).
When you request a less granular time step, e.g. hourly instead of minutes, our current behavior for most of our other variables is to find the value closest to that timestamp, not necessarily aggregating the data. We could look into taking a similar approach for the xCO2 values, but may not be able to implement it for a couple of weeks. Please let me know if this is ok.
Thank you, Kim
On Tue, Oct 26, 2021 at 2:01 AM Claas Faber cfaber@geomar.de wrote:
Hey Kim, thank you, that's some great news. I was able to find the ASVCO data in the `biogeochemical` data. However, it seems that the data is not present for all intervals? I tried to query the data with 1s interval and got valid values near the :29 and :59 minute mark, as you describe, see e.g. request https://developer-mission.saildrone.com/v1/timeseries/1079?data_set=biogeochemical&interval=1&start_date=2021-10-26T07%3A00%3A00.000Z&end_date=2021-10-26T17%3A00%3A00.000Z&order_by=desc&limit=500&offset=0 When running the query with a different interval, e.g. 60, all asvco2_xco2 data is 'null'. Example request: https://developer-mission.saildrone.com/v1/timeseries/1079?data_set=biogeochemical&interval=60&start_date=2021-10-26T05%3A00%3A00.000Z&end_date=2021-10-26T17%3A00%3A00.000Z&order_by=desc&limit=500&offset=0 I'm not sure if that's by design or not, but it would be great if aggregates of the ASVCO values would be available for hourly intervals. For our current workflow, we query the API every 10 minutes for the latest positions and then query again once every couple hours with interval of 60s to backfill data that takes a bit to process before being available in the API. Please let me know if it is possible to include the ASVCO data within an 60s interval or if we should to adapt our current workflow. Thank you, Claas