Jeremy Maitin-Shepard

@joshmoore Can you help me understand a bit more the status of multiscale proposals and support? I think it might help if we can distinguish between Python APIs and data...

I thought this proposal is being discussed in the context of zarr rather than OME and was not aware of a proposal to specify the offset and scale other than...

My own interest is in a multiscale convention/format generally, not specifically related to xarray, and in particular not tied to the use of coordinate arrays, as I think for arrays...

Thanks for your explanation @rabernat . I think the distinction between zarr user attributes or zarr core attributes is not too important --- it seems quite reasonable to use zarr...

Thanks for your comments @joshmoore and @d-v-b. Thinking about this a bit more, I think it might be best if OME can just be made to also work for the...

Generating keys with lexicographic order matching the sort order is indeed a good idea. You can zero-pad up to the maximum possible length (e.g. assuming 64-bit index but that is...

In fact, none of the filters or codecs are described in the specification, the only reference for them is their source code. There is potentially room for improvement over the...

To be clear, zarr-python isn't my code. I develop two other zarr implementations (https://github.com/google/neuroglancer and https://github.com/google/tensorstore), so I'm definitely interested in interoperability of implementations. (Note that neither of those implementations...

It certainly could be nice to support in v3, but it has not really been discussed yet in the context of v3. In v2 it is represented with a dtype...

None of the codecs/filters (and vlenarray is a filter) are described in the v2 spec; they are all "optionally supported".