search

stac-extensions / datacube

Datacube related metadata to describe their dimensions and variables.
Apache License 2.0
14 stars 2 forks source link

usage and maturity #15

Open betolink opened 10 months ago

betolink commented 10 months ago

At ITS_LIVE we have a list of Zarr data cubes (~3k items) and we'd like to generate a static STAC catalog, preferably using this extension. I'm a bit confused on the semantics of what a data cube means at the collection level, my idea is to have 1 top level collection that describes the dataset and each of the ~3000 zarr cubes are items of the collection that use the datacube extension to describe the dimensions, variables etc. I've only seen 1 cube per collection, so I'm not sure if I'm thinking this wrong. Any advice is welcome.

strobpr commented 8 months ago

Hi @betolink, I saw this question of yours and wondered whether you ever received a reply or figured out a solution yourself. I'm quite interested in semantics issues around EO and geospatial data and find your question very relevant. The concept of 'data cubes', 'collections', and alike are, if at all, not consistently defined across major actors in the field. Without proper semantics we will however struggle to achieve the interoperability which is at the core of STAC and ARD.

betolink commented 8 months ago

Hi Peter, we are still trying to figure out the semantics. I guess it could be both ways, if the "assets" in a cube align into a common grid and time dimension, then the cube could be represented at the collection level, in our case the data is sparse and do not necessarily align into a coherent grid and time dimension. Because of this I think we are going to go with a "collection of cubes" approach.