Support OGC-API Processes - Part 3: Collection Inputs

[fmigneault]

Description

Given a process execution, normally (Core specification), these are the allowed inputs formats:

{
  "input-value-literal": 123,
  "input-value": {  
    "value": 123
    "format": "int"
  },
  "input-value-remote": {  
    "href": "https://server.com/file.json",
    "type": "application/geo+json"
  }
}

This feature adds support for Collection Input, as follows:

{
  "some-input": {
    "collection": "https://server.com/collections/collectionId",
    "filter": {"op": "", "args": []},
    "filter-lang": "cql2-json",
    "properties": {  }, 
    "sortBy": "expr1,expr2,expr3"
  }
}

(note: only collection is needed, others are optional, and correspond to additional requirement classes)

The referenced collection must support (at least) one of OGC API data access mechanisms (e.g., OGC API - Tiles, Coverages, DGGS, Features, EDR, Maps) as defined by OGC API - Common - Part 2: Geospatial data.

Adds support of:

• http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-input
• http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/remote-collections
• http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/input-fields-modifiers

References

• https://github.com/opengeospatial/ogcapi-processes/tree/master/extensions/workflows/requirements/collection-input
• https://docs.ogc.org/DRAFTS/21-009.html#section_collection_input
• relates to Support OGC-API Processes - Part 3: Workflows #412
• relates to Consider filter operations with filter-lang=cql-text|cql-json using CQL2 #640

[fmigneault]

Relates to:

• Conflicting strict requirements for Part 3 collections opengeospatial/ogcapi-processes#425
• Clarify input/output field modifiers of Part 3 collections opengeospatial/ogcapi-processes#426