BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.osgeo.org//foss4g-europe-2026//speaker//PSWYNG
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20001029T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-foss4g-europe-2026-JFCDW9@talks.osgeo.org
DTSTART;TZID=EET:20260629T120000
DTEND;TZID=EET:20260629T123000
DESCRIPTION:Building analysis-ready Earth observation products starts well 
 before any algorithm runs. Source data need to be accessible\, complete\, 
 up to date. That sounds obvious\, but doing it reliably across multiple sa
 tellite missions while backfilling years of historical archives is not an 
 easy task.\n\nThis talk is about how we built that foundation. The startin
 g point is a simple Argo CronWorkflow that queries a STAC API and download
 s one day of data to S3. Nothing impressive\, but Argo already gives you t
 hings a cron job doesn't: built-in retries\, a web UI showing exactly whic
 h step failed\, and the full log. Your Python script doesn't change\, you'
 re just not the (only) one watching it anymore.\n\nThis talk follows what 
 happened when we scaled this up across various satellite products. Each pr
 oblem we ran into pushed us to add something: fan-out parallelism when seq
 uential backfills were taking days\, STAC as a logbook of what had already
  been ingested and what is missing\, and eventually an observability layer
  when we needed to understand periods of higher error rate.  \n\nThe combi
 nation of autonomous backfill and automated monitoring creates a  system t
 hat self-corrects at two levels: individual failed items are retried via S
 TAC gap detection\, while systemic issues surface in daily reports for hum
 an intervention.                                                          
                             \nAll the tools are open source: Argo Workflow
 s\, STAC API\, Python\, Kubernetes\, CI pipelines Attendees will leave wit
 h a concrete understanding of what Argo Workflows gives you at each stage 
 of complexity\, from replacing a cron job to running a system you can trus
 t "unsupervised".
DTSTAMP:20260605T022355Z
LOCATION:A13
SUMMARY:From Cron Job to Self-Healing Pipeline\, using Argo and STAC for EO
  Data Ingestion. - Loïc Houpert
URL:https://talks.osgeo.org/foss4g-europe-2026/talk/JFCDW9/
END:VEVENT
END:VCALENDAR