What is everybody going to be working on, at the 2024 Joint OGC - ASF - OSGeo Sprint?

[doublebyte1]

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

[fgravin]

I am planning to work mostly on

• OGC API Records Facet proposal, to make it concrete and accepted
• GeoNetwork OsGeo project to investigate using OGC API Records back from the geonetwork-ui datahub project

[gberaudo]

Provided my registration is accepted, I am planning to work on:

• OL-Cesium examples improvements;
• OpenLayers flat style improvements.

@doublebyte1, would be great to improve the registration process. See my comments to the organizers in my registration application.

[doublebyte1]

@gberaudo thank you for the feedback and welcome to the code sprint!

[jerstlouis]

Some of the things we may end up working on at the code sprint:

• Styles & Symbology 2.0 with @maxcollombin -- in particular a BNF grammar for CartoSym-JSON, a parser for it, a style transcoder between CartoSym-JSON / CartoSym-CSS as well as with SLD/SE and MapboxGL, and support for rendering styles in our GNOSIS SDK. Somewhat related to https://github.com/opengeospatial/ogcapi-features/issues/705 .
• Fix up / tweak our Features - Part 5: Schema implementation.
• Support for CQL2-JSON in our OGC API implementation
• Finalizing our DE-9IM / CQL2 Spatial Functions support, possibly using these together with our OGC API - Maps, OGC API - Coverages and OGC API - DGGS implementation (e.g., to cut out hexagonal ISEA3H DGGS zones from a coverage with an S_INTERSECTS() filter, and cross feature collection/coverage queries).
• Look at Records in terms of how it fits with Coverage Scenes.
• Our OGC API - DGGS implementation, including a hierarchical JSON / UB-JSON data encoding for sub-zones of hexagonal grids in particular , related DGGS discussions with @ldesousa and @allixender

[desruisseaux]

GeoAPI 3.0 currently has two implementations:

• Apache SIS (direct implementation)
• PROJ-JNI (wrappers)

If there is volunteers, a topic that I propose is to add wrappers for the following implementations (I do not plan to do this work myself for now, but would be very glad to help if someone takes this task):

• PROJ4J
• GeoTools 30 or later

An immediate benefit for those projects is to be able to run test suites, including the Geospatial Integrity of Geoscience Software tests.

[tomkralidis]

From here:

• pygeoapi:
  • update of pygeoapi OGC API - Coverages support given recent changes to the specification (cc @jerstlouis). If there are any clients to test with, please reach out
  • review of Shapely processor work and design/implementation with @krishnaglodha and @prajwalita
• OWSLib: review of ISO 19115-3 feature addition (https://github.com/geopython/OWSLib/pull/900 -- cc @vjf)
• OGC API - Records:
  • implementation updates as required (Geopython stack, QGIS)
  • Facets extension (w/ @fgravin)

[kalxas]

My work plan:

• pycsw: new 3.0.0-alpha6 release (Done: https://github.com/geopython/pycsw/releases/tag/3.0.0-alpha6)
• OWSLib: review of ISO 19115-3 pull request https://github.com/geopython/OWSLib/pull/900 (Done)
• OGC API - Records: Review ATS before submission to OAB https://github.com/opengeospatial/ogcapi-records/issues/344 (Done: https://github.com/opengeospatial/ogcapi-records/pull/345)
• UbuntuGIS packaging updates for GDAL 3.8.4 and QGIS 3.34.4 (https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-experimental/+packages?field.name_filter=&field.status_filter=published&field.series_filter=jammy)

[TaehoonK]

MF-SWG: Documentation

• Validation against the designed Core APIs
• Validation of the designed APIs against the Abstract Test Suite (ATS)

Development

• Further implementation of APIs not supported by MF-API Server (queryable API part)
• Implement STINUUM to support the newly implemented function of the MF-API Server

For more details: https://github.com/opengeospatial/mf-swg/tree/main/codesprint/2024_joint_ogc_osgeo_asf_code_sprint

[tomkralidis]

My resulting report can be found at #131

[maxcollombin]

Styles & Symbology report: #132

[tomkralidis]

Update: the pygeoapi "Shapely functions as a process work" that originated at this sprint has resulted in the integration into pygeoapi core master branch: https://github.com/geopython/pygeoapi/pull/1565 (docs now at https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-processes.html#shapely-functions-optional). Thanks for the valuable contribution @jeafreezy!

[jeafreezy]

Thank you @tomkralidis! I took a look at the deployed docs, and I noticed a typo in the curl url. It must have been an oversight from my end. I was going to open a PR to fix that, but I noticed you have already. Thank you!