Davis Bennett

To your first point, it's helpful to know that concurrent array creation _is_ a significant use pattern, and I see how implicit groups could be useful to avoid race conditions...

This offset is a transform, so it should probably be specified as part of a broader family of transforms, e.g. the ongoing OME-NGFF effort. As for changing the semantics of...

a few points in response to @jbms: > As for changing the behavior of __getitem__, that would indeed be the whole point. I agree that it could be a point...

@jbms can you explain why explicitly enumerating downscaling factors is preferred over the more explicit approach where each dataset declares its scale and offset?

> 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...

> So I don't think we can address multiscale without addressing these indexing issues. Agreed. Downsampling data necessarily generates a new coordinate grid for that data; Consumers need to know...

> none of the codecs are specified in the zarr v2 spec. This is important. It is not a deficiency of the zarr spec that the Blosc compressor isn't very...

I'm not too familiar with numpy string arrays but my impression is that an array of a variable-length type cannot use a contiguous memory buffer for the in-memory representation. As...

@jeromekelleher sorry to hear about these issues. Unfortunately, because the different Zarr implementations are independent entities, I don't think it's easy to gather exhaustive, accurate information about their feature-completeness in...

In particular, it looks like this repo is missing regular test runs, and a place to display the output of the test results, e.g. a docs page.