Meeting 2020 06 22

Date/Time

@tomkralidis (chair) @jorgejesus @francbartoli @justb4 (meeting notes) @pvgenuchten @kalxas (on mobile)

@tomkralidis: file a ticket about starting a pygeoapi workshop: done in #434
@francbartoli will update with @FarheenB to check on update of proposal. "we have updated the proposal that is now in sync with the specification. Farheen is now working on the generation of the openapi document".
@jorgejesus to check with @alex-mathew concerning data transaction proposal: "@alex-mathew proposal is ok, he is implementing the openapi doc on the code and has an issue for the the REST points. Keep in mind that students had the end of the semester on the 15th of June and now they have seminars The first 1 month was not the best, but there is more availability on the next 2 months]".

@tomkralidis: "we’re still early days in OARec so I’m hesitant to push to master, so I will continue to work on it as we evolve the spec. I will probably add a default TinyDB document backend once it’s ready. @kalxas demo’d it at the INSPIRE workshop a couple of weeks ago while presenting with @pvgenuchten. @tomkralidis: demoing it in the OGC MetOceanDWG. all to say it’s a work in progress. If folks are really adamant we could focus on pushing it to master."

@tomkralidis: "I haven’t had much time to work on this, sadly, but am targetting to have something stable soon (on the OACov SWG) to do baseline CoverageJSON output. ...will be a bit tricky given raster data could be a single file, or a set of files which need to be filtered, etc. Still early days. The OACov spec is also early days."

@tomkralidis: released 0.8 a few weeks ago (thanks @kalxas). @justb4 also updated the demo server (for stable endpoint).
@tomkralidis: nothing in 0.9 yet: https://github.com/geopython/pygeoapi/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.9.0
@tomkralidis: but we do have some items for 1.0: https://github.com/geopython/pygeoapi/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0
@francbartoli : proposes: "planning 0.9 for end of Sept and 1.0 end of year".
@francbartoli : "Tiles Status: been busy in the last one month and no progress there but now I can work on it. Think it can land 0.9 for end of Sept"
0.9 milestone updated https://github.com/geopython/pygeoapi/milestone/7

@tomkralidis: "move OARec support to 1.0"
@tomkralidis: "would be cool to have coverages, tiles, features, processing and records for 1.0"
@pvgenuchten: "move Oarec to a feature branch in the main repo?". @tomkralidis: "mindful about having features branch in the main repo as they could go stale, but they are good for shared hacking give me a couple of weeks?"

@jorgejesus: "... 1st month has been slow ... will be better availability in the next 2 months. cql filtering needs a bit more attention compared to the data transaction. Students have been present mentors had to spend more time than expected on GSoC, a bit of frustation we have the first review on the 29th"
@jorgejesus: "Issues should have been more fine-grained. Bit hard for newcomers to integrate the yaml, openapi doc, json-schema, where things fit unless they have already worked with the tools"
@jorgejesus: Overall status: "have a generic review a the end of the month, but don't expect any code merge until the end of the GSoC"

@tomkralidis: "donate button on https://pygeoapi.io"
@pvgenuchten: "idea: raise funds for specific topics?"
@justb4: https://opencollective.com/ e.g. https://opencollective.com/openlayers ?

@tomkralidis: "..gave presentations at INSPIRE conf ... presented twice (OAFeat and OARec) thanks to Angelos and Paul and everyone
@pvgenuchten: "mentioned pygeoapi at FOSS4GUK"

@justb give access to demo server to @tomkralidis
@justb create endpoints on demo.pygeoapi.io for student to demo
@jorgejesus: issue/writeup so we can clarify data provider code maintenance policy
@jorgejesus: will recheck @alex-matthew again to be certain
all: GSoC discussion for next PSC meeting following a review