eurodatacube / eodash

Software behind the RACE dashboard by ESA and the European Commission (https://race.esa.int), the Green Transition Information Factory - GTIF (https://gtif.esa.int), as well as the Earth Observing Dashboard by NASA, ESA, and JAXA (https://eodashboard.org)
https://race.esa.int
MIT License
89 stars 43 forks source link

feat: add 5 new biomass datasets from VEDA #2511

Closed lubojr closed 3 months ago

lubojr commented 3 months ago

https://github.com/eurodatacube/eodash/issues/2392

aapopescu commented 3 months ago
lubojr commented 3 months ago

@aapopescu thank you very much for the feedback.

aapopescu commented 3 months ago

Thanks, @lubojr

lubojr commented 3 months ago

@aapopescu Technically yes, I tried to integrate it already, but the dataset is huge (daily data for 19 years), so the statistics endpoint was too overloaded. NASA analytics endpoint does not allow "under-the-hood" time axis aggregation like Sentinel Hub does, so we would need to pick up dates ourselves to fetch the statistics for manually. We have observed the "reasonable" limit in the past being a few hundred of requests to the statistics at one go.

We saw now that the data is quite dynamic and it seems to have some peaks that could be a pity to miss.

We would propose to do a custom implementation for a 1 year history from the currently selected date on the main map. Or do you have any specific date range in mind which could be interesting for this dataset? E.g. first day of a month for full 19 years (ignoring the possible spikes), or weekly for last x years of duration or so?

Ideally we should let the user pick this interval/time start/end time/aggregation for custom chart themselves, but it would be more involved development, that should probably not go into the current implementation of the v4 version of the client.

lubojr commented 3 months ago

@aapopescu We have implemented the above mentioned solution of showing always 1 year history from currently selected date on the main map. This is also enabled for every other NASA statistics API dataset (previously we were only using the newest several hundred times). From our point of view the PR could be merged. Could you please confirm if the indicator names and such are now fine to be deployed?

lubojr commented 3 months ago

I am merging this PR in order to avoid possible merge conflicts upstream and to have this available in new trilateral stories. We can still do updates afterwards.