Dan Allan

Inspired by discussion with @joshmoore at SciPy 2023, but I think not written down until now.

OK, so a "layout" is a standard Zarr on-disk format with a special interpretation layered on top---i.e. "You should interpret this group of arrays as a _table_ and assume that...

Nice! I don't think I'd seen that one yet. I'm working on a branch to update on our docs on "How Tiled Fits Into the Ecosystem". I'll include `simple-zarr-server` in...

@manzt We have exactly the same vision. Choosing the format and compression encoding works now, via HTTP content negotiation headers, e.g. ``` curl -H 'Accept: application/json' 'https://tiled-demo.blueskyproject.io/api/v1/array/full/generated/medium_image?slice=:5,:5 ``` We also...

It occurred to me later `downsample_method` as implemented there assumes we are using the same downsample method for all axes, whereas the original approach we considered here, `?slice=:,::mean(2),::mean(2)`, supports a...

Actually I think this may be relevant. If we expose Tiled as "a Zarr", i.e. add a `/zarr/v3/{path}` endpoint that is Zarr-like, what should we do with tables? If we...

Yeah, that's fair enough, for sure. At an API level, we support: ``` /array/full/{path}?slice=... # global indices ``` or ``` /array/block/{path}?block=0,0,0&slice=...` # block-local indices ``` where `block` is a block...

Great. I think that is exactly what we intend with this issue.

I noticed that datetime types are missing. Per @joshmore, it may be (is likely to be) reintroduced as a "extension" as v3 takes shape. I think we may be able...

Tiled supports numpy record arrays a.k.a. [structured arrays](https://numpy.org/doc/stable/user/basics.rec.html). We have an important use case for it. We may need to wait for Zarr V3 extension data types to be more...