Skip to content

Commit

Permalink
Defer transform type definitions to [[#trafo-md]] table
Browse files Browse the repository at this point in the history
Reduce the number of definitions.
  • Loading branch information
thewtex committed Oct 4, 2023
1 parent 4dfc7d2 commit 1a55fa1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion 0.4/index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -367,7 +367,7 @@ to the current zarr group. The "path"s MUST be ordered from largest (i.e. highes

Each "datasets" dictionary MUST have the same number of dimensions and MUST NOT have more than 5 dimensions. The number of dimensions and order MUST correspond to number and order of "axes".
Each dictionary in "datasets" MUST contain the field "coordinateTransformations", which contains a list of transformations that map the data coordinates to the physical coordinates (as specified by "axes") for this resolution level.
The transformations are defined according to [[#trafo-md]]. The transformation MUST only be of type `identity`, `translation` or `scale`.
The transformations are defined according to [[#trafo-md]]. The transformation MUST only be of types defined in [[#trafo-md]].
They MUST contain exactly one `scale` transformation that specifies the pixel size in physical units or time duration. If scaling information is not available or applicable for one of the axes, the value MUST express the scaling factor between the current resolution and the first resolution for the given axis, defaulting to 1.0 if there is no downsampling along the axis.
It MAY contain exactly one `translation` that specifies the offset from the origin in physical units. If `translation` is given it MUST be listed after `scale` to ensure that it is given in physical coordinates.
The length of the `scale` and `translation` array MUST be the same as the length of "axes".
Expand Down

0 comments on commit 1a55fa1

Please sign in to comment.