BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-2022//talk//GRNXGG
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-foss4g-2022-GRNXGG@talks.staging.osgeo.org
DTSTART;TZID=CET:20220825T120000
DTEND;TZID=CET:20220825T123000
DESCRIPTION:Update on the status of OGC API standards and draft specificati
 ons enabling client-driven execution of processing workflows\, supporting 
 on-demand and ad-hoc selection of data and algorithms. Overview of the cap
 abilities enabled by OGC API - Tiles\, OGC API - Coverages and Processes 
 – Part 3: Workflows and Chaining. Demonstration of both a server and a c
 lient implementing these specifications.\n\nThe Workflows and Chaining dra
 ft extension specification to OGC API – Processes enables ad-hoc executi
 on of workflows integrating processes and data available from one or more 
 OGC API instances. The specification allows triggering processing as a res
 ult of requesting results for a specific area and resolution of interest\,
  which provides a simple mechanism to chain geospatial data inputs and out
 puts. \n\nBy referring to a collection of geospatial data irrespective of 
 a particular area\, resolution or date/time of interest\, workflows can be
  defined in a generic\, re-usable manner\, and processing can be performed
  on-demand rather than (or in addition to) as a batch execution. Such on-d
 emand processing has the advantage of optimizing the use of computing reso
 urces and speeding up the availability of the latest available data\, such
  as for continuously captured Earth Observation satellite imagery.\n\nThe 
 initial version of the Workflows and Chaining specification was a result o
 f a GeoConnections 2020-2021 project funded by Natural Resources Canada\, 
 which also supported the development of a unified OGC API driver in GDAL a
 llowing to directly visualize the results of such workflows in QGIS.\n\nOG
 C API – Tiles is the specification succeeding to WMTS in the OGC API fam
 ily\, leveraging the concept of 2D Tile Matrix Sets. In addition to provid
 ing tiles of maps or imagery\, Tiles can also be used to distribute raw da
 ta tiles\, including coverage and vector tiles. Using tiles to deliver res
 ults and trigger execution of processing workflows can facilitate caching 
 while allowing to efficiently select an area and resolution of interest.\n
 \nOGC API – Coverages is the specification suceeding to WCS in the OGC A
 PI family\, and provides a simple mechanism to request an optionally down-
 sampled subset of a coverage. Specific fields (e.g. imagery band) can be s
 elected as needed. The Coverages specification can also be used to request
  results while triggering execution of a workflow.
DTSTAMP:20260412T160622Z
LOCATION:Room 4
SUMMARY:Update on Modular OGC API Workflows specifications - Jerome St-Loui
 s
URL:https://talks.staging.osgeo.org/foss4g-2022/talk/GRNXGG/
END:VEVENT
END:VCALENDAR