You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: latest/index.bs
+9-8Lines changed: 9 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -289,16 +289,17 @@ The length of the `scale` and `translation` array MUST be the same as the length
289
289
The requirements (only `scale` and `translation`, restrictions on order) are in place to provide a simple mapping from data coordinates to physical coordinates while being compatible with the general transformation spec.
290
290
291
291
Each "multiscales" dictionary:
292
-
* MAY contain the field "coordinateTransformations", describing transformations that are applied to all resolution levels in the same manner.
293
-
The transformations MUST follow the same rules about allowed types, order, etc. as in "datasets:coordinateTransformations" and are applied after them.
294
-
They can for example be used to specify the `scale` for a dimension that is the same for all resolutions.
295
292
296
-
* SHOULD contain the field "name" which is informative to users but not sufficient for unique identifiation.
293
+
* MAY contain the field "coordinateTransformations", describing transformations that are applied to all resolution levels in the same manner.
294
+
The transformations MUST follow the same rules about allowed types, order, etc. as in "datasets:coordinateTransformations" and are applied after them.
295
+
They can for example be used to specify the `scale` for a dimension that is the same for all resolutions.
0 commit comments