You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to establish whether there is new/changed data being delivered by the CLIMADA API?
I'm mainly interested in large changes, for example another year of historical data being added to an indicator or the basis year of something like LitPop being changed.
The context for this question is that I am looking for a trigger to refresh the data on HDX. In the absence of a simple trigger I'll probably just set a yearly schedule to update data.
I considered using versions of this repo as a guide but as I understand this simply reflects changes in the mechanism of data delivery rather than a change in the underlying data.
The text was updated successfully, but these errors were encountered:
Thanks for the question. There is the 'activation_date' that is an attribute of every dataset. Perhaps that could be helpful?
There is no "greater than" condition for it so you would have to fetch all datasets, e.g. into a data frame and query that:
Is there a way to establish whether there is new/changed data being delivered by the CLIMADA API?
I'm mainly interested in large changes, for example another year of historical data being added to an indicator or the basis year of something like LitPop being changed.
The context for this question is that I am looking for a trigger to refresh the data on HDX. In the absence of a simple trigger I'll probably just set a yearly schedule to update data.
I considered using versions of this repo as a guide but as I understand this simply reflects changes in the mechanism of data delivery rather than a change in the underlying data.
The text was updated successfully, but these errors were encountered: