Conformance test datasets: 18 Zarr v3 stores for v1 conventions#127
Open
wietzesuijker wants to merge 1 commit intozarr-developers:mainfrom
Open
Conformance test datasets: 18 Zarr v3 stores for v1 conventions#127wietzesuijker wants to merge 1 commit intozarr-developers:mainfrom
wietzesuijker wants to merge 1 commit intozarr-developers:mainfrom
Conversation
wietzesuijker
force-pushed
the
conformance-test-datasets
branch
2 times, most recently
from
7989827 to
8f93cf1
Compare
wietzesuijker
force-pushed
the
conformance-test-datasets
branch
from
8f93cf1 to
ea7cae2
Compare
wietzesuijker
changed the title
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.
Addresses #115.
18 Zarr v3 test stores (13 valid, 5 invalid) covering the three v1 convention schemas: proj:, spatial:, and multiscales.
Includes a sharded dataset (
spatial-sharded) to verify conventions work through thesharding_indexedcodec, and five invalid datasets testing schema rejection boundaries.Three validation layers:
generate_datasets.py --verify— self-check expected values (transform math, shapes, CRS codes)validate_schema.py— fetch upstream JSON schemas, validate all zarr.json files; invalid datasets must be rejectedvalidate_gdal.py— cross-implementation check with GDAL >= 3.13 (exit 2 if unavailable)All scripts return exit code 0/1/2, ready for CI.
Note: proj: CMO URLs use
zarr-experimentalto match upstream geo-proj schema.json const values. Will update when #126 resolves.See
test-datasets/README.mdfor dataset descriptions and implementer guidance.