Skip to content

Commit

Permalink
Add reference to xarray compatibility (re: _ARRAY_DIMENSIONS, ref #217
Browse files Browse the repository at this point in the history
)
  • Loading branch information
tcompa committed Oct 17, 2023
1 parent ac43558 commit 3fca4de
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion 0.4/index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ For this example we assume an image with 5 dimensions and axes called `t,c,z,y,x
├── .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
│ # may also contain "_ARRAY_DIMENSIONS" if this group directly contains multi-scale arrays.
│ # may also contain "_ARRAY_DIMENSIONS" for compatibility with xarray if this group directly contains multi-scale arrays.
├── 0 # Each multiscale level is stored as a separate Zarr array,
│ ... # which is a folder containing chunk files which compose the array.
Expand Down
2 changes: 1 addition & 1 deletion latest/index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ For this example we assume an image with 5 dimensions and axes called `t,c,z,y,x
├── .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
│ # may also contain "_ARRAY_DIMENSIONS" if this group directly contains multi-scale arrays.
│ # may also contain "_ARRAY_DIMENSIONS" for compatibility with xarray if this group directly contains multi-scale arrays.
├── 0 # Each multiscale level is stored as a separate Zarr array,
│ ... # which is a folder containing chunk files which compose the array.
Expand Down

0 comments on commit 3fca4de

Please sign in to comment.