Skip to content

Commit 452d9bb

Browse files
chris-littlechris-little
authored
Update domain examples and descriptions in clause spec
Correct the nesting of brackets
1 parent 39c4caa commit 452d9bb

1 file changed

Lines changed: 30 additions & 52 deletions

File tree

‎standard/clause_specification_text.adoc‎

Lines changed: 30 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1059,7 +1059,7 @@ Requirements for all domain types defined in this OGC Community Standard:
10591059

10601060
- A domain with Grid domain type MUST have the axes `"x"` and `"y"` and MAY have the axes `"z"` and `"t"`.
10611061

1062-
Domain example:
1062+
Domain example of a Grid:
10631063

10641064
[%unnumbered%]
10651065
```json
@@ -1076,7 +1076,7 @@ Domain example:
10761076
}
10771077
```
10781078

1079-
Coverage example:
1079+
Coverage example of a Grid:
10801080

10811081
[%unnumbered%]
10821082
```json
@@ -1114,7 +1114,7 @@ Coverage example:
11141114
- 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.
11151115
- A domain with VerticalProfile domain type MAY have the axis `"t"` which MUST have a single coordinate value only.
11161116

1117-
Domain example:
1117+
Domain example of a VerticalProfile:
11181118

11191119
[%unnumbered%]
11201120
```json
@@ -1131,7 +1131,7 @@ Domain example:
11311131
}
11321132
```
11331133

1134-
Coverage example:
1134+
Coverage example of a VerticalProfile:
11351135

11361136
[%unnumbered%]
11371137
```json
@@ -1170,7 +1170,7 @@ Coverage example:
11701170
- 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.
11711171
- A domain with PointSeries domain type MAY have the axis `"z"` which MUST have a single coordinate value only.
11721172

1173-
Domain example:
1173+
Domain example of a PointSeries:
11741174

11751175
[%unnumbered%]
11761176
```json
@@ -1187,7 +1187,7 @@ Domain example:
11871187
}
11881188
```
11891189

1190-
Coverage example:
1190+
Coverage example of a PointSeries:
11911191

11921192
[%unnumbered%]
11931193
```json
@@ -1225,7 +1225,7 @@ Coverage example:
12251225

12261226
- 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.
12271227

1228-
Domain example:
1228+
Domain example of a Point:
12291229

12301230
[%unnumbered%]
12311231
```json
@@ -1242,7 +1242,7 @@ Domain example:
12421242
}
12431243
```
12441244

1245-
Coverage example:
1245+
Coverage example of a Point:
12461246

12471247
[%unnumbered%]
12481248
```json
@@ -1279,7 +1279,7 @@ Coverage example:
12791279
- A domain with MultiPointSeries domain type MUST have the axes `"composite"` and `"t"`.
12801280
- The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"x","y","z"` or `"x","y"`, in that order.
12811281

1282-
Domain example:
1282+
Domain example of a MultiPointSeries:
12831283

12841284
[%unnumbered%]
12851285
```json
@@ -1301,7 +1301,7 @@ Domain example:
13011301
}
13021302
```
13031303

1304-
Domain example without z:
1304+
Domain example a MultiPointSeries without z:
13051305

13061306
[%unnumbered%]
13071307
```json
@@ -1323,7 +1323,7 @@ Domain example without z:
13231323
}
13241324
```
13251325

1326-
Coverage example:
1326+
Coverage example of a MultiPointSeries:
13271327

13281328
[%unnumbered%]
13291329
```json
@@ -1367,7 +1367,7 @@ Coverage example:
13671367
- 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.
13681368
- The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"x","y","z"` or `"x","y"`, in that order.
13691369

1370-
Domain example:
1370+
Domain example of a MultiPoint:
13711371

13721372
[%unnumbered%]
13731373
```json
@@ -1389,7 +1389,7 @@ Domain example:
13891389
}
13901390
```
13911391

1392-
Domain example without z and t:
1392+
Domain example of a MultiPoint without z and t:
13931393

13941394
[%unnumbered%]
13951395
```json
@@ -1410,7 +1410,7 @@ Domain example without z and t:
14101410
}
14111411
```
14121412

1413-
Coverage example:
1413+
Coverage example of a MultiPoint:
14141414

14151415
[%unnumbered%]
14161416
```json
@@ -1453,7 +1453,7 @@ Coverage example:
14531453
- The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"t","x","y","z"` or `"t","x","y"`, in that order.
14541454
- The value ordering of the axis `"composite"` MUST follow the ordering of its `"t"` coordinate as defined in the corresponding reference system.
14551455

1456-
Domain example:
1456+
Domain example of a Trajectory:
14571457

14581458
[%unnumbered%]
14591459
```json
@@ -1474,7 +1474,7 @@ Domain example:
14741474
}
14751475
```
14761476

1477-
Domain example without z:
1477+
Domain example of a Trajectory without z:
14781478

14791479
[%unnumbered%]
14801480
```json
@@ -1495,7 +1495,7 @@ Domain example without z:
14951495
}
14961496
```
14971497

1498-
Domain example with z defined as constant value:
1498+
Domain example of a Trajectory with z defined as constant value:
14991499

15001500
[%unnumbered%]
15011501
```json
@@ -1517,7 +1517,7 @@ Domain example with z defined as constant value:
15171517
}
15181518
```
15191519

1520-
Coverage example:
1520+
Coverage example of a Trajectory:
15211521

15221522
[%unnumbered%]
15231523
```json
@@ -1561,7 +1561,7 @@ Coverage example:
15611561
- The axis `"composite"` MUST have the data type `"tuple"` and the coordinate identifiers `"t","x","y"`, in that order.
15621562
- The value ordering of the axis `"composite"` MUST follow the ordering of its `"t"` coordinate as defined in the corresponding reference system.
15631563

