Josh Moore

> I'm not sure what the deal with distribution of 3i's jar is see https://www.intelligent-imaging.com/technical-answers and http://sites.imagej.net/SlideBook/

cc: @RichardMyers (https://github.com/ome/bioformats/pull/2289)

Thanks for the link, @jhamman. The most immediate issue I ran into when trying to use xarray with OME-Zarr data does seem _similar_. A rough representation of one multiscale image...

Happy to provide assistance on the image pyramid (i.e. "[multiscale](https://github.com/zarr-developers/zarr-specs/issues/50)") use case.

Picking up on @dcherian's https://github.com/pydata/xarray/issues/4118#issuecomment-806954634 and @rabernat's https://github.com/ome/ngff/issues/48#issuecomment-833456889, Zarr was also accepted to the second round and certainly references this issue in case we want to sync up. (Apologies if...

As mentioned to @manzt elsewhere, this has raised its head for us as well recently (cc: @davehorsfall). For my part, I will be working try to pin down the specification...

> https://github.com/hms-dbmi/viv/issues/290#issuecomment-718886080 OME-Zarr is a spec that describes how to organize _many_ (zarr) arrays within a hierarchy with associated metadata. Is the same not true of OME-XML/OME-TIFF modulo "list of...

:) Excited as well, hopefully I'm not missing the point above. From my perspective, there's not too much new in the OME-Zarr spec beyond OME-TIFF. Each OME-TIFF can have an...

> ... or list of nD-Arrays if multiscale This reminds me of napari where the the base contract for a plugin/loader is to always return a list of layers where...

@ttung: what type of environment are you talking about standing up here?