Provide OGC conformance definitions for "search/filter" query parameters
Opened this issue · 0 comments
Description
All query parameters used on /processes
and /jobs
need a way to indicate that they are supported on the server:
(see table https://docs.ogc.org/DRAFTS/20-004.html#clause-record-core-query-parameters)
-
q
- #644 -
filter
- #640 -
sort
-
datetime
- #236 -
limit
-
⚠️ type
- #642 (supported, but conflicting definitions) -
⚠️ ids
- Weaver definesprocess
with the same capability prop=value
todo
-
indicate the
/processes
and/jobs
endpoints as searchable/queryable/filetrable using the `links in the landing page:See opengeospatial/ogcapi-records#300 (comment)
You can indicate which endpoints are instumented for catalog-like searching be including one or more links (relation: http://www.opengis.net/def/rel/ogc/1.0/ogc-catalog-local) in the landing page of the server.
-
add the various conformance/requirements definitions from https://docs.ogc.org/DRAFTS/20-004.html as applicable to supported parameters
extras Weaver supports
-
page
not applicable (?)
What to do about those?
- ❌
bbox
- ❌
externalIds
References
-
OGC API - Records approach:
- https://docs.ogc.org/DRAFTS/20-004.html#clause-record-core-query-parameters
8.4. Requirements Class "Record Core Query Parameters" (Building Block)
- https://docs.ogc.org/DRAFTS/20-004.html#clause-filtering
8.7. Requirements Class "Filtering" (Building Block)
- https://docs.ogc.org/DRAFTS/20-004.html#clause-autodiscovery
8.8. Requirements Class "Autodiscovery" (Building Block)
- https://docs.ogc.org/DRAFTS/20-004.html#clause-searchable-catalog
9.3. Requirements Class "Searchable Catalog" (Deployment)
- https://docs.ogc.org/DRAFTS/20-004.html#clause-local-resources-catalog
9.4. Requirements Class "Local Resources Catalog" (Deployment)
- opengeospatial/ogcapi-records#300 (comment)
- https://docs.ogc.org/DRAFTS/20-004.html#clause-record-core-query-parameters
-
OGC API - Common approach:
-
OGC API - Processes approach (TBD):
-
Other related issues: