Meeting 2020 05 11 - geopython/pygeoapi GitHub Wiki

Date/Time

@justb4, @jorgejesus, @tomkralidis, @francbartoli

(pygeoapi) OGC API - Tiles workflow is:

clients generates static tiles (using things like tippecanoe or other tooling)
pygeoapi OGC API - Tiles connects accordingly via URL (like Minio, s3, Azure blob storage). We need to also implement file-based access
No style implementation for now

Once we have file-based access (in addition to object storage access) we can clean things up, test, document and push?? a

basic implementation that ingests metadata docs into ES and exposes accordingly.

possibility of pycsw to be backed of

Some tests and implementations on rasterio (also an xarray/dash backend)

need a JSON schema of sorts once things settle, before we hit 1.0, at which point we need to have stable support
records and coverages on 0.8

start coding on 1st June

preperation before around 22th June

OGC API - Features - P3 - Common Query Language (http://docs.opengeospatial.org/DRAFTS/19-079.html)
OGC API - Features - P4 -Simple Transactions (http://docs.opengeospatial.org/DRAFTS/20-002.html) The proposals are on the GSOC but i can put then on a public place

CQL , take a look at pycql as a first step.

Setup endpoint for them to demo the code

pygeoapi workshop proper for many purposes

Athens is postponed to a later date. Worst case is March 2021

Moved from previous actions:

@tomkralidis: file a ticket about starting a pygeoapi workshop
@jorgejesus: issue/writeup so we can clarify data provider code maintenance policy

New actions:

@tomkralidis report on OGC API - Records next month @tomkralidis report on OGC API - Coverages next month

@francbartoli will update with @FarheenB to check on update of proposal

@jorgejesus to check with @alex-mathew concerning data transaction proposal

@justb to create end points on demo.pygeoapi.io for student to demo @justb to give acess to demo server to @tomkralidis