Accept zipped zarr stores as an input for spatialdata.read_zarr(). Must also have ome-zarr-py ZarrLocation changes.#1141
Conversation
|
Hi again! I got an update from @will-moore this morning that ome-zarr is preparing to fully deprecate |
|
Hi, wanted to chime in to voice my support for the Zipped zarr directory use case as another member of the HuBMAP consortium. For further background, Vitessce, which is used by HuBMAP for visualization purposes, also supports reading Zipped AnnData objects, OME-Zarr images, and SpatialData objects (code). @pennycuda , I also wonder whether the open pull request at #1107 will resolve the ZipStore usage issues already (once it is finalized/merged). It seems to generalize the function signature of
(Another related point to mention is the OME-Zarr proposal called RFC-9 to define a new |
|
Thanks @keller-mark for your support! I will look at that PR as well and test to see if any changes need to be made for it to read zipped zarr stores as well. I also read about the |

This branch introduces functionality to allow zipped zarr stores as an input for the
read_zarr()function. It will only work with changes to ome-zarr-py'sZarrLocationclass made in the following PR:ome/ome-zarr-py#587
This was motivated by HuBMAP Consortium's desire to reduce the number of files in our filesystem while maintaining our requirement that our output files be easily readable by our users. HuBMAP has already built other infrastructure to support zipped zarr stores for AnnData objects as well.
Please let me know what changes I need to make to get this PR merged; I am happy to work with you all!