feat(esm_catalog): PR-A1d — datacube STAC extension#1507
Merged
Conversation
Co-Authored-By: Paul Gierz <pgierz@awi.de>
Co-Authored-By: Paul Gierz <pgierz@awi.de>
…hema Co-Authored-By: Paul Gierz <pgierz@awi.de>
…ariables edge Co-Authored-By: Paul Gierz <pgierz@awi.de>
siligam
added a commit
that referenced
this pull request
Jul 15, 2026
mandresm
approved these changes
Jul 16, 2026
Contributor
|
#bump #patch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds PR-A1d — Datacube extension from the plan:
cube:dimensionsandcube:variableson items when the scan metadata carries them.Two notes. The extension is applied as one self-contained
add_datacube_extension()called frommake_item— the single-seam shape from the #1506 discussion, so guard, URL, and properties can't drift apart. And it turns out the v2.2.0 schema requirescube:dimensionswhenever the extension is declared, so variables-only metadata is a no-op; there's a test validating a full item against a vendored copy of the schema to keep us honest (the CI workflow getsjsonschemaadded for that).