From 61ff2585b56f3e9e737bd6f3ec6331eceaa751a5 Mon Sep 17 00:00:00 2001 From: Johannes Soltwedel <38459088+jo-mueller@users.noreply.github.com> Date: Fri, 28 Aug 2026 09:35:50 +0200 Subject: [PATCH 1/2] chore: fix broken cross-reference --- index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.md b/index.md index da28878a..ee3b1c61 100644 --- a/index.md +++ b/index.md @@ -234,7 +234,7 @@ refer to different physical entities and therefore should not be analyzed jointl Tasks that require images, annotations, regions of interest, etc., SHOULD ensure that they are in the same coordinate system (same name and location within the Zarr hierarchy, with identical axes) or can be transformed to the same coordinate system before doing analysis. -See the [example below](spec:example:coordinate_transformation). +See the [example below](spec:example:coordinate_transformation_scale). #### "axes" metadata (axes-md)= From b3560a5a887c7c696002cfdfc49b12bf3a8cb322 Mon Sep 17 00:00:00 2001 From: Johannes Soltwedel <38459088+jo-mueller@users.noreply.github.com> Date: Fri, 28 Aug 2026 09:38:41 +0200 Subject: [PATCH 2/2] fix: update references --- index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.md b/index.md index ee3b1c61..31e1bb77 100644 --- a/index.md +++ b/index.md @@ -234,7 +234,7 @@ refer to different physical entities and therefore should not be analyzed jointl Tasks that require images, annotations, regions of interest, etc., SHOULD ensure that they are in the same coordinate system (same name and location within the Zarr hierarchy, with identical axes) or can be transformed to the same coordinate system before doing analysis. -See the [example below](spec:example:coordinate_transformation_scale). +See the [example below](#spec:example:coordinate_transformation_scale). #### "axes" metadata (axes-md)= @@ -1556,7 +1556,7 @@ In the `zarr.json` under the image.zarr group, an explicit `identity` transform the coordinate system named `"physical"` in the multiscales metadata of the original image is the same as the coordinate system named `"physical"` in the multiscales metadata of the label image: -```{literalinclude} examples/multiscales_strict/multiscale_reference_to_label.json +```{literalinclude} examples/multiscales_strict/multiscales_reference_to_label.json :language: json ```