Skip to content

Commit f509d23

Browse files
authored
Merge pull request #137 from opengeospatial/20240806_final_staff_review
20240806 final staff review 2
2 parents 28e2758 + 846c9a1 commit f509d23

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

core/standard/clause_15_map_paramGeneralSubsetting.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This functionality is defined as common building blocks shared with other OGC AP
1212

1313
=== Describing the extent of the additional dimensions
1414

15-
When implementing the General Subsetting requirements class, additional dimensions included in an extent description must use a uniform approach to describe the lower and upper bounds of those dimensions based on the `intervals` property. An example is found in an OGC API collection description response described in OGC API - Common - Part 2 and follows the JSON schema in https://github.com/opengeospatial/ogcapi-maps/blob/master/openapi/schemas/common-geodata/collectionInfo.yaml. This is the same as with the temporal dimension.
15+
When implementing the General Subsetting requirements class, additional dimensions included in an extent description must use a uniform approach to describe the lower and upper bounds of those dimensions based on the `intervals` property. An example is found in an OGC API collection description response described in OGC API - Common - Part 2 and follows the JSON schema in https://schemas.opengis.net/ogcapi/maps/part1/1.0/openapi/schemas/common-geodata/collectionDesc.yaml. This is the same as with the temporal dimension.
1616

1717
include::requirements/general-subsetting/REQ_uniform-additional-dimensions.adoc[]
1818

core/standard/clause_6_overview.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,9 +166,9 @@ whereas requesting raw data values using _OGC API - Tiles_ (e.g. from tiled vect
166166

167167
The Maps API Standard defines how to describe the domain of the maps, including spatiotemporal axes as well as additional dimensions.
168168

169-
With the <<rc_collection-map,_Collection Map_>> requirements class, the https://github.com/opengeospatial/ogcapi-maps/blob/master/openapi/schemas/common-geodata/collectionInfo.yaml[collection description]
169+
With the <<rc_collection-map,_Collection Map_>> requirements class, the https://schemas.opengis.net/ogcapi/maps/part1/1.0/openapi/schemas/common-geodata/collectionDesc.yaml[collection description]
170170
inherited from _OGC API - Common - Part 2_ contains an `extent` property that can describe both the spatial and temporal domain of the data. In addition, the _Unified Additional Dimensions_ common building block,
171-
specified in the <<rc_general-subsetting,_General Subsetting_>> requirements class and used in the https://github.com/opengeospatial/ogcapi-maps/blob/master/openapi/schemas/common-geodata/extent-uad.yaml[example OpenAPI definition],
171+
specified in the <<rc_general-subsetting,_General Subsetting_>> requirements class and used in the https://schemas.opengis.net/ogcapi/maps/part1/1.0/openapi/schemas/common-geodata/extent-uad.yaml[example OpenAPI definition],
172172
requires that additional dimensions be described in a similar way to the temporal dimension.
173173
This allows providing an overall lower and upper bound (the first `interval` element), as well as optional sparse inner intervals where data is found along each dimension (additional `interval` elements).
174174
A `grid` property also supports the description of regular and irregular grids.

0 commit comments

Comments
 (0)