Skip to content

Commit 972779d

Browse files
authored
Merge pull request #445 from opengeospatial/20230711_final_review
generated radius adoc files and updated crs tests of position and cor…
2 parents 38f21ba + 6034a30 commit 972779d

16 files changed

+242
-8
lines changed

standard/abstract_tests/collections/area/ATS_rc-coords-response.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,6 @@ test-method::
1111
--
1212
. Verify that only resources that have a spatial geometry that intersects the coordinates are returned as part of the result set.
1313
. Verify `coords` values are valid for the specified coordinate reference system
14-
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for WGS 84 longitude/latitude (`http://www.opengis.net/def/crs/OGC/1.3/CRS84` or `http://www.opengis.net/def/crs/OGC/0/CRS84h`).
14+
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for the coordinate reference system defined by the spatial element of the extent section in the collection response.
1515
--
16-
====
16+
====

standard/abstract_tests/collections/corridor/ATS_rc-coords-response.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,6 @@ test-method::
1111
--
1212
. Verify that only resources that have a spatial geometry that intersects the coordinates are returned as part of the result set.
1313
. Verify `coords` values are valid for the specified coordinate reference system
14-
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for WGS 84 longitude/latitude (`http://www.opengis.net/def/crs/OGC/1.3/CRS84` or `http://www.opengis.net/def/crs/OGC/0/CRS84h`).
14+
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for the coordinate reference system defined by the spatial element of the extent section in the collection response.
1515
--
16-
====
16+
====

standard/abstract_tests/collections/position/ATS_rc-coords-response.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,6 @@ test-method::
1111
--
1212
. Verify that only resources that have a spatial geometry that intersects the coordinates are returned as part of the result set.
1313
. Verify `coords` values are valid for the specified coordinate reference system
14-
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for WGS 84 longitude/latitude (`http://www.opengis.net/def/crs/OGC/1.3/CRS84` or `http://www.opengis.net/def/crs/OGC/0/CRS84h`).
14+
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for the coordinate reference system defined by the spatial element of the extent section in the collection response.
1515
--
16-
====
16+
====
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_edr_rc-coords-definition-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/rc-coords-definition-radius
7+
target:: /req/edr/coords-definition
8+
test-purpose:: Validate that the coords query parameters are constructed correctly.
9+
test-method::
10+
+
11+
--
12+
Verify that the `coords` query parameter complies with the following definition (using an OpenAPI Specification 3.0 fragment):
13+
14+
[source,YAML]
15+
----
16+
name: coords
17+
in: query
18+
required: true
19+
schema:
20+
type: string
21+
style: form
22+
explode: false
23+
----
24+
25+
Use a coords value in all requests:
26+
27+
* A valid Well-Known Text (WKT) representation of geometry string
28+
--
29+
====
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_edr_rc-coords-response-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/rc-coords-response-radius
7+
target:: /req/edr/point-coords-response
8+
test-purpose:: Validate that the `coords` query parameters are processed correctly.
9+
test-method::
10+
+
11+
--
12+
. Verify that only resources that have a spatial geometry that intersects the coordinates are returned as part of the result set.
13+
. Verify `coords` values are valid for the specified coordinate reference system
14+
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for the coordinate reference system defined by the spatial element of the extent section in the collection response.
15+
--
16+
====
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_edr_rc-crs-definition-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/REQ_rc-crs-definition-radius
7+
target:: /req/edr/REQ_rc-crs-definition
8+
test-purpose:: Validate that the crs query parameters are constructed correctly.
9+
test-method::
10+
+
11+
--
12+
Verify that the `crs` query parameter complies with the following definition (using an OpenAPI Specification 3.0 fragment):
13+
14+
[source,YAML]
15+
----
16+
name: crs
17+
in: query
18+
required: false
19+
schema:
20+
type: string
21+
style: form
22+
explode: false
23+
----
24+
--
25+
====
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_edr_rc-crs-response-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/REQ_rc-crs-response-radius
7+
target:: /req/edr/REQ_rc-crs-response
8+
test-purpose:: Validate that the crs query parameters are processed correctly.
9+
test-method::
10+
step::: Verify that the geometry of the resources returned are valid for the requested coordinate reference system
11+
step::: Verify that all crs values defined in the collections metadata are supported by the collection
12+
step::: Verify that all crs values not defined in the collections metadata will generate a HTTP `400` error
13+
step::: Validate that the crs parameter complies with the syntax described in <<req_edr_crs-response,/req/edr/REQ_rc-crs-response>>.
14+
====
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_collections_rc-f-definition-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/rc-f-definition-radius
7+
target:: /req/edr/rc-f-definition
8+
test-purpose:: Validate that the `f` query parameter is constructed correctly.
9+
test-method::
10+
+
11+
--
12+
Verify that the `f` query parameter complies with the following definition (using an OpenAPI Specification 3.0 fragment):
13+
14+
[source,YAML]
15+
----
16+
name: f
17+
in: query
18+
required: false
19+
schema:
20+
type: string
21+
style: form
22+
explode: false
23+
----
24+
--
25+
====
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_collections_rc-f-response-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/collections/rc-f-response-radius
7+
target:: /req/edr/REQ_rc-f-response
8+
test-purpose:: Validate that the `f` query parameters are processed correctly.
9+
test-method::
10+
step::: Verify that the response is returned in the requested data format
11+
step::: Verify that all output format values defined in the collections metadata are supported by the collection
12+
step::: Validate that the `f` parameter complies with the syntax described in <<req_edr_f-response,/req/edr/REQ_rc-f-response>>.
13+
====
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_collections_rc-parameter-name-definition-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/collections/REQ_rc-parameter-name-definition-radius
7+
target:: /req/edr/REQ_rc-parameter-name-definition
8+
test-purpose:: Validate that the parameter-name query parameters are constructed correctly.
9+
test-method::
10+
+
11+
--
12+
Verify that the `parameter-name` query parameter complies with the following definition (using an OpenAPI Specification 3.0 fragment):
13+
14+
[source,YAML]
15+
----
16+
name: parameter-name
17+
in: query
18+
required: false
19+
schema:
20+
type: string
21+
style: form
22+
explode: false
23+
----
24+
--
25+
====
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_collections_rc-parameter-name-response-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/rc-parameter-name-response-radius
7+
target:: /req/edr/parameter-name-response
8+
test-purpose:: Validate that the parameter-name query parameters are processed correctly.
9+
test-method::
10+
step::: Verify that only resources for the requested parameters were included in the result set
11+
step::: Validate that the parameter-name parameter complies with the syntax described in <<req_edr_parameters-response,/req/edr/parameter-name-response>>.
12+
====
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_collections_rc-z-definition-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/rc-z-definition-radius
7+
target:: /req/edr/z-definition
8+
test-purpose:: Validate that the vertical level query parameters are constructed correctly.
9+
test-method::
10+
+
11+
--
12+
Verify that the `z` query parameter complies with the following definition (using an OpenAPI Specification 3.0 fragment):
13+
14+
[source,YAML]
15+
----
16+
name: z
17+
in: query
18+
required: false
19+
schema:
20+
type: string
21+
style: form
22+
explode: false
23+
----
24+
--
25+
====
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_collections_rc-z-response-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/edr/rc-z-response-radius
7+
target:: /req/edr/z-response
8+
test-purpose:: Validate that the vertical level query parameters are processed correctly.
9+
test-method::
10+
step::: Verify that only resources that have a vertical geometry that intersects the vertical information in the `z` parameter were included in the result set
11+
step::: Validate that the vertical level parameter complies with the syntax described in <<req_edr_z-response,/req/edr/z-response>>.
12+
====

