Meeting 2021 03 10

Date/Time

Wednesday 10 March 2021 16h UTC

Location

https://gitter.im/geopython/pygeoapi

Agenda (Draft)

review of previous meeting actions
OGC API - Records implementation
Python 2 support and dev style adoption
Application to the Docker Open Source Program
1.0 roadmap
Events
OSGeoLive application progress

Attendees

Just, Tom, Paul, Angelos

Notes

Review actions

Dev style put forth by @jorgejesus looks good, needs review. Add to wiki or docs -> wiki. Should be findable, if in Wiki refer from doc. > action Tom.
Still in queue for dockerhub
GeoNode update next time

OGC API - Records implementation

Made it to master in last OGC API sprint. Roadmap is csw backend and improve elastic backend, maybe postgres backend (+1) GeoPackage backend with full-text-search extension. This would end up being an official GPKG profile that we would propose in tandem with other catalogue type projects (pycsw, GeoNetwork, etc.) There is a sample metadata loader in https://github.com/geopython/pygeoapi/blob/master/tests/load_tinydb_records.py which uses OWSLib to load ISO XML metadata We’ve also done some work on QGIS MetaSearch which will help move forward OARec in general. OARec has been brewing for quite some time, and I’m glad the standard is starting to harden, which allows us to further implement. I don’t see pygeoapi becoming a full-blown metadata tool, but in the UNIX style of composable tools, it’s a great fit along with pycsw, pygeometa, and so on

Python 2 support and dev style adoption

Dropped python 2 Dev style in wiki adopted

Roadmap

What is missing for 1.0?

OGC EDR API: I’m almost done this work and should have a PR soon with full details. For those not aware of EDR: http://docs.opengeospatial.org/DRAFTS/19-086.html
should we consider OAMaps/OAStyles BEFORE 1.0 ?
we have numerous open PRs and issues and we need to have a sweep/sprint

Or should we do a 0.10 first? Can we do 1.0 with many of the OGC schema's still in draft?

Api.py refacture needed (very monolothic), could be done after 1.0, but preferably before.

General agreement on moving for 0.10 over 1.0, cut march 15. EDR and multilingual to 0.11.

Angelos volunteers as release manager

GeoHealthCheck fails on OARec schema parsing, not likely to be resolved before 0.10

Events

Great presence at OGC API sprint. OARec developments and neat demos on Ocean data by @jmunroe and DGGS by @allixender

Upcoming:

pygeoapi at the Developer Track of the next OGC Member meetings. OATiles, OAProc and OARec will be showcased
geopython conf. Paul has a slot on Bridge, will include some pygeoapi
FOSS4G: Tom submits a talk for pygeoapi. We will coordinate if/once accepted

we are putting forth another Geopython workshop at FOSS4G 2021, which (the last time) included a small bit on pygeoapi. Do we want a dedicated pygeoapi only workshop? Workshop may need to be refactored a bit. Pygeoapi will be included in geopython workshop.