1564-
Domain example:
1564+
Domain example of a Section:
15651565

15661566
[%unnumbered%]
15671567
```json
@@ -1583,7 +1583,7 @@ Domain example:
15831583
}
15841584
```
15851585

1586-
Coverage example:
1586+
Coverage example of a Section:
15871587

15881588
[%unnumbered%]
15891589
```json
@@ -1627,7 +1627,6 @@ Coverage example:
16271627
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):
16281628
- 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.
16291629
- 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.
1630-
16311630
- A domain with Polygon domain type MUST have the axis `"composite"` which has a single Polygon value.
16321631
- The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order.
16331632
- 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:
19011900
"dataType": "polygon",
19021901
"coordinates": ["x", "y"],
19031902
"values": [
1904-
[
1905-
[
1906-
[40, 40],
1907-
[20, 45],
1908-
[45, 30],
1909-
[40, 40]
1910-
]
1911-
],
1912-
[
1913-
[
1914-
[20, 35],
1915-
[10, 30],
1916-
[10, 10],
1917-
[30, 5],
1918-
[45, 20],
1919-
[20, 35]
1920-
],
1921-
[
1922-
[30, 20],
1923-
[20, 15],
1924-
[20, 25],
1925-
[30, 20]
1926-
]
1927-
]
1903+
[ [[40, 40], [20, 45],[45, 30], [40, 40]] ],
1904+
[ [[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]],
1905+
[[30, 20],[20, 15],[20, 25],[30, 20]] ]
19281906
]
19291907
},
19301908
"z": {
@@ -1964,9 +1942,9 @@ Coverage example of a MultiPolygon where one of the Polygons has a hole.
19641942
"dataType": "polygon",
19651943
"coordinates": ["x", "y"],
19661944
"values": [
1967-
[[[40, 40],[20, 45],[45, 30],[40, 40]]],
1968-
[[[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]],
1969-
[[30, 20],[20, 15],[20, 25],[30, 20]]
1945+
[ [[40, 40],[20, 45],[45, 30],[40, 40]] ],
1946+
[ [[20, 35],[10, 30],[10, 10],[30, 5],[45, 20],[20, 35]],
1947+
[[30, 20],[20, 15],[20, 25],[30, 20]] ]
19701948
]
19711949
},
19721950
"z": {
@@ -2000,7 +1978,7 @@ Coverage example of a MultiPolygon where one of the Polygons has a hole.
20001978
- The axis `"composite"` MUST have the data type `"polygon"` and the coordinate identifiers `"x","y"`, in that order.
20011979
- A MultiPolygon domain MAY have the axis `"z"` which MUST have a single coordinate value only.
20021980

2003-
Domain example:
1981+
Domain example of a MultiPolygonSeries:
20041982

20051983
[%unnumbered%]
20061984
```json
@@ -2012,8 +1990,8 @@ Domain example:
20121990
"dataType": "polygon",
20131991
"coordinates": ["x","y"],
20141992
"values": [
2015-
[ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] ],
2016-
[ [ [200.0, 10.0], [201.0, 10.0], [201.0, 11.0], [200.0, 11.0], [200.0, 10.0] ] ]
1993+
[ [[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]] ],
1994+
[ [[200.0, 10.0], [201.0, 10.0], [201.0, 11.0], [200.0, 11.0], [200.0, 10.0]] ]
20171995
]
20181996
},
20191997
"z": { "values": [2] },
@@ -2023,7 +2001,7 @@ Domain example:
20232001
}
20242002
```
20252003

2026-
Coverage example:
2004+
Coverage example of a MultiPolygonSeries:
20272005

20282006
[%unnumbered%]
20292007
```json

0 commit comments

Comments
 (0)