Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Proposal]: Dump ReferenceFileSystem spec for ZarrTiffStore that can be read natively as zarr

See original GitHub issue

Thank you so much for your work on this project. I just came across experimental aszarr and ZarrTiffStore and am so excited! I’d written some one-off stores wrapping tifffile to read different pyramidal images as zarr (for napari), but having this in tifffile is incredible!

I’m curious if you’ve seen the proposed JSON specification for describing a ReferenceFileSystem? Asking naively, and a bit selfishly, would it be possible to detect whether a ZarrTiffStore can be natively read by zarr and “export” one of these references?

I work on web-based tools for visualizing OME-TIFF / Zarr data, and it would be really useful to quickly create these references.

Here is an example viewing a multiscale tiff on the web using zarr.js, and this is the python script I wrote with the newest version of tifffile to generate the reference. I wonder if there is some way to generalize this script, but don’t have the familiarly with the underlying formats to know if this is a silly idea.

I notice that the TiffZarrStore handles all compression, so I know at least you need to detect whether the chunk compression is supported in Zarr.