Docs/mini geozarr spec#24
Merged
emmanuelmathot merged 15 commits intoEOPF-Explorer:mainfrom Sep 25, 2025
Merged
Conversation
d-v-b
commented
Aug 20, 2025
…nd clarifying its implementation details in architecture and contribution documents.
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
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.
This PR adds a compact form of the GeoZarr spec that will define exactly the interpretation of GeoZarr that will be implemented by this library. This mini spec is compatible with the current editor's draft GeoZarr spec, but is much smaller and uses language that is more directed for guiding an implementation.
I am opening this in draft form so @emmanuelmathot can suggest additional constraints / rules / metadata that I have not included yet. For example, there are some minimal CF metadata fields that should probably be specified for downsampled Datasets (like
"grid_mapping").This spec diverges somewhat in recommending that collections of downsampled datasets (which I am calling "Multiscale Datasets") do not contain anything other than the downsampled datasets. This will make parsing easier, but it may also complicate some applications, so it would be great to know if this blocks off intended usage.
To illustrate what this means:
This layout would be permitted:
But this layout would be discouraged, and the code in this repo would not parse / generate it: