Code Sprint outcome

[doublebyte1]

During this code sprint I was involved in the following projects:

python-xacml-sdk (proof of concept)

• Added support for geometry data types (and other improvements) in the python xacml sdk.
  https://github.com/doublebyte1/python-xacml-sdk/commits/master

QGIS

• Feature request: Give support to OGC API Records metadata format in layer metadata qgis/QGIS#52856
• Give support to an OGC API Tiles layer qgis/QGIS#50296
• Feature request: Add support to OGC API Collections, through the "Add Layer Menu" qgis/QGIS#52674 (merged)

pygeoapi

• Update wording on OGC API - Tiles documentation, to be more aligned with the standard geopython/pygeoapi#1228
• I would like to thank @IngenieroGeomatico for his contribution 🔧 if conditional is added to the collections section geopython/pygeoapi#1226 (comment)

GDAL (ongoing)

• Give support to an OGC API Tiles layer qgis/QGIS#50296
• ogcapi update / fixes required OSGeo/gdal#6832
• - Added fixes for the OGC API Tiles driver OSGeo/gdal#7656 (merged)

[jerstlouis]

During this code sprint, the main thing I worked on was the JSON encoding for the OGC Styles & Symbology draft candidate Standard, including:

• Presenting the standard in detail to the GeoStyler team who provided us with valuable feedback.
• A new example styling polygon features
• A new JSON Schema for the encoding,
• Add some descriptive text for the section

I also provided some guidance to @doublebyte1 on fixing the OGC API - Tiles support in GDAL, discussed Processes - Part 3 with a few participants including @gfenoy who started implementing support for it in the ZOO project, presented overviews of OGC API - Maps, DGGS, Processes - Part 1-3, Coverages and OGC Styles and Symbology, took part in some OGC API - Features discussions on schemas, raised an issue with the CQL2-JSON encoding, took part in discussions on GeoPose in the SWG and with the Smapshot team and hosted an OGC API - DGGS breakout session.