BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-2022//talk//ELXNEB
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-ELXNEB@talks.staging.osgeo.org
DTSTART;TZID=CET:20220825T144500
DTEND;TZID=CET:20220825T151500
DESCRIPTION:The open standards\, open source geospatial and open science co
 mmunities still have a very limited answer to the question how researchers
  active in applied domains such as agriculture\, ecology\, hydrology\, oce
 anography or land use planning can benefit from the large amounts of open 
 Earth Observation (EO) data currently available. Solutions are very much t
 ied to platforms operated and controlled by big tech (Earth Engine\, Plane
 tary Computer)\, particular programming languages\, software stacks and/or
  file formats (xarray\, Pangeo\, ODC\, GeoPySpark/GeoTrellis). The openEO 
 initiative provides an API and a set of processes that separate the “wha
 t” from the “how”: users specify what they want to compute\, and bac
 k-end processing engines decide how to do this. The openEO API is OpenAPI 
 compliant\, and has client interfaces for Python\, R\, and JavaScript\, an
 d in addition graphical user interfaces running in the browser or in QGIS.
  The underlying data model is that of a data cube view: image collections 
 or vector data may be stored as they are\, but are analysed as if they wer
 e laid out as a raster or vector data cube\, e.g. for raster with dimensio
 ns x\, y\, band and time\, or for vector with dimensions geometry\, band a
 nd time. Because openEO assumes that imagery is described as STAC collecti
 ons and the implementation is composed of open source components\, it is r
 elatively easy to set it up and compute on infrastructure where imagery is
  available through a STAC interface. Having a single interface to carry ou
 t computations on back-ends with different architecture makes it possible 
 to compare results across implementations\, to verify that EO processing i
 s reproducible. So far\, over 100 processes have been defined\, and user-d
 efined functions written in Python or R extend this ad infinitum. openEO w
 as initially developed during a H2020 project (2017-2020). It is currently
  continued with ESA funding that has resulted in the “openEO Platform”
 \, an implementation run by VITO and EODC where the general public can use
  the openEO interface for large scale computations. Several upcoming Horiz
 on Europe projects will further support continued development of the API a
 nd openEO software ecosystem of clients and back-ends. Since the initiativ
 e is designed to be an open science\, all users and developers are invited
  to engage. We will present the current state of the openEO ecosystem and 
 give an outlook to forthcoming developments.
DTSTAMP:20260404T032754Z
LOCATION:Auditorium
SUMMARY:openEO: Open Science for Earth Observation Research - Edzer Pebesma
 \, Matthias Mohr
URL:https://talks.staging.osgeo.org/foss4g-2022/talk/ELXNEB/
END:VEVENT
END:VCALENDAR