bioio-ome-tiff
A BioIO reader plugin for reading OME TIFF files using tifffile
Documentation
See the full documentation on our GitHub pages site - the generic use and installation instructions there will work for this package.
Information about the base reader this package relies on can be found in the bioio-base repository here
Installation
Stable Release: pip install bioio-ome-tiff
Development Head: pip install git+https://github.com/bioio-devs/bioio-ome-tiff.git
Example Usage (see full documentation for more examples)
Install bioio-ome-tiff alongside bioio:
pip install bioio bioio-ome-tiff
This example shows a simple use case for just accessing the pixel data of the image
by explicitly passing this Reader into the BioImage. Passing the Reader into
the BioImage instance is optional as bioio will automatically detect installed
plug-ins and auto-select the most recently installed plug-in that supports the file
passed in.
from bioio import BioImage
import bioio_ome_tiff
img = BioImage("my_file.ome.tiff", reader=bioio_ome_tiff.Reader)
img.data
OmeTiffWriter
Import for the writer:
from bioio_ome_tiff.writers import OmeTiffWriter
The OmeTiffWriter lets you save image data to OME-TIFF files, supporting:
- Single- or multi-scene datasets with explicit dimension order
- Custom channel names, colors, and physical pixel sizes
- Automatic generation and validation of OME-XML metadata
- BigTIFF output for large (>2 GB) images
Example Usage
# Write a TCZYX dataset to OME-TIFF
image = numpy.ndarray([1, 10, 3, 1024, 2048])
OmeTiffWriter.save(image, "file.ome.tif")
# Write data with a specific dimension order
image = numpy.ndarray([10, 3, 1024, 2048])
OmeTiffWriter.save(image, "file.ome.tif", dim_order="ZCYX")
# Write multi-scene data, specifying channel names
image0 = numpy.ndarray([3, 10, 1024, 2048])
image1 = numpy.ndarray([3, 10, 512, 512])
OmeTiffWriter.save(
[image0, image1],
"file.ome.tif",
dim_order="CZYX", # will be applied to both scenes
channel_names=[["C00", "C01", "C02"], ["C10", "C11", "C12"]],
)
# Write data with a custom compression scheme
image = numpy.ndarray([1, 10, 3, 1024, 2048])
OmeTiffWriter.save(
image,
"file.ome.tif",
tifffile_kwargs={
"compression": "zlib",
"compressionargs": {"level": 8},
},
)
Issues
Click here to view all open issues in bioio-devs organization at once or check this repository's issue tab.
Development
See CONTRIBUTING.md for information related to developing the code.
Release files for bioio-ome-tiff 1.4.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 | |
|---|---|---|---|
| bioio_ome_tiff-1.4.0.tar.gz | 34.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bioio_ome_tiff-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 61.6 kB
Release files / bioio_ome_tiff-1.4.0.tar.gz
| Download URL | bioio_ome_tiff-1.4.0.tar.gz |
|---|---|
| Size | 34.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0073ff612926ea17c72a32f378d62361e282dd7afbc561e8c0a53316fd8d2e29
|
|
BLAKE2b-256 checksum How to use checksums |
b395fd5ccfb07c5159983a40746b1c0da1c7648918bcfdb940189bf52f7340d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 10, 2025.
Transparency logRelease files / bioio_ome_tiff-1.4.0-py3-none-any.whl
| Download URL | bioio_ome_tiff-1.4.0-py3-none-any.whl |
|---|---|
| Size | 27.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98107a847244a7b515c7a8c39b5119e67f4047b63661238b49b3d0cc36a86cd9
|
|
BLAKE2b-256 checksum How to use checksums |
ec88cdfc59ac1fb3db84d59d47b8afa3bcf539b8afabc86d8b5230909b6487f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 10, 2025.
Transparency log