Difference between revisions of "OGC API Hackathon June 2019"

From OSGeo
Jump to: navigation, search
Line 28: Line 28:
 
** meetings on CAT 4.0
 
** meetings on CAT 4.0
 
** CAT 4.0 SWG will be created at OGC TC next week (Leuven)
 
** CAT 4.0 SWG will be created at OGC TC next week (Leuven)
** pycsw 3 will be the LTR for CSW2/3
+
** pycsw 3 will be the LTR for CSW 2/3
 
** pycsw 4 will align with CAT 4.0
 
** pycsw 4 will align with CAT 4.0
 
** discussions / testing on whether pycsw 4 is built with pygeoapi underneath with addition of full search conformance class
 
** discussions / testing on whether pycsw 4 is built with pygeoapi underneath with addition of full search conformance class

Revision as of 05:14, 23 June 2019

Purpose

Document/track/coordinate FOSS4G project participation at the OGC API Hackathon (20-21 June 2019) in London.

Event Details

All information, logistics for participants is coordinated by OGC at https://www.opengeospatial.org/projects/initiatives/oapihackathon19

Participants

No Name Country Email Organization Projects Local or Remote
1 Tom Kralidis Canada tomkralidis at gmail.com Meteorological Service of Canada pygeoapi (WFS 3 server, WPS 3 server, WCS, etc.), pycsw (CSW 4 server), OWSLib (OGC API client) local
2 Fabian Schindler & Stephan Meißl Austria stephan.meissl at eox.at EOX IT Services MapServer, EOxServer Local
3 Angelos Tzotsos Greece tzotsos at osgeo.org OSGeo pygeoapi (WFS 3 server, WPS 3 server, WCS, etc.), pycsw (CSW 4 server), OWSLib (OGC API client) TBD
4 Francesco Bartoli Italy xbartolone@gmail.com OSGeo GeoNode-api (OGC API - Processing for now) Local
5 Gérald Fenoy France gerald.fenoy@geolabs.fr GeoLabs ZOO-Project (kind of "OGC API - Processing") local

Updates

  • pycsw
    • meetings on CAT 4.0
    • CAT 4.0 SWG will be created at OGC TC next week (Leuven)
    • pycsw 3 will be the LTR for CSW 2/3
    • pycsw 4 will align with CAT 4.0
    • discussions / testing on whether pycsw 4 is built with pygeoapi underneath with addition of full search conformance class
  • pygeoapi
    • continued implementation of WPS REST binding (jobs, results)
    • implementation of process manager to support asynchronous processing and job storage