BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.osgeo.org//foss4g-europe-2024//speaker//H8LVLX
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1;UNTIL=20001231T220000Z
TZNAME:EET
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:STANDARD
BEGIN:STANDARD
DTSTART:20021027T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20020331T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-foss4g-europe-2024-EQSNSK@talks.osgeo.org
DTSTART;TZID=EET:20240703T110000
DTEND;TZID=EET:20240703T113000
DESCRIPTION:pygeoapi is an OGC API Reference Implementation. Implemented in
  Python\, pygeoapi supports numerous OGC APIs via a core agnostic API\, di
 fferent web frameworks (Flask\, Starlette\, Django) and a fully integrated
  OpenAPI capability. Lightweight\, easy to deploy and cloud-ready\, pygeoa
 pi's architecture facilitates publishing datasets and processes from multi
 ple sources. The project also provides an extensible plugin framework\, en
 abling developers to implement custom data adapters\, filters and processe
 s to meet their specific requirements and workflows. pygeoapi also support
 s the STAC specification in support of static data publishing.\n\npygeoapi
  has a significant install base around the world\, with numerous projects 
 in academia\, government and industry deployments. The project is also an 
 OGC API Reference Implementation\, lowering the barrier to publishing geos
 patial data for all users.\n\nThis presentation will provide an update on 
 the current status\, latest developments in the project\, including new co
 re features and plugins. In addition\, the presentation will highlight key
  projects using pygeoapi for geospatial data discovery\, access and visual
 ization.
DTSTAMP:20261014T163655Z
LOCATION:GEOCAT (301)
SUMMARY:pygeoapi mid-year update - Tom Kralidis\, Paul van Genuchten\, Ange
 los Tzotsos\, Just van den Broecke\, Joana Simoes
URL:https://talks.osgeo.org/foss4g-europe-2024/talk/EQSNSK/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-foss4g-europe-2024-3LPRP3@talks.osgeo.org
DTSTART;TZID=EET:20240703T113000
DTEND;TZID=EET:20240703T120000
DESCRIPTION:Metadata\, YAML files and pipelines? When I try to convince my 
 colleagues that the approach mentioned in this presentation is fun\, they 
 look at me alienated.\n\nThis presentation will highlight the usage of pyg
 eometa\, mdme and DevOps workflow in two projects from different domains o
 f interest.\n\nLand-Soil-Crop data\n================\n\nISRIC is endorsing
  the pygeometa MCF format\, a YAML-based representation originally develop
 ed as a subset of ISO 19115 metadata\, advertised by the pygeometa communi
 ty as 'Metadata Creation for the Rest of Us'. YAML reads much better then 
 XML\, and is optimal for content versioning in Git. But YAML comes with it
 s peculiarities\, such as strict indenting and reserved characters.\n\n'Av
 erage users should not look at code\, instead use shiny (web) interfaces' 
 is a quote often used\, but we're not used to reverse the quote: "As a Dev
 Ops engineer I hate shiny interfaces. I want to look at code\, see the his
 tory of that code\, who changed what\, when\, and how can I fix it".\nThis
  is where the fun part of pygeometa MCF comes in. CI/CD pipelines which ru
 n on content changes validate the YAML format and report errors to the sub
 mitters.\n\nShould we then fully neglect the basic user? Of course not! So
  we crafted web based forms that generate mcf (osgeo.github.io/mdme) and h
 ave import options for Excel sheets (every column is a metadata field). Co
 nsider that many data scientists (fortunately) are used to placing a READM
 E.md in any project folder. We just ask them to structure the content usin
 g YAML. We added an inheritance mechanism\, so common properties (contact 
 details\, usage constraints) are inserted only once and inherited by lower
  levels in the folder hierarchy. And embedded metadata is extracted from d
 ata files (bounds\, projection\, format) or online sources.\n\nAll this me
 tadata is crawled to a central search index (pycsw/pygeoapi/geonetwork). T
 o increase the participatory experience we added 'Edit me on GIT' links to
  each of the records\, which brings users back to the original mcf file to
  suggest changes.\n\nWeather/climate/water metadata\n=====================
 =========\n\nThe WMO Information System (WIS2) is the next generation data
  exchange infrastructure for real-time and archive weather/climate/water d
 ata.  Discovery metadata is a key component for cataloguing and discovery.
   An event driven architecture\, metadata files are managed on GitHub\, wh
 ich on change\, trigger CI/CD workflow to generate compliant WMO discovery
  metadata\, validation and publish to an MQTT broker.
DTSTAMP:20261014T163655Z
LOCATION:GEOCAT (301)
SUMMARY:A fun way to do spatial cataloguing and publishing using pygeometa 
 and mdme - Tom Kralidis\, Paul van Genuchten
URL:https://talks.osgeo.org/foss4g-europe-2024/talk/3LPRP3/
END:VEVENT
END:VCALENDAR