Assignment of time-optimized cubes via (configurable) patterns or templates within xcube serve DataStore configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 230
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
I would like to configure corresponding time optimized cubes via the DataStore configuration of xcube serve.
Current Situation:
Many of our datacubes have a corresponding time optimized cubes, which is used e.g. for time series display in xcube viewer. The time optimized cubes are not visible the datasets of xcube viewer but if they are configured in the xcube server they will be used for the time series generation. The configuration is like the one below:
Datasets:
- Identifier: l2c-lm
Title: "Lake Mälaren"
FileSystem: "obs"
Endpoint: "https://s3.eu-central-1.amazonaws.com"
Anyonymous: false
Path: "bucket/ws-cube-v3.zarr"
Style: default
TimeSeriesDataset: l2c-lm_time_chunk
- Identifier: l2c-lm_time_chunk
Title: "Lake Mälaren Time Chunked"
Format: zarr
Endpoint: "https://s3.eu-central-1.amazonaws.com"
Anyonymous: false
Path: "bucket/ws-cube-v3-t_opt.zarr"
FileSystem: "obs"
Hidden: true
Style: default
When using DataStores the configuration would look e.g. like the one below:
DataStores:
- Identifier: Sweden
StoreId: s3
StoreParams:
root: bucket/Sweden
max_depth: 1
storage_options:
anon: false
Datasets:
- Identifier: "ws-*-v3.zarr"
Style: "default"
It would be great, if xcube serve would discover if there are cubes which are time optimized and then automatically use them for time-series visualisation.
This could be achieved e.g. by agreeing on a certain prefix or suffix in the cubes naming.
For example, we have ws-cube-v3.zarr (spatially optimised and visible in xcube viewer) and corresponding ts_ws-cube-v3.zarr
This way it would be possible to match the correct cube pairs.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names xcube serve DataStores and dataset discovery as the entry points; start by tracing how DataStores expand dataset patterns such as ws-*-v3.zarr. Determine how a matching time-optimized cube is identified and linked for time-series visualization, then verify that the optimized dataset can remain hidden while the visible cube uses it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100