From b544854f279df7294fcf26b69c8d4dc71634d707 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Tue, 5 May 2026 17:58:59 +0100 Subject: [PATCH 1/2] Add explanation of coverage dimensions in documentation Clarify the limits of coverage domain dimensions in CoverageJSON. Addresses Issue #220 --- standard/clause_0_front_material.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/standard/clause_0_front_material.adoc b/standard/clause_0_front_material.adoc index 453b6c07f6..d7ab0052a9 100644 --- a/standard/clause_0_front_material.adoc +++ b/standard/clause_0_front_material.adoc @@ -34,6 +34,8 @@ The next simplest use case is to put data values for each variable (parameter) i A sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server. +The abstract, conceptual, definition of a coverage allows its Domain to have any number of coordinate dimensions, such 1 (e.g. timeseries), 2 (e.g. an area), 3 (e.g. a volume), 4 (e.g. an animated, multi-band, satellite image) or more. The coverageJSON Standard is currently restricted to 4 spatio-temporal dimensions (x,y,z,t). + [keywords] [[keywords]] == Keywords From 58e008a3a5d1e17b3dffded0d85586b37fd9d4a3 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 09:58:09 +0100 Subject: [PATCH 2/2] Clarified Domain Type restrictions Clarify coverage definition and expand on dimensions and parameters. --- standard/clause_0_front_material.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard/clause_0_front_material.adoc b/standard/clause_0_front_material.adoc index d7ab0052a9..ee74d0bc66 100644 --- a/standard/clause_0_front_material.adoc +++ b/standard/clause_0_front_material.adoc @@ -34,7 +34,7 @@ The next simplest use case is to put data values for each variable (parameter) i A sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server. -The abstract, conceptual, definition of a coverage allows its Domain to have any number of coordinate dimensions, such 1 (e.g. timeseries), 2 (e.g. an area), 3 (e.g. a volume), 4 (e.g. an animated, multi-band, satellite image) or more. The coverageJSON Standard is currently restricted to 4 spatio-temporal dimensions (x,y,z,t). +The abstract, conceptual, definition of a coverage allows its Domain to have any number of coordinate dimensions, such 1 (e.g. a timeseries), 2 (e.g. an area), 3 (e.g. a volume), 4 (e.g. an animated, multi-band, satellite image) or more. Similarly, a coverage can have multiple ranges or parameters (e.g. pressure, temperature and humidity across a domain). The coverageJSON Standard supports this definition but the convenient, predefined Domain Types are currently restricted to 4 spatio-temporal dimensions (x,y,z,t). [keywords] [[keywords]]