Skip to content

pvretano/developer-track

 
 

Repository files navigation

Developer Track at OGC Member Meetings

This Github repository is for Developer Track sessions at OGC Member Meetings.

The Discussions are at https://github.com/opengeospatial/developer-track/discussions

#OGCAPI

About the Developer Track sessions

The goal of the Developer Track sessions is to provide developers with exposure to the draft OGC standards, as well as to share productivity advice about implementing the standards.

About the next Developer Track session

When: Wednesday 24 March from 09:00 EDT to 19:45 EDT

Register at https://portal.ogc.org/meet

The focus of the next Developer Track session will be on OGC APIs for Processes, Records, Tiles and Environmental Data Retrieval. Each practical work block will include a training, followed by prototype development.

Participants (including any member of the audience) will be invited to present a demonstration of their prototype during the Demonstrations session. All participants will be able to vote for their favourite demonstration.

Agenda

Times in EDT (New York time)

  • 09:00 - 09:05 Welcome Remarks - Gobe Hobona (OGC)
  • 09:05 - 09:10 Participant Introductions - All
  • 09:10 - 09:20 Program for the day and Ways of Working - Gobe Hobona (OGC)
  • 09:20 - 09:40 Status of OGC API – Tiles – Joan Maso (UAB CREAF)
  • 09:40 - 10:00 Status of OGC API – Processes - Benjamin Pross (52 North)
  • 10:00 - 10:20 Status of OGC API – Records - Panagiotis ‘Peter’ Vretanos (CubeWerx)
  • 10:20 - 10:40 Overview of the OGC API – Environmental Data Retrieval candidate standard - Chris Little (Met Office)
  • 10:40 - 11:15 Break
  • 11:15 - 13:15 Practical work: Block 1
    • Retrieving vector tiles from OGC API - Tiles implementations using pygeoapi - Francesco Bartoli (OSGeo) - 40 minutes (More info)
    • Publishing data through implementations of the OGC API – Environmental Data Retrieval candidate standard - Mark Burgoyne (Met Office), Shane Mill (NWS), Igor Andruska (IBL) - 40 minutes (More info)
    • Development work - 40 minutes
  • 13:15 - 15:15 Practical work: Block 2
    • Publishing your Python code as OGC API - Processes using pygeoapi - Tom Kralidis (MSC) - 40 minutes (More info)
    • Development work - 80 minutes
  • 15:15 - 17:15 Practical work: Block 3
    • Publishing your geospatial metadata with pygeoapi - Tom Kralidis (MSC), Paul van Genuchten (GeoCat BV) - 40 minutes (More info)
    • Development work - 80 minutes
  • 17:15 - 18:15 Break
  • 18:15 - 19:00 Demonstrations
  • 19:00 - 19:30 Discussion
  • 19:30 - 19:45 Wrap up and Close

Quick Links