This release is a pre-release and may not be stable for production use.
napari-hdf5-labels-io
napari plugin to store napari projects in a .h5 file. Label layer are stored in a sparse representation (COO list).
This napari plugin was generated with Cookiecutter using with @napari's cookiecutter-napari-plugin template.
Description
This napari plugin provides a writer and reader to store existing layers in the current napari window, all the metadata is stored as well in a HDF5 file. All the stored preferences are included when a project file is opened.
Label layers are stored in a coordinate list sparse representation with the Sparse module to keep the project file size minimum when possible (aiming to implement this in other layers in the future).
HDF5 file architecture
The project file is a HDF5 generated with the h5py module. The file groups correspond to the different napari layer types and the layer metadata is stored as attributes of each layer.
In the case of the meta dictionary which is nested in the LayerData meta dictionary (napari IO), new keys are generated in the outer dictionary to use them as h5 dataset attributes. This nested dictionary architecture is reconstructed by the reader to ensure format compatibility.
Installation
You can install napari-hdf5-labels-io via pip:
pip install napari-hdf5-labels-io
Contributing
Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.
License
Distributed under the terms of the GNU GPL v3.0 license, "napari-hdf5-labels-io" is free and open source software.
Issues
If you encounter any problems, please file an issue along with a detailed description.
Metadata
Release files for napari-hdf5-labels-io 0.3.dev16
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 | Actions |
|---|---|---|---|---|
| napari-hdf5-labels-io-0.3.dev16.tar.gz | 30.7 kB | Without provenance | Details for napari-hdf5-labels-io-0.3.dev16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| napari_hdf5_labels_io-0.3.dev16-py3-none-any.whl | Python 3 | none | any | Details for napari_hdf5_labels_io-0.3.dev16-py3-none-any.whl |
Total release size: 51.5 kB
Release files / napari-hdf5-labels-io-0.3.dev16.tar.gz
| Download URL | napari-hdf5-labels-io-0.3.dev16.tar.gz |
|---|---|
| Size | 30.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a16a66b3480b374403f6dd64d03de5cf3624d3072783f330d7d2baf7f613dac6
|
|
BLAKE2b-256 checksum How to use checksums |
dc2fc37145a1dd5d10e10f70c85c34bc7e8dcdbb0e364a774b3e3fd8fb0cf953
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Release files / napari_hdf5_labels_io-0.3.dev16-py3-none-any.whl
| Download URL | napari_hdf5_labels_io-0.3.dev16-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b579bf23c07071611b159a098ef43827937eaa23df4c44bf8f72ef78ce4964d1
|
|
BLAKE2b-256 checksum How to use checksums |
eab49937fdfba5067dfcf771523d7d73e3daa06dfb1d7061d1660362cb242bc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for napari-hdf5-labels-io 0.3.dev16
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.