Meeting 2020 07 27
https://gitter.im/geopython/pygeoapi
- review of previous meeting actions
- OGC API - Records implementation
- OGC API - Coverages implementation
- HTML/UI strategy
- Python 2 support and dev style adoption
- 0.8 release, 0.9 milestones
- 1.0 roadmap
- Google Summer of code (update on current status, next steps)
- Triple store (RDF) implementation of WoSIS dataset - prototype guidelines
- Events
@tomkralidis (chair) @jorgejesus (meeting notes) @kalxas
- There was not enough attendees, some decisions will be taken on next meeting
- See actions
- Review of data provider code https://github.com/geopython/pygeoapi/issues/403#issuecomment-650502840
- OGC API - Records implementation, work in progress, concluded to implement TinyDB
- slowly evolving. I expanded our provider configuration to take into account for OACov, as well as Coverages that could be advertised as features. Waiting on OACov sprint to further make a dent based on what’s in the coverages branch.
Need to be carefull with merge into master, bad experience from OAProc Our recent schema troubles in OAProc are a good example (https://github.com/geopython/pygeoapi/pull/494)
Skipped to next meeting
dropped Python 2 support, f-string and .format() to be decided later.
6 and 7 (https://github.com/geopython/pygeoapi/milestone/3) roadmap
No decision
@FarheenB has implemented pycql on the pytests, and now she is looking at a full example using an URL @alex-mathew has the rest end points done, some issues of implementation logic with json-merge they have been working on simple data providers, csv and geojson for GSoC-3 they have to work on other data providers
In ISRIC, We have triple store (virtuoso) that supports GeoSparql, and there we have dataset and profiles as "entry point", the idea is for pygeoapi have as tripple store provider and output JSON-LD specific for this Like OAProc, I am concern on merging to master, and would also like to look at the geojson-ls content This is a bit blue sky research and has to be present on the 1st week of September. @alex-mathew will likely have comments/opinions here
- @francbartoli, @kalxas and @tomkralidis presenting pygeoapi at https://www.w3.org/2020/maps/
- @tomkralidis presenting pygeoapi at ApacheCon: https://www.apachecon.com/acna2020/
- @jorgejesus @alex-mathew and @FarheenB have also register for the OAFeatures OGC meeting in September
- @tomkralidis will also give a report at the OSGeo AGM in September (we are a community project)
- @justb "mini" GeoPython 2020 online edition, September 21-22, 2020 ???
- Drop support for python2
- @justb give access to demo server to @tomkralidis
- @justb create endpoints on demo.pygeoapi.io for student to demo
- @tomkralidis to update docs on provider support (https://github.com/geopython/pygeoapi/issues/403)
- @jorgejesus: to contact providers https://github.com/geopython/pygeoapi/issues/403#issuecomment-650502840 to determine if ok to move table to read the docs