standard/abstract_tests/collections/trajectory/ATS_rc-coords-response.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,6 @@ test-method::
1111
--
1212
. Verify that only resources that have a spatial geometry that intersects the coordinates are returned as part of the result set.
1313
. Verify `coords` values are valid for the specified coordinate reference system
14-
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for WGS 84 longitude/latitude (`http://www.opengis.net/def/crs/OGC/1.3/CRS84` or `http://www.opengis.net/def/crs/OGC/0/CRS84h`).
14+
. Verify that the coordinate reference system of the geometries is valid for the parameter defined by `crs`. If the `crs` parameter is not defined the geometries shall be valid for the coordinate reference system defined by the spatial element of the extent section in the collection response.
1515
--
16-
====
16+
====
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_core_rc-time-definition-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/core/datetime-definition-radius
7+
target:: /req/core/datetime-definition
8+
test-purpose:: Validate that the datetime query parameters are constructed correctly.
9+
test-method::
10+
+
11+
--
12+
Verify that the `datetime` query parameter complies with the following definition (using an OpenAPI Specification 3.0 fragment):
13+
14+
[source,YAML]
15+
----
16+
name: datetime
17+
in: query
18+
required: false
19+
schema:
20+
type: string
21+
style: form
22+
explode: false
23+
----
24+
--
25+
====
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
//Autogenerated file - DO NOT EDIT
2+
[[ats_core_rc-time-response-radius]]
3+
[abstract_test]
4+
====
5+
[%metadata]
6+
identifier:: /conf/core/datetime-response-radius
7+
target:: /req/core/datetime-response
8+
test-purpose:: Validate that the `datetime` query parameters are processed correctly.
9+
test-method::
10+
step::: Verify that only resources that have a temporal geometry that intersects the temporal information in the `datetime` parameter were included in the result set.
11+
step::: Verify that all resources in the collection that are not associated with a temporal geometry are included in the result set.
12+
step::: Validate that the `datetime` parameter complies with the syntax described in <<req_core_rc-time-response,/req/core/datetime-response>>.
13+
====

0 commit comments

Comments
 (0)