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
constantinius opened this issue
Jun 24, 2024
· 1 comment
Assignees
Labels
BR062provide access to multidimensional data with an OGC GeoDatacube APIBR063support assets via common storage technology interfaces, e.g. S3, HTTP, filesystem
The text was updated successfully, but these errors were encountered:
constantinius
added
BR062
provide access to multidimensional data with an OGC GeoDatacube API
BR063
support assets via common storage technology interfaces, e.g. S3, HTTP, filesystem
labels
Jun 24, 2024
constantinius
changed the title
Expose OGC API coverages routes within GeoDatacube API frontend
Expose OGC API coverages routes within GeoDatacube API frontend [#3305]
Sep 13, 2024
Schpidi
changed the title
Expose OGC API coverages routes within GeoDatacube API frontend [#3305]
Expose OGC API coverages routes within GeoDatacube API frontend [#3306]
Jan 2, 2025
There's no clear alignment on how coverages should be used, and no way of knowing how to drive it forward. We spent time experimenting with multidimensional coverages within Testbed-20, but we didn't find a feasible solution within the Stacture/Terravis stack. The task in this BB is to expose Coverages via the gdc-api, but we barely have this functionality in data-access BB as is.
Time was spent on:
Meetings
Searching for multidimensional coverages
Subsetting, moving, and standardizing a coverage on our servers
Rethinking and rearchitecting how this fits within Stacture/Terravis, as it doesn't integrate well with the current architecture
BR062provide access to multidimensional data with an OGC GeoDatacube APIBR063support assets via common storage technology interfaces, e.g. S3, HTTP, filesystem
No description provided.
The text was updated successfully, but these errors were encountered: