Giters

opengeospatial / ogcapi-processes

Home Page:https://ogcapi.ogc.org/processes

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

OGC API - Processes SWG participation in Code Sprint

gfenoy opened this issue · comments

commented

I plan to attend the OGC-ASF-OSGeo code sprint on-site and work on the ZOO-Project, which is an OSGeo project.

I am willing to work on the OGC API - Processes - Part 3: Workflow & Chaining draft specification, specifically reviewing the nested-processes and remote-core-processes Requirements Classes.

My main tasks will be testing the workflow & chaining support available in the ZOO-Project, writing documentation, and setting up a demonstration server instance, including ready-to-use workflow examples.

I also plan to review how to integrate Apache Airflow to deploy processes using the Part 2 draft specification.

commented

Anyone willing to work on the OGC API - Processes during the coming OGC-ASF-OSGeo code sprint is invited to update this issue with the description of the work to be handled.

commented

I'm also interested to work on Part 3 Workflows (same requirements). If some references to remote servers/processes can be shared to define a workflow that is expected to work, that would be great.

commented

Hi @fmigneault , @gfenoy . I also plan to be there in-person and though I will probably be working on a few different things, I would be very happy to do some Processes-3 breakout and work on getting more TIEs going.

To clarify those 2 req. classes specifically:

  • nested-processes: This is being able to use a "process" object as an input to another process
  • remote-core-processes: This is the ability of a server to execute processes using OGC API - Processes - Part 1: Core from a remote OGC API - Processes implementation. The executing server may require such remote servers to be explicilty authorized / federated previously.