Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include _ARRAY_DIMENSIONS metadata? #563

Closed
tcompa opened this issue Oct 11, 2023 · 3 comments
Closed

Include _ARRAY_DIMENSIONS metadata? #563

tcompa opened this issue Oct 11, 2023 · 3 comments

Comments

@tcompa
Copy link
Collaborator

tcompa commented Oct 11, 2023

Ref https://ngff.openmicroscopy.org/0.4/#image-layout

├── .zgroup               # Each image is a Zarr group, or a folder, of other groups and arrays.
├── .zattrs               # Group level attributes are stored in the .zattrs file and include
│                         # "multiscales" and "omero" (see below). In addition, the group level attributes
│                         # must also contain "_ARRAY_DIMENSIONS" if this group directly contains multi-scale arrays.

Should we include this additional information?

@tcompa
Copy link
Collaborator Author

tcompa commented Oct 11, 2023

EDIT: ome/ome-zarr-py#166 (comment) says that

Closing for now, the requirement has been removed from the 0.4 specification. Various layout currently allow to use xarray together with OME Zarr datasets. Hopefully the discussion in ome/ngff#48 will converge towards a set of recommendations that can be reintroduced later allowing compatibillity.

Thus I guess this is a typo in the specs?

@tcompa tcompa changed the title Include _ARRAY_DIMENSIONS metadata Include _ARRAY_DIMENSIONS metadata? Oct 11, 2023
@tcompa
Copy link
Collaborator Author

tcompa commented Oct 17, 2023

@tcompa
Copy link
Collaborator Author

tcompa commented Oct 17, 2023

Closing, as of ome/ngff#217 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant