Provide OGC conformance definitions for "search/filter" query parameters #641
Labels
project/OGC
Related to OGC testbeds or relavant projects.
triage/conformance
Issue related to fixing/ensuring compliance to specifications.
triage/feature
New requested feature.
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
/query
- support text search withq
andquery
parameters #644filter
- Considerfilter
operations withfilter-lang=cql-text|cql-json
using CQL2 #640sort
datetime
- [Feature] Support search withdatetime
parameter #236limit
type
- Support a query parameter for matching the processtype
#642 (supported, but conflicting definitions)ids
- Weaver definesprocess
with the same capabilityprop=value
order
-order=ASC|DESC
to be correctly combined with the definedsort
field #643version
- search byversion="x.y.z"
#627license
- Search for a givenlicense
type applied in thelinks
for a process #626category
- supportcategory=application|workflow
process filtering #645todo
indicate the
/processes
and/jobs
endpoints as searchable/queryable/filetrable using the `links in the landing page:See Local Resource Catalogs and req. class organization opengeospatial/ogcapi-records#300 (comment)
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:
OGC API - Common approach:
OGC API - Processes approach (TBD):
Other related issues:
The text was updated successfully, but these errors were encountered: