Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OGC-API Processes - Part 3: Collection Outputs #683

Open
4 tasks
fmigneault opened this issue Jul 15, 2024 · 1 comment
Open
4 tasks

Support OGC-API Processes - Part 3: Collection Outputs #683

fmigneault opened this issue Jul 15, 2024 · 1 comment
Assignees
Labels
feature/collection Issues related to Collection inputs/outputs and their resolution. process/OAP-Part3: Workflows OGC API - Processes - Part 3: Workflows/Chaining triage/feature New requested feature.

Comments

@fmigneault
Copy link
Collaborator

fmigneault commented Jul 15, 2024

Description

Given a process execution, normally (Core specification), the resulting outputs are literal data directly provided, or a URI to a file where it can be retrieved.

This feature adds the response query parameter provided in the execution request to obtain the result through a OGC API /collections/... capable endpoint.

The resulting 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.


⚠️ Pre-requirements:

  • The process must have only 1 output (from its outputs definition), or a single output must be explicitly selected when multiple are available, using the outputs field in the execution request.
    Selection of the outputs depends on Filter out non-requested outputs #380 to be implemented.
  • The process should ideally verify if a Collection Output is a valid type of representation for the unique/selected output.
    This is maybe not so trivial depending on cases. For example, if the output is:
    • Feature Collection (GeoJSON): this makes sense
    • literal data: this probably doesn't make sense
    • Bounding Box: could be a single item GeoJSON Collection (requires conversion with shapely)
    • GeoTiff: could make sense, but must it be represented as STAC Single-Item Collection? Should certain STAC extension be inferred... (relates to Support for STAC metadata #103)
    • Other complex data? Depends on what it is...
  • The produced output must be POST'd to a (remote) catalog to fulfil the requirement that the linked collection data must be accessible/filterable. It cannot be a simple static document. Therefore, this output catalog must be configurable (similar to how S3 output bucket can be configured).

Adds support of:

  • http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-output
  • response=collection, return HTTP 303 See Other, Location: <collection-uri>
  • response=landingPage, idem as collection, but the link is the root of the server with /collections listed within its links
  • http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/output-fields-modifiers

References

@fmigneault fmigneault added the triage/feature New requested feature. label Jul 15, 2024
@fmigneault fmigneault self-assigned this Jul 15, 2024
@github-actions github-actions bot added the process/workflow Related to a Workflow process. label Jul 15, 2024
@fmigneault fmigneault added process/OAP-Part3: Workflows OGC API - Processes - Part 3: Workflows/Chaining feature/collection Issues related to Collection inputs/outputs and their resolution. and removed process/workflow Related to a Workflow process. labels Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/collection Issues related to Collection inputs/outputs and their resolution. process/OAP-Part3: Workflows OGC API - Processes - Part 3: Workflows/Chaining triage/feature New requested feature.
Projects
None yet
Development

No branches or pull requests

1 participant