zarr-python-n5
N5 utilities for zarr-python.
- Documentation: https://zarr-python-n5.readthedocs.io
Codecs
N5 Default Codec
Only whole-chunk reading is supported.
N5 Compressor support
| N5 compressor | Supported | Zarr bytes-to-bytes codec | Notes |
|---|---|---|---|
raw |
yes | n/a | Equivalent to omitted bytes-to-bytes codec |
blosc |
yes | blosc |
|
gzip |
yes | gzip |
|
zstd |
yes | zstd |
|
lz4 |
no | Incompatible codecs | |
xz |
no | No equivalent Zarr codec | |
jpeg |
no | Needs N5 documentation, Zarr codec | |
bzip2 |
no | No equivalent Zarr codec |
Stores
N5WrapperStore allows reading N5 data with DEFAULT-mode blocks through any Zarr store by converting metadata on the fly.
By default, this does not replicate the N5 behaviour of inferring an empty group where a metadata document does not exist.
To achieve this, wrap it in the provided ImplicitGroupWrapperStore.
Tools
This package provides n5tozarr, a command-line interface for converting N5 data to Zarr in-place.
The N5 metadata are left untouched, and no chunk data is altered, moved, or copied.
A zarr.json file is simply added to each Zarr node.
N5 attributes are extracted and added to the zarr.json attributes.
The full N5 metadata document is accessible inside the zarr.json in an attribute called _n5.
If a directory/prefix was empty and the existence of an N5 group was inferred,
the zarr.json attribute _implicit will be true.
Contributing
Use uv for project management.
Use just for common development tasks.
1 maintainer
Metadata
1 maintainer
Release files for zarr-n5 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zarr_n5-0.3.1.tar.gz | 11.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zarr_n5-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.6 kB
Release files / zarr_n5-0.3.1.tar.gz
| Download URL | zarr_n5-0.3.1.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
804ef5647d68e584b325956b5e886bcbe8b346e3e915fab02455b005e70bd1f1
|
|
BLAKE2b-256 checksum How to use checksums |
8b7e5e2d4eaebf04837385c4889f4aec0215147563f271df5492333261aaa570
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / zarr_n5-0.3.1-py3-none-any.whl
| Download URL | zarr_n5-0.3.1-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a24b7adc6cef1498ff0884ebe092b1a40ca07312eb3489a385604ea145a9ad4
|
|
BLAKE2b-256 checksum How to use checksums |
e61ea73d455120612620e5b6d52e07d7483258f742f12743a7fab793fd899d56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for zarr-n5 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
