End of Day 2 Report — OS4CSAPI at OGC Code Sprint 26

[Sam-Bolling]

🧭 OS4CSAPI — End of Day 2 Report

Date of Activities: October 21, 2025
Sprint: OGC Code Sprint 26
Project: Open Source for OGC API – Connected Systems (OS4CSAPI)

🧩 Overview

Day 2 of OGC Code Sprint 26 focused on consolidating the collaborative progress achieved during Day 1. Implementers across multiple open-source communities continued refining their Connected Systems integrations, validating schema behavior, and preparing demonstrations for Day 3. While no major specification updates were introduced, teams emphasized coordination, documentation, and environment readiness to ensure reproducible validation results. The OS4CSAPI initiative demonstrated sustained momentum and strong engagement across server and client implementations.

🏗 Establishing Collaborative Spaces and Onboarding

Day 2 showcased the first full use of OS4CSAPI’s shared collaboration spaces. The organization’s coordinated GitHub ecosystem supported agile tracking, discussion, and documentation across all active implementation threads. The Org-Level Project Workspace reflected visible momentum as multiple backlog items advanced through testing, review, and completion—including the 52°North team’s closure of Issue #11
in connected-systems-pygeoapi, marking a key Connected Systems validation milestone.

In parallel, the Meta Repository and Discussions Forum became central venues for technical exchange and onboarding. Contributors used these spaces to share interoperability findings, coordinate testing strategies, and document sprint feedback in real time. Welcome new member @doublebyte1 (Jo)! Their addition further strengthens OS4CSAPI’s growing, multi-project community.

Key Collaboration Links

🏛 OS4CSAPI GitHub Organization – central hub for coordination

📘 Meta Repository – planning, onboarding, and architectural alignment

🗂 Org-Level Project Workspace – agile tracking across linked repos

💬 Discussions Forum – transparent venue for sprint feedback

Current OS4CSAPI Members (8): @Sam-Bolling | @archerdev | @EricLo-417 | @mikebotts | @SpeckiJ | @teezip | @tomkralidis | @doublebyte1

🎯 Sprint Goal 1 — Validate OpenAPI Definitions for CSAPI Parts 1 & 2

Discussion Thread: Sprint Goal #1 Feedback

Day 2 carried forward the YAML validation activities initiated on Day 1. Participants continued monitoring the rebuilt bundle process described by @SpeckiJ and retesting existing files from both schemas.opengis.net and the opengeospatial/ogcapi-connected-systems
repository. No new bundle release was published during the day, and earlier reference and packaging issues—such as mixed relative and absolute imports, case-sensitivity mismatches (e.g., SensorML vs. sensorML), and missing schema dependencies—remained present.

While no additional findings were reported, implementers agreed to maintain side-by-side comparisons of the two sources to capture reproducible errors and support a more stable single-file bundle in future tag builds. The focus remains on improving discoverability and ensuring consistent tooling behavior once the next set of generated bundles becomes available.

🎯 Sprint Goal 2 — Validate Client Connectivity to CSAPI Servers

Discussion Thread: Sprint Goal #2 Feedback

Day 2 maintained focus on validating interoperability between OGC API – Features clients and CSAPI servers. The technical limitations documented on Day 1—particularly MIME-type handling and nested JSON arrays such as deployedSystems@link—remained unresolved, with no new validation results reported.

During the day, @SpeckiJ began preparing both the QGIS client application (QGIS Repository) and the 52°North pygeoapi server implementation (connected-systems-pygeoapi Repository) for a Day 3 demonstration. The setup includes curated sample data and configured endpoints intended to illustrate how Connected Systems resources appear within standard OGC API clients and to highlight current interoperability challenges in practice.

🎯 Sprint Goal 3 — Establish Multiple Independent CSAPI Implementations
Hakunapi Implementation Progress

The Hakunapi team continued development activities initiated on Day 1, focusing on integrating Connected Systems concepts into their OGC API – Features–based architecture. While no new public updates were reported on Day 2, contributors confirmed steady progress toward schema alignment and conformance test preparation. The Docker configurations and automation introduced earlier in the sprint remain the foundation for upcoming CSAPI endpoint experiments.

OpenSensorHub and OWSLib Implementation Progress

Work also continued in OpenSensorHub (OSH) and OWSLib, following the schema and test adjustments introduced on Day 1. The OSH Pull Request #318 that updated control-stream and command property names remained under review after successful automated checks, while OWSLib contributors continued to refine CSAPI test connections and mocked response strategies. Both efforts are advancing toward stable validation runs expected later in the sprint.

52°North pygeoapi Implementation Progress

@SpeckiJ reported from Rotterdam that the 52°North Connected Systems pygeoapi (repository) was updated to align with the latest pygeoapi core version and re-enabled integration with existing specifications. Several new issues and TODOs were opened to guide future development. Work also began on preparing a public demo instance populated with sample CSAPI data and improving documentation to make the repository easier to navigate. These actions position the implementation for potential upstream integration and a Day 3 demonstration.

Camptocamp OGC Client Implementation Progress

Client-side development within the Camptocamp OGC Client (repository) advanced through continued alignment and testing of the new CSAPI module written in TypeScript. Over Day 2, contributors focused on verifying integration with the existing endpoint lifecycle and refining the module’s type models to accurately reflect Connected Systems schema structures.

The implementation successfully passed internal checks confirming import/export parity, barrel organization, and shared Jest harness compatibility. These refinements strengthen the client’s readiness for upcoming interoperability testing and ensure consistent behavior across server–client CSAPI exchanges.

🧮 Summary

Day 2 reinforced OS4CSAPI’s foundation for collaborative, multi-project development. While technical milestones largely extended Day 1’s efforts, the day was defined by improved coordination, documentation, and demonstration preparation across all implementations. The 52°North team completed key updates to their pygeoapi implementation, contributors advanced TypeScript client integration within Camptocamp’s OGC Client, and cross-project testing environments were positioned for validation in the coming days.

With demonstrations scheduled for Day 3 and documentation updates underway, OS4CSAPI enters the midpoint of OGC Code Sprint 26 with a cohesive community and a shared focus on practical interoperability.