From 9868aac2e4efe5fa9ffca442f04884967239dab8 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 25 Mar 2026 21:48:41 +0000 Subject: [PATCH 01/10] Update clause_specification_text.adoc --- standard/clause_specification_text.adoc | 28 +++++++++++++++++++++++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 79c1795cb..187db7571 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1624,7 +1624,7 @@ Coverage example: //### 11.9. Polygon ==== Polygon -Polygons in this domain domain type are defined equally to GeoJSON, except that they can only contain `[x,y]` positions (and not `z` or additional coordinates): +Polygons in this domain domain type are defined equivalent to GeoJSON, except that they can only contain `[x,y]` positions (and not `z` or additional coordinates): - A LinearRing is an array of 4 or more `[x,y]` arrays where each of `x` and `y` is a coordinate value. The first and last `[x,y]` elements are identical. - A Polygon is an array of LinearRing arrays. For Polygons with multiple rings, the first MUST be the exterior ring and any others MUST be interior rings or holes. @@ -1632,7 +1632,7 @@ Polygons in this domain domain type are defined equally to GeoJSON, except that - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A Polygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. -Domain example: +Domain example of a Simple Polygon: [%unnumbered%] ```json @@ -1654,6 +1654,30 @@ Domain example: } ``` +Domain example of a Polygon with two holes: + +[%unnumbered%] +```json +{ + "type": "Domain", + "domainType": "Polygon", + "axes": { + "composite": { + "dataType": "polygon", + "coordinates": ["x","y"], + "values": [ + [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] + [ [100.3, 0.2], [100.3, 0.4], [100.5, 0.4], [100.5, 0.2], [100.3, 0.2] ] + [ [100.7, 0.6], [100.8, 0.8], [100.9, 0.6], [100.7, 0.6] ] ] + ] + }, + "z": { "values": [2] }, + "t": { "values": ["2008-01-01T04:00:00Z"] } + }, + "referencing": [...] +} +``` + Coverage example: [%unnumbered%] From da76d366e881894c1af9d092c94a2e4a1d25c4bc Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 25 Mar 2026 22:17:33 +0000 Subject: [PATCH 02/10] Update clause_specification_text.adoc Added clarifying text and improved examples for MultiPolygon domain --- standard/clause_specification_text.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 187db7571..ae43c25c9 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1737,7 +1737,7 @@ Domain example: ] }, "z": { "values": [2] }, - "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z"] } + "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z","2008-01-01T06:00:00Z] } }, "referencing": [...] } @@ -1761,7 +1761,7 @@ Coverage example: ] }, "z": { "values": [2] }, - "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z"] } + "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z","2008-01-01T05:00:00Z] } }, "referencing": [...] }, @@ -1773,7 +1773,7 @@ Coverage example: "type" : "NdArray", "dataType": "float", "axisNames": ["t"], - "shape": [2], + "shape": [3], "values" : [...] } } @@ -1787,6 +1787,7 @@ Coverage example: - A domain with MultiPolygon domain type MUST have the axis `"composite"` where the values are Polygons. Polygons are defined in the Polygon domain type. - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A MultiPolygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. +- A MultiPolygon may represent several polygons that define non-contiguous regions of one underlying coverage range. It is not intended to represent several polygons that are separate coverages each with their own separate ranges. The latter case is a collection of coverages. Domain example: @@ -1874,7 +1875,7 @@ Domain example: ] }, "z": { "values": [2] }, - "t": { "values": ["2008-01-01T04:00:00Z", "2010-01-01T00:00:00Z"] } + "t": { "values": ["2008-01-01T00:00:00Z", "2010-01-01T00:00:00Z", "2012-01-01T00:00:00Z"] } }, "referencing": [...] } From df1d16ded02cdfca8fcb7710ba85851607ccad9a Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 25 Mar 2026 22:39:59 +0000 Subject: [PATCH 03/10] Update clause_specification_text.adoc improved punctuation --- standard/clause_specification_text.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index ae43c25c9..73902a491 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1632,7 +1632,7 @@ Polygons in this domain domain type are defined equivalent to GeoJSON, except th - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A Polygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. -Domain example of a Simple Polygon: +Domain example of a simple Polygon: [%unnumbered%] ```json @@ -1654,7 +1654,7 @@ Domain example of a Simple Polygon: } ``` -Domain example of a Polygon with two holes: +Domain example of a Polygon with two holes, one square, the other triangular: [%unnumbered%] ```json @@ -1787,7 +1787,7 @@ Coverage example: - A domain with MultiPolygon domain type MUST have the axis `"composite"` where the values are Polygons. Polygons are defined in the Polygon domain type. - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A MultiPolygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. -- A MultiPolygon may represent several polygons that define non-contiguous regions of one underlying coverage range. It is not intended to represent several polygons that are separate coverages each with their own separate ranges. The latter case is a collection of coverages. +- A MultiPolygon is intended to represent several polygons, possibly with holes, that define non-contiguous regions of one underlying coverage range. It is not intended to represent several polygons that are separate coverages, each with their own separate ranges. The latter case is a collection of coverages. Domain example: From 110ef385e5e0742b4302267e2ea7dae6d0cbda7d Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 11:57:00 +0100 Subject: [PATCH 04/10] Clarify MultiPolygon representation in documentation Used Jon Blower's re-phrasing --- standard/clause_specification_text.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 73902a491..054ea8394 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1787,7 +1787,7 @@ Coverage example: - A domain with MultiPolygon domain type MUST have the axis `"composite"` where the values are Polygons. Polygons are defined in the Polygon domain type. - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A MultiPolygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. -- A MultiPolygon is intended to represent several polygons, possibly with holes, that define non-contiguous regions of one underlying coverage range. It is not intended to represent several polygons that are separate coverages, each with their own separate ranges. The latter case is a collection of coverages. +- A MultiPolygon uses multiple polygons to represent non-contiguous regions, which are collectively treated as a single coverage domain, with a single associated range value. For example the MultiPolygon could represent the individual islands within a country, associated with the total population of that country. Domain example: From 2bc94f306c220419014310a205a4826060521cd8 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 12:08:42 +0100 Subject: [PATCH 05/10] Update coverage examples for Polygon with holes Added @awarde's suggested example of a coverage of a polygon with holes --- standard/clause_specification_text.adoc | 43 +++++++++++++++++++++++-- 1 file changed, 40 insertions(+), 3 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 054ea8394..b57eaf746 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1654,6 +1654,41 @@ Domain example of a simple Polygon: } ``` +Coverage example of a simple Polygon: + +[%unnumbered%] +```json +{ + "type" : "Coverage", + "domain" : { + "type": "Domain", + "domainType": "Polygon", + "axes": { + "composite": { + "dataType": "polygon", + "coordinates": ["x","y"], + "values": [ + [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] ] + ] + }, + "z": { "values": [2] }, + "t": { "values": ["2008-01-01T04:00:00Z"] } + }, + "referencing": [...] + }, + "parameters" : { + "temperature": {...} + }, + "ranges" : { + "temperature" : { + "type" : "NdArray", + "dataType": "float", + "values" : [...] + } + } +} +``` + Domain example of a Polygon with two holes, one square, the other triangular: [%unnumbered%] @@ -1678,7 +1713,7 @@ Domain example of a Polygon with two holes, one square, the other triangular: } ``` -Coverage example: +Coverage example of a Polygon with two holes, one square, the other triangular: [%unnumbered%] ```json @@ -1692,7 +1727,9 @@ Coverage example: "dataType": "polygon", "coordinates": ["x","y"], "values": [ - [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] ] + [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] + [ [100.3, 0.2], [100.3, 0.4], [100.5, 0.4], [100.5, 0.2], [100.3, 0.2] ] + [ [100.7, 0.6], [100.8, 0.8], [100.9, 0.6], [100.7, 0.6] ] ] ] }, "z": { "values": [2] }, @@ -1707,7 +1744,7 @@ Coverage example: "temperature" : { "type" : "NdArray", "dataType": "float", - "values" : [...] + "values" : [273.15] } } } From 39c4caa0c65c51da0ad4e77daf6238ebe3de8dd0 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 12:38:29 +0100 Subject: [PATCH 06/10] Fix formatting and clarify examples for polygons added coverage example for MultiPolygon with holes --- standard/clause_specification_text.adoc | 115 ++++++++++++++++++++++-- 1 file changed, 110 insertions(+), 5 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index b57eaf746..6dff210cf 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1624,7 +1624,7 @@ Coverage example: //### 11.9. Polygon ==== Polygon -Polygons in this domain domain type are defined equivalent to GeoJSON, except that they can only contain `[x,y]` positions (and not `z` or additional coordinates): +Polygons in this domain type are defined equivalent to GeoJSON, except that they can only contain `[x,y]` positions (and not `z` or additional coordinates): - A LinearRing is an array of 4 or more `[x,y]` arrays where each of `x` and `y` is a coordinate value. The first and last `[x,y]` elements are identical. - A Polygon is an array of LinearRing arrays. For Polygons with multiple rings, the first MUST be the exterior ring and any others MUST be interior rings or holes. @@ -1758,7 +1758,7 @@ Coverage example of a Polygon with two holes, one square, the other triangular: - A domain with PolygonSeries domain type MAY have the axis `"z"` which MUST have a single coordinate value only. - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. -Domain example: +Domain example of a PolygonSeries: [%unnumbered%] ```json @@ -1780,7 +1780,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a PolygonSeries: [%unnumbered%] ```json @@ -1826,7 +1826,7 @@ Coverage example: - A MultiPolygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. - A MultiPolygon uses multiple polygons to represent non-contiguous regions, which are collectively treated as a single coverage domain, with a single associated range value. For example the MultiPolygon could represent the individual islands within a country, associated with the total population of that country. -Domain example: +Domain example of a MultiPolygon: [%unnumbered%] ```json @@ -1849,7 +1849,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a MultiPolygon: [%unnumbered%] ```json @@ -1887,6 +1887,111 @@ Coverage example: } ``` +Domain example of a MultiPolygon where one polygon has a hole: + +[%unnumbered%] +```json +{ + "type": "Coverage", + "domain": { + "type": "Domain", + "domainType": "MultiPolygon", + "axes": { + "composite": { + "dataType": "polygon", + "coordinates": ["x", "y"], + "values": [ + [ + [ + [40, 40], + [20, 45], + [45, 30], + [40, 40] + ] + ], + [ + [ + [20, 35], + [10, 30], + [10, 10], + [30, 5], + [45, 20], + [20, 35] + ], + [ + [30, 20], + [20, 15], + [20, 25], + [30, 20] + ] + ] + ] + }, + "z": { + "values": [2] + }, + "t": { + "values": ["2008-01-01T04:00:00Z"] + } + }, + "referencing": [...] + }, + "parameters": { + }, + "ranges": { + "temperature": { + "type": "NdArray", + "dataType": "float", + "axisNames": ["composite"], + "shape": [2], + "values": [23.1, 24.7] + } + } +} +``` + +Coverage example of a MultiPolygon where one of the Polygons has a hole. + +[%unnumbered%] +```json +{ + "type": "Coverage", + "domain": { + "type": "Domain", + "domainType": "MultiPolygon", + "axes": { + "composite": { + "dataType": "polygon", + "coordinates": ["x", "y"], + "values": [ + [[[40, 40],[20, 45],[45, 30],[40, 40]]], + [[[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]], + [[30, 20],[20, 15],[20, 25],[30, 20]] + ] + }, + "z": { + "values": [2] + }, + "t": { + "values": ["2008-01-01T04:00:00Z"] + } + }, + "referencing": [...] + }, + "parameters": { + }, + "ranges": { + "temperature": { + "type": "NdArray", + "dataType": "float", + "axisNames": ["composite"], + "shape": [2], + "values": [23.1, 24.7] + } + } +} +``` + [[multipolygonseries]] //### 11.12. MultiPolygonSeries ==== MultiPolygonSeries From 452d9bbc80171898ba2c7a8305e3a1f0e8ff2a9a Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 14:20:57 +0100 Subject: [PATCH 07/10] Update domain examples and descriptions in clause spec Correct the nesting of brackets --- standard/clause_specification_text.adoc | 82 +++++++++---------------- 1 file changed, 30 insertions(+), 52 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 6dff210cf..430d98873 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1059,7 +1059,7 @@ Requirements for all domain types defined in this OGC Community Standard: - A domain with Grid domain type MUST have the axes `"x"` and `"y"` and MAY have the axes `"z"` and `"t"`. -Domain example: +Domain example of a Grid: [%unnumbered%] ```json @@ -1076,7 +1076,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a Grid: [%unnumbered%] ```json @@ -1114,7 +1114,7 @@ Coverage example: - A domain with VerticalProfile domain type MUST have the axes `"x"`, `"y"`, and `"z"`, where `"x"` and `"y"` MUST have a single coordinate value only. - A domain with VerticalProfile domain type MAY have the axis `"t"` which MUST have a single coordinate value only. -Domain example: +Domain example of a VerticalProfile: [%unnumbered%] ```json @@ -1131,7 +1131,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a VerticalProfile: [%unnumbered%] ```json @@ -1170,7 +1170,7 @@ Coverage example: - A domain with PointSeries domain type MUST have the axes `"x"`, `"y"`, and `"t"` where `"x"` and `"y"` MUST have a single coordinate value only. - A domain with PointSeries domain type MAY have the axis `"z"` which MUST have a single coordinate value only. -Domain example: +Domain example of a PointSeries: [%unnumbered%] ```json @@ -1187,7 +1187,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a PointSeries: [%unnumbered%] ```json @@ -1225,7 +1225,7 @@ Coverage example: - A domain with Point domain type MUST have the axes `"x"` and `"y"` and MAY have the axes `"z"` and `"t"` where all MUST have a single coordinate value only. -Domain example: +Domain example of a Point: [%unnumbered%] ```json @@ -1242,7 +1242,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a Point: [%unnumbered%] ```json @@ -1279,7 +1279,7 @@ Coverage example: - A domain with MultiPointSeries domain type MUST have the axes `"composite"` and `"t"`. - The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"x","y","z"` or `"x","y"`, in that order. -Domain example: +Domain example of a MultiPointSeries: [%unnumbered%] ```json @@ -1301,7 +1301,7 @@ Domain example: } ``` -Domain example without z: +Domain example a MultiPointSeries without z: [%unnumbered%] ```json @@ -1323,7 +1323,7 @@ Domain example without z: } ``` -Coverage example: +Coverage example of a MultiPointSeries: [%unnumbered%] ```json @@ -1367,7 +1367,7 @@ Coverage example: - A domain with MultiPoint domain type MUST have the axis `"composite"` and MAY have the axis `"t"` where `"t"` MUST have a single coordinate value only. - The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"x","y","z"` or `"x","y"`, in that order. -Domain example: +Domain example of a MultiPoint: [%unnumbered%] ```json @@ -1389,7 +1389,7 @@ Domain example: } ``` -Domain example without z and t: +Domain example of a MultiPoint without z and t: [%unnumbered%] ```json @@ -1410,7 +1410,7 @@ Domain example without z and t: } ``` -Coverage example: +Coverage example of a MultiPoint: [%unnumbered%] ```json @@ -1453,7 +1453,7 @@ Coverage example: - The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"t","x","y","z"` or `"t","x","y"`, in that order. - The value ordering of the axis `"composite"` MUST follow the ordering of its `"t"` coordinate as defined in the corresponding reference system. -Domain example: +Domain example of a Trajectory: [%unnumbered%] ```json @@ -1474,7 +1474,7 @@ Domain example: } ``` -Domain example without z: +Domain example of a Trajectory without z: [%unnumbered%] ```json @@ -1495,7 +1495,7 @@ Domain example without z: } ``` -Domain example with z defined as constant value: +Domain example of a Trajectory with z defined as constant value: [%unnumbered%] ```json @@ -1517,7 +1517,7 @@ Domain example with z defined as constant value: } ``` -Coverage example: +Coverage example of a Trajectory: [%unnumbered%] ```json @@ -1561,7 +1561,7 @@ Coverage example: - The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"t","x","y"`, in that order. - The value ordering of the axis `"composite"` MUST follow the ordering of its `"t"` coordinate as defined in the corresponding reference system. -Domain example: +Domain example of a Section: [%unnumbered%] ```json @@ -1583,7 +1583,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a Section: [%unnumbered%] ```json @@ -1627,7 +1627,6 @@ Coverage example: Polygons in this domain type are defined equivalent to GeoJSON, except that they can only contain `[x,y]` positions (and not `z` or additional coordinates): - A LinearRing is an array of 4 or more `[x,y]` arrays where each of `x` and `y` is a coordinate value. The first and last `[x,y]` elements are identical. - A Polygon is an array of LinearRing arrays. For Polygons with multiple rings, the first MUST be the exterior ring and any others MUST be interior rings or holes. - - A domain with Polygon domain type MUST have the axis `"composite"` which has a single Polygon value. - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A Polygon domain MAY have the axes `"z"` and `"t"` which both MUST have a single coordinate value only. @@ -1901,30 +1900,9 @@ Domain example of a MultiPolygon where one polygon has a hole: "dataType": "polygon", "coordinates": ["x", "y"], "values": [ - [ - [ - [40, 40], - [20, 45], - [45, 30], - [40, 40] - ] - ], - [ - [ - [20, 35], - [10, 30], - [10, 10], - [30, 5], - [45, 20], - [20, 35] - ], - [ - [30, 20], - [20, 15], - [20, 25], - [30, 20] - ] - ] + [ [[40, 40], [20, 45],[45, 30], [40, 40]] ], + [ [[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]], + [[30, 20],[20, 15],[20, 25],[30, 20]] ] ] }, "z": { @@ -1964,9 +1942,9 @@ Coverage example of a MultiPolygon where one of the Polygons has a hole. "dataType": "polygon", "coordinates": ["x", "y"], "values": [ - [[[40, 40],[20, 45],[45, 30],[40, 40]]], - [[[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]], - [[30, 20],[20, 15],[20, 25],[30, 20]] + [ [[40, 40],[20, 45],[45, 30],[40, 40]] ], + [ [[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]], + [[30, 20],[20, 15],[20, 25],[30, 20]] ] ] }, "z": { @@ -2000,7 +1978,7 @@ Coverage example of a MultiPolygon where one of the Polygons has a hole. - The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order. - A MultiPolygon domain MAY have the axis `"z"` which MUST have a single coordinate value only. -Domain example: +Domain example of a MultiPolygonSeries: [%unnumbered%] ```json @@ -2012,8 +1990,8 @@ Domain example: "dataType": "polygon", "coordinates": ["x","y"], "values": [ - [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] ], - [ [ [200.0, 10.0], [201.0, 10.0], [201.0, 11.0], [200.0, 11.0], [200.0, 10.0] ] ] + [ [[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]] ], + [ [[200.0, 10.0], [201.0, 10.0], [201.0, 11.0], [200.0, 11.0], [200.0, 10.0]] ] ] }, "z": { "values": [2] }, @@ -2023,7 +2001,7 @@ Domain example: } ``` -Coverage example: +Coverage example of a MultiPolygonSeries: [%unnumbered%] ```json From 160a538b5fc5fa6b175fd515639028c6ee306e06 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 15:00:25 +0100 Subject: [PATCH 08/10] Simplify JSON example in clause specification Corrected multipoint domain example. --- standard/clause_specification_text.adoc | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 430d98873..19626c0de 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1891,7 +1891,6 @@ Domain example of a MultiPolygon where one polygon has a hole: [%unnumbered%] ```json { - "type": "Coverage", "domain": { "type": "Domain", "domainType": "MultiPolygon", @@ -1913,18 +1912,6 @@ Domain example of a MultiPolygon where one polygon has a hole: } }, "referencing": [...] - }, - "parameters": { - }, - "ranges": { - "temperature": { - "type": "NdArray", - "dataType": "float", - "axisNames": ["composite"], - "shape": [2], - "values": [23.1, 24.7] - } - } } ``` From 7cf9d517b1b740420eb6f47c851619ed74c67323 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 15:16:29 +0100 Subject: [PATCH 09/10] Fix formatting of polygon values in clause specification missed some commas at end of lines --- standard/clause_specification_text.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 19626c0de..3a99aa90d 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1700,8 +1700,8 @@ Domain example of a Polygon with two holes, one square, the other triangular: "dataType": "polygon", "coordinates": ["x","y"], "values": [ - [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] - [ [100.3, 0.2], [100.3, 0.4], [100.5, 0.4], [100.5, 0.2], [100.3, 0.2] ] + [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ], + [ [100.3, 0.2], [100.3, 0.4], [100.5, 0.4], [100.5, 0.2], [100.3, 0.2] ], [ [100.7, 0.6], [100.8, 0.8], [100.9, 0.6], [100.7, 0.6] ] ] ] }, @@ -1726,8 +1726,8 @@ Coverage example of a Polygon with two holes, one square, the other triangular: "dataType": "polygon", "coordinates": ["x","y"], "values": [ - [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] - [ [100.3, 0.2], [100.3, 0.4], [100.5, 0.4], [100.5, 0.2], [100.3, 0.2] ] + [ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ], + [ [100.3, 0.2], [100.3, 0.4], [100.5, 0.4], [100.5, 0.2], [100.3, 0.2] ], [ [100.7, 0.6], [100.8, 0.8], [100.9, 0.6], [100.7, 0.6] ] ] ] }, From 7d84a0b3f4559c6289985e98e5394c208811ec9c Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 6 May 2026 16:17:59 +0100 Subject: [PATCH 10/10] Fix formatting of date values in clause specification Typos --- standard/clause_specification_text.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/standard/clause_specification_text.adoc b/standard/clause_specification_text.adoc index 3a99aa90d..fac6d873c 100644 --- a/standard/clause_specification_text.adoc +++ b/standard/clause_specification_text.adoc @@ -1773,7 +1773,7 @@ Domain example of a PolygonSeries: ] }, "z": { "values": [2] }, - "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z","2008-01-01T06:00:00Z] } + "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z","2008-01-01T06:00:00Z"] } }, "referencing": [...] } @@ -1797,7 +1797,7 @@ Coverage example of a PolygonSeries: ] }, "z": { "values": [2] }, - "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z","2008-01-01T05:00:00Z] } + "t": { "values": ["2008-01-01T04:00:00Z","2008-01-01T05:00:00Z","2008-01-01T05:00:00Z"] } }, "referencing": [...] },