What is everybody going to be working on at the Open Standards Open Source Sprint?

[doublebyte1]

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

[danduk82]

I'd like to work on Baremaps

[fgravin]

I'll work within the GeoNetwork community. Probably plug the datahub (geonetwork-ui) to an OGC API records backend.

If you guys want to work on geonetwork/geonetwork-ui please add your name & ideas right here :smile:

[jahow]

I'd like to improve OGC API support in ogc-client and also work on having geonetwork-ui work on OGC API Records.

Also potentially some OpenLayers work regarding WebGL renderers.

[allixender]

I'd like to test/add DGGS-API with pygeoapi.

In the end I hope to arrive at a similar stage like this webgis DGGS custom demo from last year's code sprint.

• https://github.com/allixender/dggs-webgis (OpenLayers based web client)
• https://github.com/allixender/ogcapi-dggs-webdev-python (0.0.5 or 0.0.6 OGC DGGS API spec)

[allixender]

Potentially updating the DGGS Info website with more information, examples, code, documentation, so it can be more useful for the OGC DGGS Dev page

Source: https://github.com/allixender/dggs_webgen

[bchapuis]

I will work on Apache Baremaps and more specifically on the implementation of the OGC API.

[pvgenuchten]

Some ideas:

• enable datapackage model and datacite in pygeometa and mdme to bridge to iso and ogc api records
• a pythonic metadata workflow, using pygeometa, pycsw/geonetwork
• Improve html encoding (skin) of ogc api records in pycsw
• give a look at faceted search in postgres or ES, to facilitate aggregations plug-in for ogc api records in geonetwork or pycsw
• I'm looking for a basic SKOS codelist browser, I want to further investigate vocview, looking for people to revive the project with. Or even more simple, to generate a static website from skos ttl file as part of ci-cd, like widoco, but then with a ui like mkdocs

[jerstlouis]

Here are some of the things I may focus on during the code sprint:

OGC Styles & Symbology

• Implementing support for the Cascading Cartographic Symbology Style Sheets (CCSSS) encoding for the draft SymCore 2.0 in our GNOSIS tools
  • Rendering the styles in GNOSIS Cartographer and GNOSIS Map Server
  • Transcoding the style to and from SLD/SE and MapboxGL style (representations available through OGC API - Styles)
• Improve the SymCore 2.0 draft candidate standard (particularly in terms of the CCCSS and JSON encodings, encoding and visual examples the requirements classes)
• Discuss improvements and answer questions on the draft standard

OGC API - Maps

• Improving our OGC API - Maps implementation
  • Update to the latest changes (in particular the Core (currently missing response headers), Scaling, Subsetting and Display Resolution requirements classes)
• Work on the specification as needed and answer questions on the draft standard

OGC API - DGGS

• Improving our OGC API - DGGS implementation (example requests in this issue https://github.com/opengeospatial/ogcapi-discrete-global-grid-systems/issues/63#issuecomment-1488346827)
  • Improvements to the ISEA9R DGGS (missing 'neighbors', improve zone queries)
  • Missing zone IDs on GeoJSON representations of zone listing
• Work on the specification as needed and answer questions on the draft standard

OGC API - Processes

• Any feedback as needed on issues raised with the ETS for Part 1
• Improve our Part 3: Workflows & Chaining implementation
• Work on the (Part 3) specification as needed and answer questions on the draft standard

OGC API - Coverages

• Work on the OGC API - Coverages specification as needed and answer questions on the draft standard
• Improvements and work on offering netCDF and STAC/COG sentinel-2 data as Coverages in our implementation (including support for downsampling, range and domain subsetting, filtering and derived derived fields with CQL2), and as mechanism to trigger Processes - Part 3 processing or chaining as input to another process

OGC API - Tiles

• Any feedback as needed on issues the ETS under development for OGC API - Tiles
• Answer questions on the draft standard

[jiayuasu]

Some ideas for Integrate Apache SIS with Apache Sedona – CRS Transformation, GeoTiff Reader and more:

Apache Sedona is a high-performance cluster computing system designed specifically for processing large-scale spatial data. The system leverages a number of open-source libraries, including GeoTools, to execute spatial operations such as Coordinate Reference System (CRS) transformation and file reading. However, as an Apache project, Sedona is striving to reduce its reliance on GeoTools due to licensing issues. In order to address this challenge, Sedona is migrating affected functions to Apache SIS, which offers improved support for CRS transformation.

In this code sprint, we will concentrate on replacing GeoTools' usage in two key functions within Sedona: ST_Transform and the GeoTiff reader. Our focus will be on demonstrating how to migrate these functions to Apache SIS, providing a comprehensive tutorial on the necessary steps involved. By the end of this code sprint, you will have a solid understanding of how to replace GeoTools with Apache SIS within Sedona's functionality, allowing you to effectively tackle large-scale spatial data processing tasks.

[ByronCinNZ]

I'll work within the GeoNetwork community. Probably plug the datahub (geonetwork-ui) to an OGC API records backend.

If you guys want to work on geonetwork/geonetwork-ui please add your name & ideas right here 😄

I have limited availability, but sure - Byron Cochrane

[pvretano]

I'll be dedicating my code sprint time working on Records and Processes (mostly Part 1 [the new version] & 2).

[IvanSanchez]

As I announced at https://mastodon.social/@IvanSanchez/110186926642289665 , I'll be trying to build a prototype OGC API SensorThings for HomeAssistant.