enh: clarify CF metadata scope in GeoZarr mini-spec and update attribute definitions#133
Open
emmanuelmathot wants to merge 1 commit intomainfrom
Open
enh: clarify CF metadata scope in GeoZarr mini-spec and update attribute definitions#133emmanuelmathot wants to merge 1 commit intomainfrom
emmanuelmathot wants to merge 1 commit intomainfrom
Conversation
d-v-b
reviewed
Mar 16, 2026
| ### Attributes | ||
|
|
||
| There are no required attributes for Datasets. To qualify as a GeoZarr Dataset, the group must carry geospatial metadata via the `proj:` and `spatial:` conventions declared in its `zarr_conventions` attribute. | ||
| There are no required attributes for Datasets. To qualify as a GeoZarr Dataset, the group must carry geospatial metadata via the `proj:` and `spatial:` conventions declared in its `zarr_conventions` key. |
Contributor
There was a problem hiding this comment.
this is still a bit confusing -- aren't we saying that a geozarr dataset MUST have proj and spatial conventions declared in attributes?
There was a problem hiding this comment.
Suggested change
| There are no required attributes for Datasets. To qualify as a GeoZarr Dataset, the group must carry geospatial metadata via the `proj:` and `spatial:` conventions declared in its `zarr_conventions` key. | |
| To qualify as a GeoZarr Dataset, the group must carry geospatial metadata via the `proj:` and `spatial:` conventions declared in its `zarr_conventions` attribute. |
vincentsarago
requested changes
Mar 17, 2026
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
3 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.
Clarify the relationship between CF metadata and the GeoZarr specification, emphasizing that CF metadata is not required but can coexist with Zarr conventions. Update attribute definitions for consistency and clarity.
Follows-up on #129