Josh Moore

Gotcha. Seems straight-forward enough. Happy to add something but I'll need the list of datasets for consideration.

> Since both are in the same group (the root group), this is an inconsistency > because one variable says y=930 and the other says y=465. > You might contact...

> It is actually an XArray problem since the _ARRAY_DIMENSIONS attribute > is not recognized in Zarr V2 (or has that changed?) It's definitely true that Zarr v2 is agnostic...

> I would suggest two changes to the OME format: Suggestion noted, thanks, @DennisHeimbigner, but I don't think we should open that conversation here. Leaving nczarr, s3, and http out...

> Speaking for myself, I say no. The fact that they cannot be read by Xarray > makes it clear that having an inconsistent _ARRAY_DIMENSION shape > mapping is just...

Thanks for the explanation, @DennisHeimbigner. I definitely understand the primary goal. But is there also a sub-goal of mapping _all_ pure Zarr datasets to some subset of netcdf-4?

I guess I defer there to @dzenanz' testing since in https://github.com/Unidata/netcdf-c/issues/2474#issuecomment-1211459122 there appear to be Zarr datasets that aren't openable. If it would help to copy them somewhere for testing,...

Seconding @r03ert0 's [comment](https://github.com/zenodo/zenodo/issues/1089#issuecomment-587725585), a number of microscopy formats are organized into directories where the path information is critical for interpreting the data (e.g. defining the ordering of a time...

General :thumbsup:  and a few comments: * The support level of python-bioformats (see [this thread](https://forum.image.sc/t/ongoing-support-for-python-bioformats/49683)) would likely suggest using something else in the Python space * @tlambert03 & co. recently...

As well as https://github.com/google/tensorstore and in C, https://github.com/Unidata/netcdf-c . Thanks to @jakirkham and @grlee77 for the heads up about this issue. I'll try to follow along in case there are...