a robust way to determine dimensions and shape

[lazarusA]

This check is too brittle:

Browzarr/src/components/zarr/ZarrGetters.ts

Line 152 in c3ebe15

const hasTimeChunks = is4D ? fullShape[1]/chunkShape[0] > 1 : fullShape[0]/chunkShape[0] > 1

Things work if the order is

• time, Lon, lat or
• p, time, Lon, lat,

but it will fail if it is

• lon, lat, time !, which is a very common pattern.

Soon I will have use cases where things will be like

• lon, lat, depth or depth, lon, lat.

we already have functions for getting the dimension names and shapes, we will only need maybe a permutedims function, to be applied in the GetArray values (to get proper slices also), before passing them to the shaders, or maybe apply transforms directly there.

[TheJeran]

I definitely want to revisit all of this logic eventually. Presently stuff with 4D+ feels awkward and also there's no flexibility for dimension layout which is something I would like to address eventually. Permute dims is probably the next major thing I will look at.

[milankl]

Just to illustrate this issue I have a 96x48x1x81 array (column major) -- the vertical dimension is 1, so essentially a 2D array + time which just carries around a singleton dimension for consistency with 3D arrays + time. At the moment I cannot run an animation across time as the singleton dimension prevents that