Custom chunk shape

[will-moore]

Currently, for non-tiled images in OMERO, the default chunk size is a whole XY 2D plane (single ZCT).
For "Big" tiled images, the default chunks are set by the API re.getTileSize() which can give sub-optimal sizes. E.g. in omero-cli-zarr we ignore this and just use 1024 x 1024 chunks (same as bioformats2raw).

omero-web-zarr/omero_web_zarr/views.py

Line 143 in 67bb245

def get_chunk_shape(image):

These behaviours correspond to typical "2D" viewers, but might not be suitable for 3D viewers.

Possible options:

• provide different endpoints for 2D vv 3D chunks. E.g. /zarr/v0.4/image/2D/[ID].zarr, /zarr/v0.4/image/3D/[ID].zarr.
• Possible to imagine support for nD but probably not worth it, e.g. chunks of (10, 1, 256, 256) could be /zarr/v0.4/chunk/10/1/256/256/image/[ID].zarr or /zarr/v0.4/chunk/10.1.256.256/image/[ID].zarr but you'd have to first find the size of the image via /zarr/v0.4/image/[ID].zarr/0/.zarray (which would give you shape and default chunks).
• Query parameters are possible, but harder to teach the library that loads chunks to include the query string on every call. E.g. you couldn't do this with existing vizarr etc as you could do with the other strategies above.