Document Zarr encoding options#11343
Draft
omribz156 wants to merge 1 commit into
Draft
Conversation
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
1 participant
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.
Description
Closes #9987.
This adds a short
Dataset.to_zarrpointer for Zarr-specific encoding keys and clarifies the Zarr v3 codec split in the I/O guide:compressorsfor bytes-to-bytes codecs andserializerfor array-to-bytes codecs. The text keeps codec construction details with zarr-python.Verification:
git diff --checkpython -m py_compile xarray\core\dataset.pysphinxis not installed in this environment.Checklist
whats-new.rstapi.rstAI Disclosure