The spec for "rotation" at https://ngff-spec.readthedocs.io/en/latest/specification.html#rotation states "The matrix MUST be stored as a 2D array either as json or in a zarr array".
Same is true for Affine.
However, the schema at
has the
rotation property as a list of numbers:
"rotation": {
"type": "array",
"items": {
"type": "number"
}
},
Whereas for Affine it supports a flat list OR a nested 2D list:
https://github.com/ome/ngff-spec/blob/9e65955df1b840bf955ca328b859722870807ae4/schemas/coordinate_transformation.schema#L240C32-L240C47
The schema above is currently causing validation failures if I have a 2D list for "rotation".
In the table at https://ngff-spec.readthedocs.io/en/latest/specification.html#coordinatetransformations-metadata the rotation description doesn't say that a 2D array should be used, and in the affine description of the table it says "affine transformation matrix stored as a flat array" which contradicts the spec above.
The spec for "rotation" at https://ngff-spec.readthedocs.io/en/latest/specification.html#rotation states "The matrix MUST be stored as a 2D array either as json or in a zarr array".
Same is true for Affine.
However, the schema at
ngff-spec/schemas/coordinate_transformation.schema
Line 262 in 9e65955
has the
rotationproperty as a list of numbers:Whereas for Affine it supports a flat list OR a nested 2D list:
https://github.com/ome/ngff-spec/blob/9e65955df1b840bf955ca328b859722870807ae4/schemas/coordinate_transformation.schema#L240C32-L240C47
The schema above is currently causing validation failures if I have a 2D list for "rotation".
In the table at https://ngff-spec.readthedocs.io/en/latest/specification.html#coordinatetransformations-metadata the
rotationdescription doesn't say that a2Darray should be used, and in theaffinedescription of the table it says "affine transformation matrix stored as a flat array" which contradicts the spec above.