BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-2022//talk//GZACL9
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-GZACL9@talks.staging.osgeo.org
DTSTART;TZID=CET:20220825T174500
DTEND;TZID=CET:20220825T181500
DESCRIPTION:The European Flood Awareness System and the Global Flood Awaren
 ess System (EFAS and GloFAS)\, are the two Early Warning Service for flood
 s part of the Copernicus Emergency Management Service (CEMS)\, operated by
  the EU Joint Research Centre (JRC). EFAS and GloFAS aims to complement na
 tional and regional service by providing medium-range flood forecasts and 
 hydrological outlooks for large\, transboundary rivers. Data and products 
 are accessible to eligible users through the Climate Data Store and dedica
 ted web interfaces. ECMWF\, having the role of the computational centre wi
 thin CEMS\, is responsible for running the forecasts and the post-processi
 ng\, on top of co-developing and hosting the EFAS and GloFAS information s
 ystems.\n\nThese two information systems consist on back-end/front-end web
  services based on OGC standards and open-source software. As it is often 
 the case\, a web-based mapviewer allows to display different layers\, prod
 uced by a WMS back-end. These layers are the graphical representation of t
 he output of the hydrological models and meteorological observations\, lik
 e flood probability\, soil moisture\, return period\, observed precipitati
 on etc. For most layers a new forecast is produced every 12 hours for EFAS
  and every 24 hours for GloFAS.\n\nUnlike many similar services\, however\
 , the aim of EFAS and GloFAS is not only to offer the latest forecasts or 
 the latest observations but also to browse through data from previous days
 \, so that older forecasts can be compared with actual observed events. Th
 is inherently means supporting the time dimension within the WMS standard\
 , and managing large quantity of data that accumulates every day. In the c
 ase of EFAS\, for example\, an additional 1.5 Gb of data is produced twice
  a day.\n\nIt also means handling the inevitable changes in data formats a
 nd structures that arise as the service grows and new features are added\,
  without breaking backward compatibility. New layers are added\, old layer
 s are removed\, changes in the geographical domain or the projection for a
  certain layer must be supported from a certain date onward\, etc. Not to 
 mention increasing the number of forecast cycles from one per day to two o
 r more.\n\nTo make matters worse\, data access must be restricted on both 
 front-end and back-end based on a matrix of user privileges\, requested pr
 oduct and requested date. For example some layers are offered to all users
  with no time restrictions\, while others are restricted to some users for
  the latest 30 days\, and freely accessible to all users for dates older t
 han 30 days ago.\n\nIn this talk we describe the challenges of developing 
 and operating an authentication-aware web service heavily based on large g
 eospatial datasets with a strong diachronic component.
DTSTAMP:20260403T220249Z
LOCATION:Auditorium
SUMMARY:10 years of open-source software in emergency management: the case 
 of the European Flood Awareness Service - Dimitar Tasev\, Paolo Battino
URL:https://talks.staging.osgeo.org/foss4g-2022/talk/GZACL9/
END:VEVENT
END:VCALENDAR