xtiff
A tiny Python 3 library for writing multi-channel TIFF stacks.
The aim of this library is to provide an easy way to write multi-channel image stacks for external visualization and analysis. It acts as an interface to the popular tifffile package and supports xarray DataArrays as well as numpy-compatible data structures.
To maximize compatibility with third-party software, the images are written in standard-compliant fashion, with minimal metadata and in TZCYX channel order. In particular, a minimal (but extensible) subset of the OME-TIFF standard is supported, enabling the naming of channels.
Installation
Install from pypi:
pip install xtiff
Usage
The package provides the following main function for writing TIFF files:
to_tiff(img, file, image_name=None, channel_names=None, image_date=None,
write_mode=WriteMode.OME_TIFF, big_tiff=None, big_tiff_size_threshold=4294967246,
byte_order=None, compression_type=None, compression_level=0, pixel_size=None,
pixel_depth=None, ome_xml=get_ome_xml, ome_xml_template=OME_XML_TEMPLATE_201606V2
**ome_xml_kwargs)
Documentation of the function parameters is available via Python's internal help system: help(xtiff.to_tiff)
In addition, the function get_ome_xml() is provided as the default OME-XML-generating function.
FAQ
Why should I care about TIFF? I use Zarr/NetCDF/whatever.
That's good! TIFF is an old and complex file format, has many disadvantages and is impractical for storing large images. However, it also remains one of the most widely used scientific image formats and is (at least partially) supported by many popular tools, such as ImageJ. With xtiff, you can continue to store your images in your favorite file format, while having the opportunity to easily convert them to a format that can be read by (almost) any tool.
Why can't I use the tifffile package directly?
Of course you can! Christoph Gohlke's tifffile package provides a very powerful and feature-complete interface for writing TIFF files and is the backend for xtiff. Essentially, the xtiff package is just a wrapper for tifffile. While you can in principle write any image directly with tifffile, in many cases, the flexibility of the TIFF format can be daunting. The xtiff package reduces the configuration burden and metadata to an essential minimum.
Change log
2019-12-12 v0.1.2 - Initial release
2019-12-12 v0.2.1 - Expose OME-XML to user
2019-12-12 v0.2.2 - Support for ome_xml_kwargs
2019-12-13 v0.3.0 - Simplified to_tiff interface
License
This project is licensed under the MIT license.
Metadata
Release files for xtiff 0.3.0
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 |
|---|---|---|---|---|
| xtiff-0.3.0.tar.gz | 8.2 kB | Without provenance | Details for xtiff-0.3.0.tar.gz |
Release files / xtiff-0.3.0.tar.gz
| Download URL | xtiff-0.3.0.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13f98ce06628a15882dda26e91da76fac50729c9ff5cccdb4bb759fc205caa51
|
|
BLAKE2b-256 checksum How to use checksums |
ac530bd09b30ca2ce51f4083a896cf1b46aceed9e7a7f381f19fe59d54137499
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0.post20191030 requests-toolbelt/0.9.1 tqdm/4.40.0 CPython/3.7.5
|
Security for xtiff 0.3.0
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.