From 72dc2309ee71706a1a09b314db44403201e34435 Mon Sep 17 00:00:00 2001 From: Michael Sumner Date: Sat, 8 Nov 2025 08:57:18 +1100 Subject: [PATCH] Fix link formatting for Datacube Extension Overhaul --- content/blog/2025/251028-stac-sprint-eu-recap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2025/251028-stac-sprint-eu-recap.md b/content/blog/2025/251028-stac-sprint-eu-recap.md index f443b27..88b9d53 100644 --- a/content/blog/2025/251028-stac-sprint-eu-recap.md +++ b/content/blog/2025/251028-stac-sprint-eu-recap.md @@ -31,7 +31,7 @@ The sprint produced several concrete proposals that will shape how we work with - **[Best Practices for STAC Zarr and N-Dimensional Arrays](https://github.com/radiantearth/stac-best-practices/pull/29)**: A comprehensive draft providing guidance on using Zarr with STAC. This is significant because, until now, nobody had proper guidance on this integration. The PR is ready for community review and needs feedback to refine and finalize the recommendations. We would like to merge it by the end of November to provide clarity to implementers. We encourage everyone to review and contribute feedback by participating in the next community meetings or commenting directly on the PR. -- **[Datacube Extension Overhaul of Variables](https://github.com/stac-extensions/datacube/issue/30)**: A proposal to replace `cube:variables` with `bands` to better align with how STAC structures metadata. This change could make the datacube extension more intuitive and powerful for multidimensional datasets. This PR will probably require further discussion before merging, as it represents a breaking change in the extension. +- **[Datacube Extension Overhaul of Variables](https://github.com/stac-extensions/datacube/issues/30)**: A proposal to replace `cube:variables` with `bands` to better align with how STAC structures metadata. This change could make the datacube extension more intuitive and powerful for multidimensional datasets. This PR will probably require further discussion before merging, as it represents a breaking change in the extension. - **[EOPF STAC Patterns](https://github.com/EOPF-Sample-Service/eopf-stac/pull/54)**: ESA-specific best practices for their Earth Observation Processing Framework (EOPF) Zarr products. EOPF STAC represents the largest effort to-date of representing Zarr stores in STAC. Aligning EOPF STAC with the newly emerging best practices serves as a test of the feasibility of these best practices and provides a concrete example. Part of this effort also involves reusing existing STAC extensions wherever possible to improve compatibility between EOPF products and external products.