What is everybody going to be working on?

[ghobona]

Post a comment letting us know what you are going to be working on.

[pomakis]

CubeWerx has been involved in the development of the various OGC API specifications. In an effort to make sense of them all, and to shake out the details and the missing pieces, we've implemented a test service at https://test.cubewerx.com/cubewerx/cubeserv/demo/ogcapi/Daraa which we are constantly updating as the specifications evolve.

We're offering this service for use during the sprint to use as a proof-of-concept implementation of the "OGC API - Coverages" specification and its integration within an OGC API framework. I encourage participants (especially client-side implementers) to experiment with our service implementation and provide feedback. I'll be present for the first day of the sprint, and I believe my colleague Peter Vretanos will be available both days, to demonstrate our implementation and to help work out some of the evolving details of the specifications.

[jerstlouis]

Ecere will be focusing on a server-side implementation of OGC API - Coverages and contributing to the development of the specifications. Our test service is at https://maps.ecere.com/ogcapi, with only minimal support for coverages at the moment (e.g. 16-bit PNG data values at https://maps.ecere.com/ogcapi/collections/Daraa:Daraa_DTED/coverage). We will likely be focusing on adding GeoTIFF support for the sprint, in addition to getting the CIS JSON DomainSet & RangeSet right in the collection resource, and improving support for temporal queries. We will also be supporting coverage tiles (e.g. https://maps.ecere.com/ogcapi/collections/Daraa:Daraa_DTED/tiles).

We may also try to make progress on the client-side as well.

[jyutzler]

IM will be continuing its work its GeoPackage Provisioner. The main goal is to be able to read DTED data and add it to a GeoPackage as PNG files using the Tiled Gridded Coverage Extension. We also intend to build test code that navigates key offerings (not just Coverages, but all OGC APIs) from each provider listed in https://github.com/opengeospatial/OGC-API-Sprint-August-2020/blob/master/implementations.adoc. We have already done Cubewerx.

[tomkralidis]

pygeoapi will continue work on OACov, building off the January 2020 Coverages and Processing Sprint. Specifically, continuing on response formats for coverage descriptions as well as native coverage output.

Code: https://github.com/tomkralidis/pygeoapi/tree/oacov
Demo: https://dev.api.weather.gc.ca/coverages-demo/collections/gdps-temperature

[joanma747]

From my side, Nuria and I are on vacation so I will limit my participation to "chat" a bit. :-(
But this does not mean that we are not interested in implementing OGC API coverages in the near future.