Attending
Torben Barsballe
Kevin Smith
Jukka Rahkonen
Jody Garnett
Andrea Aime
Actions from Last Meeting- Torben: Restore build server email updates [DONE]
- Jody: Private repository will go pay $7 a month just to get it done [Won’t Do]
Agenda- Travis CI - JDK 11 builds failing
-
Build Server - Repository, Cite Tests
-
Report from OGC Hackaton and ogcapi module
-
CITE Test Upgrade planning/interest
Actions- Jody: CITE Test upgrade page & proposal
Travis CI - JDK 11 builds failing
https://travis-ci.community/t/install-of-oraclejdk11-is-failing-11-0-3-12/3887
We basically will just need to wait for Travis to fix the issue.
Q: How do we want to handle backports / etc while waiting for a fix
A: Merge it if it is important, and let Jenkins verify
Build Server
Mostlying work 
- CITE still needs love
Release:
- Torben will update release scripts while doing the 2.15.2 release this week
Q: Push compiled binaries to GitHub?
A: No, SourceForge has better metrics.
Online Tests:
-
AppSchema broken - geotools PostGIS DB user needs elevated permissions
-
Oracle, MySQL - Pending availability
Report from OGC Hackathon and ogcapi module
London:
-
ogc features api - template used by others (formally wfs-3…)
-
ogc maps and tiles api - may show up as one or two services
-
ogc coverage api
-
ogc processes api
-
ogc catalog api - or records …
Each protocol:
-
tiny “core” + “extensions”
-
core:
-
feature - notion of collection
-
filter on space and time
-
filter on attribute - only do equality comparison
-
CRS:84
-
huh: no required output format …
-
huh: no schemas … yet
-
extension:
-
html, gml, geojson
-
described by open api documents that link to each other …
-
clients:
-
dynamic from open api document
-
generated from open api document
-
following links that have well-known relationships
Caution - not ready to implement yet
-
only ogc features api has a spec right now
-
everything else is ideas and test-bed prototypes
Suggestions in engineering report:
-
Suggest filtering using (E)CQL the way GeoServer does it
-
Consider: filter general on any attributes VS declare upfront attributes that are queriables
-
anything else is more than a month old …
Other activity:
-
processes group was active and tried implementing their ideas
-
map and tiles
-
considering adding as an extension to features or coverages (to visualize)
-
vector tiles? An add on for features … see wfs3 prototype
-
But what about process output etc…
-
But what about only doing maps (no feature or coverage access)
-
STAC tried to get compatible with wfs3 so no idea if they are going to keep pace …
-
Limited overlap with ogc coverage api? …
GeoServer
-
community module ogc api started
-
new dispatcher similar to spring MVC one … and still supports dispatcher callback and thread locals “geoserver” approach …
CITE Test Upgrade planning/interest
Updated the maintenance wiki page:
Any feedback or can we have a vote and start this?
This is of course tentative pending any party expressing interest….
Discussion:
-
ogc provides docker image for cite tests
-
Needs a minimum of orchestration to setup cite test image and geoserver image
-
This kind of means planet federal has the access needed to set this up with jenkins
(so deployment may not be part of contract phase…) -
Idea: overlay geoserver over ogc cite docker image
-
Idea: use official cite engine, would require cite test geoserver image to be internet accessible …
Action:
-
Jody: update CITE-Test-Upgrade with above options (docker …)
-
Jody: make a proposal for PSC to approve starting this …