Skip to content

Datacube Access Architecture⚓︎

See also the Detailed Datacube Access Design

Overview⚓︎

The Datacube Access BB provides ‘pixel-based’ access to multidimensional data in accordance with the emerging OGC GeoDatacube API [RD28]. The goal of this API is to harmonise access to multidimensional data – and in doing so facilitate fusion of data from multiple sources by allowing alignment of units, geometries, references systems, etc. During OGC Testbed-19 the approach attempted to consolidate the APIs offered by the openEO Specification [RD19] and OGC API Processes [RD05]/[RD06] to present a singular interface.

Datacube Access

Via this interface, the Datacube Access BB offers a data access interface that is designed to satisfy the data access requirements of the openEO Building Block.

Data Gateway Reuse⚓︎

See section Datacube Access BB dependency on the Data Gateway.

Data assets are provided through a variety of storage technologies. The Datacube Access BB should use a modular design through which an extensible set of storage interface capabilities can be added. For this the Asset Storage Drivers that are defined as components of the Data Access BB can be relied upon - and in turn it is anticipated that the Asset Storage Drivers will utilise the Data Gateway BB in their implementation.

The Data Gateway provides access to the (raw) assets that are referenced from the product metadata - which facilitates their retrieval and delivery via the Datacube API.

In addition, the Data Gateway provides specific capabilities through which datasets can be made accessible through an xarray.DataArray representation. It is anticipated that this capability can be used to further enhance the offering of the Datacube API.