From 9868aac2e4efe5fa9ffca442f04884967239dab8 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 25 Mar 2026 21:48:41 +0000 Subject: [PATCH 1/3] 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 2/3] 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 3/3] 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: