Support OME-TIFF through custom OmeTiffStore
#254
Conversation
This file contains 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
manzt
changed the title
OmeTiffStore
manzt
force-pushed
the
manzt/ome-tiff
branch
3 times, most recently
from
8021b71 to
07a35a6
Compare
Adds experimental support for OME-TIFF using a custom Zarr store (`OmeTiffStore`). Internally, a `geotiff.GeoTIFF` image is mapped to a multiscale Zarr dataset. This implementation prevents OME-XML data model from leaking out like in Viv/Avivator. Instead, OME-TIFF metadata MUST be mapped to NGFF to tell Vizarr how to render. Caveats: Does not support interleaved data nor multi-image OME-TIFFs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds experimental support for OME-TIFF using a custom Zarr store (
OmeTiffStore). Internally, ageotiff.GeoTIFFimage is mapped to a multiscale Zarr dataset. This implementation is experimental, and care has been taken to prevent the OME-XML data model from leaking out like in Viv/Avivator. Instead, OME-TIFF metadata MUST be mapped to NGFF to tell Vizarr how to render.Caveats: Does not support interleaved data nor multi-image OME-TIFFs (yet).
demo: https://deploy-preview-254--vizarr.netlify.app/?source=https://viv-demo.storage.googleapis.com/Vanderbilt-Spraggins-Kidney-MxIF.ome.tif
I'm thinking that it might be preferable to use a custom protocol (e.g.,
ome-tiff://) to prefix the sources explicitly that are OME-TIFF (rather that using the URL to determine which store to use).If we were to upstream this into Viv, I also think it would be useful to put the OME-XML string somewhere in the store. But the core idea would be that we don't expose a datastructure with the parsed XML other than what we can translate to OME-NGFF.