Draft
Conversation
added 19 commits
February 23, 2026 13:02
… such as coverage, more
…eneath dataset endpoint
…ect period format
…al code so we always work with an xarray dataset, dask compute after time aggregation to avoid very slow dask graphs later
…s zarr file if it exists which is much faster
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
datasetsroute which handles data registry via yaml files and via dhis2eo can trigger cache builds from api as well (though maybe not ideal for prod). Everything is generic and nothing is hardcoded for each data source, so it's easy to add new sources as long as they are supported by dhis2eo (in future should be possible to support non-dhis2eo sources too).aggregateroute for requesting aggregates from cached datasets and custom aggregation statistics.Quick and dirty, many improvements needed.