CSAPI at the OGC Builder Days Code Sprint
Connected Systems at the May 2026 Sprint

Mon, 11 May 2026 – Wed, 13 May 2026 · London, UK (BST, UTC+1)
Participation Quick Links
Geovation — F4, Sutton Yard, 65 Goswell Rd., London EC1V 7EN, United Kingdom

See our talks Register

Countdown

Loading…

Counting down to 09:00 London, UK (BST, UTC+1) on Day 1.

May 2026

Loading…

Sprint days are highlighted. Today is outlined.

Time Zones

Location Local vs. London

How to Participate

Choose what works for you. Hybrid is fully supported.

Register & Connect

Register (free) on the OGC event page , then join the OGC events Discord (or the Matrix bridge ).

Review our Sprint Goals

Skim the Sprint Goals to see what OS4CSAPI participants intend to tackle. Pick a thread that overlaps your interests, or bring your own — anything CSAPI-adjacent is welcome.

Tell OGC what you'll work on

Comment on developer-events #181 — OGC's public "what is everybody working on" thread. CSAPI is currently underrepresented there.

Drop daily notes

See Daily Participation Reporting for the full guidance — short note each day, aggregated into the daily brief-backs.

Attend the Talks

Show up — in person or remote — for the four CSAPI-themed talks scheduled on Day 3 (Wednesday, 13 May), the final day of the sprint. Bringing an audience helps signal interest in CSAPI to the wider OGC community.

Registration

Free, but you must register on the OGC event page.

The OGC Builder Days Code Sprint is free to attend, in person at Geovation in London or remotely via Microsoft Teams. Registration is required either way — OGC uses it for headcount, the venue list, and the Teams invite.

Register on the OGC event page

After registering, join the OGC events Discord so you can find the #connected-systems channel before day one.

Sprint Goals

What OS4CSAPI is collectively working toward at this sprint.

  1. Arrive at 3 or more stable, independent open-source server implementations of CSAPI.
  2. Arrive at 3 or more stable, independent open-source client implementations of CSAPI.
  3. Create official conformance tests for CSAPI Parts 1 and 2.
  4. Prototype and test CSAPI Part 3 (Pub/Sub).
  5. Prototype and test CSAPI Part 5 (Binary).
  6. Resolve active, open GitHub issues on the official OGC CSAPI standard.
  7. Add open-source data-source transformers, ETLs, publishers, data simulators, and sample data.

Goal 6 tracks the official spec repository at https://github.com/opengeospatial/ogcapi-connected-systems .

About Issue #181

The "what is everybody working on" thread — and who's already on it.

OGC has opened a public GitHub thread, opengeospatial/developer-events#181 , inviting every sprint participant to post a comment describing what they plan to work on. It is the most visible single channel for getting your work onto OGC's radar before the sprint starts, and it is read by the organizers, mentors, and other tracks. If you would prefer not to post yourself, get the gist of it to Sam any way you like — a paragraph, a quick call, a text, a Discord DM — and it will be posted on your behalf with a clear attribution.

Suggested template — adapt freely

I will be working on [project / repo] during the May 2026 sprint as part of the OS4CSAPI community. My focus is [Pub/Sub, Binary, conformance tests, ETL, sample data, server, client, docs — pick what fits]. If anyone is interested in [collaborating on / testing / reviewing] this, please reach out on Discord or in the OS4CSAPI Discussions space.

Posts already up

4 CSAPI participants have posted on issue #181

See how others framed theirs — then add your own (or send it to Sam to post for you).

ricardogsilva avatar
@ricardogsilva relayed
OACS QGIS plugin

QGIS plugin that brings OGC API – Connected Systems data into QGIS as a client.

client QGIS
byteroad/qgis-oacs-plugin View on #181
Sam-Bolling avatar
@Sam-Bolling
OSHConnect-Python (OS4CSAPI fork)

A fleet of publishers that ingest public live data sources, map them to CSAPI, and publish to a CSAPI server — evolving rapid ingest tooling into a reusable open-source CSAPI publishing capability (fork of GeoRobotix's OSH Python client).

client publisher ETL sample data Python
OS4CSAPI/OSHConnect-Python View on #181
cam-s-hunt avatar
@cam-s-hunt
ets-ogcapi-connectedsystems10

Continuing work on a Connected Systems API Executable Test Suite (ETS) for the OGC TEAM Engine validator — standing up automated conformance testing for CSAPI implementations.

conformance test suite ETS TEAM Engine validator
Botts-Innovative-Research/ets-ogcapi-connectedsystems10 View on #181
nsnarayanam avatar
@nsnarayanam relayed
ogc-csapi-agent

Python ADK agent (Google Gemini) that drives the @camptocamp/ogc-client CSAPI client via a Node CLI subprocess to query CSAPI endpoints from natural language — a second consumer of the client library that has already surfaced real-world interop fixes.

client agent natural language Python Gemini ADK
nsnarayanam/ogc-csapi-agent View on #181

Posting on someone's behalf? Add an entry by opening a quick issue on the guide repo, or just send it to Sam.

Daily Participation Reporting

A short note each sprint day — aggregated into the daily brief-backs.

During the three sprint days, OS4CSAPI participants are encouraged to drop a short note each day describing what they got done, what's blocking them, and what they're picking up next. These notes get aggregated into the daily brief-backs and surfaced to the wider OGC community. Post directly in OS4CSAPI Discussions , or send your update to Sam any way you like — a written note, a quick call, a text, a Discord DM — and he will post it for you with attribution.

Suggested daily template — adapt freely

Day [1 / 2 / 3] — [your name / project]. Today: [what you got done]. Blockers: [anything stuck, or "none"]. Next: [what you're picking up tomorrow / after the sprint]. Looking for: [reviewers / testers / collaborators / nothing].

CSAPI Talks at the Sprint

Day 3 — Wednesday, 13 May 2026

Four OS4CSAPI participants are filling speaking slots across Day 3 — the final day of the sprint — with sessions running from late morning into early afternoon. Each presents on a Connected Systems topic. These are individual contributions to the broader OGC Builder Days agenda — not a dedicated CSAPI track. All sessions are accessible in person at Geovation, on Microsoft Teams, and via the #connected-systems Discord channel.

10:30 – 11:00 BST

A case study in vibe-coding OGC CSAPI

Sam Bolling — Riverside Research

Lifecycle walkthrough of an AI-assisted, no-code-skills contribution that produced a TypeScript client library for OGC API – Connected Systems.

Read the full abstract

AI-assisted software development has emerged in the mainstream and public domain and is trending in a way that can alter the landscape of software development. As an early adoption of the practice, Mr. Sam Bolling, with no coding skills, used practices from agile, scrum, extreme programming, and predictive waterfall to use AI tools to complete an open-source code contribution that implements a typescript client library for the OGC API Connected Systems standard. This session walks through the lifecycle of that activity from beginning to present.

11:30 – 12:00 BST

Implementing Binary Encodings with OGC CSAPI

Robin White — GeoRobotix

How binary encodings can complement CSAPI to reduce bandwidth and improve performance for high-rate sensor data while preserving interoperability.

Read the full abstract

Efficient exchange of sensor data becomes increasingly important as systems scale in volume, velocity, and operational demand. While OGC CSAPI provides a modern and standardized API approach for connected systems interoperability, binary encodings can help improve performance, reduce bandwidth burden, and support more practical handling of high-rate or data-intensive exchanges. This session walks through an implementation approach for applying binary encodings with OGC CSAPI, illustrating how they can complement the standard's API and data model foundations while preserving interoperability benefits.

13:30 – 14:00 BST

Implementing Pub/Sub MQTT with OGC CSAPI

Ian Patterson — GeoRobotix

Walkthrough of an MQTT-based pub/sub implementation that complements CSAPI for event-driven, low-latency dissemination of sensor data.

Read the full abstract

Many connected-system use cases require timely dissemination of events and updates without relying solely on repeated polling or strictly request-response interaction patterns. Publish/subscribe approaches can complement OGC CSAPI by supporting more responsive, event-driven exchange of sensor-related information across distributed systems. This session walks through an implementation approach using MQTT with OGC CSAPI to illustrate how pub/sub patterns can support interoperable connected-system workflows and highlight the practical benefits for real-world operational use.

14:30 – 15:00 BST

Automated tipping and cuing between a satellite and drone using OGC CSAPI

Drew Botts — GeoRobotix

End-to-end demo of cross-asset tipping and cuing built on CSAPI, using real, diverse sensing assets to illustrate the standardized capability.

Read the full abstract

Tipping and Cueing between different sensing assets with no native association is a key use case in many organizationally and operationally defined domains. OGC CSAPI is both aware of and addresses this use case in a straightforward and standardized approach. This session walks through an example of that use case with the application of real, diverse sensing assets to illustrate the enabled capability and highlight the benefits.

Repositories of Interest

Open-source CSAPI server and client repos of interest to the OS4CSAPI effort.

Servers

Clients & libraries

Tools, simulators & encodings

Quick Participation Links

Venue, links, and the practical details.

Venue
F4, Sutton Yard, 65 Goswell Rd., London EC1V 7EN, United Kingdom
Microsoft Teams
Join the meeting · Meeting ID: 291 891 040 830 07 · Passcode: eE7Zb7bh
Discord
https://discord.gg/3uyaZZuXr3
Matrix
https://matrix.to/#/%23ogc:matrix.org
Wiki
https://github.com/opengeospatial/developer-events/wiki/May-2026-Builder-Days-Code-Sprint
Registration
https://events.ogc.org/OGCBuilderDaysCodeSprint#/?lang=en
Hotels
See the Period and Location section of the OGC wiki for recommended hotels and transit notes.
Liaison
Sam Bolling (Riverside Research) is the OS4CSAPI liaison for this sprint. Any update — whether you want it forwarded to OGC, posted on issue #181, or just acknowledged privately — can go through him. Easiest channels: OGC events Discord, OS4CSAPI Discussions, or email.
GitHub
@Sam-Bolling
Email
sbolling@riversideresearch.org

Useful CSAPI Links

Specs and reference material for getting up to speed on CSAPI.

Spec
OGC API – Connected Systems – Part 1: Feature Resources (OGC 23-001) · Approved Implementation Standard — Systems, Deployments, Procedures, Sampling Features, Properties.
Spec
OGC API – Connected Systems – Part 2: Dynamic Data (OGC 23-002) · Approved Implementation Standard — DataStreams, Observations, Control Streams, Commands.
OpenAPI
Part 1 OpenAPI bundle (YAML, OAS 3.1) · Machine-readable Part 1 endpoint and schema definitions (all $refs resolved).
OpenAPI
Part 2 OpenAPI bundle (YAML, OAS 3.1) · Machine-readable Part 2 endpoint and schema definitions (all $refs resolved).
Guide
OGC API – Connected Systems Reviewer's Guide (OGC 23-053r1) · Official OGC reviewer's guide (PDF).
News
OGC API – Connected Systems – v1.0 publication announcement · Announcement of v1.0 and supporting-standard updates.
Repo
CSAPI standard repo (opengeospatial/ogcapi-connected-systems) · Public repository for the Connected Systems SWG.
Site
OS4CSAPI CSAPI developer page · CSAPI developer page — overview of CSAPI and the open-source ecosystem.
Forum
Connected Systems SWG — General · SWG space on OGC Agora.
Forum
Connected Systems SWG — Events · SWG events feed on OGC Agora.

About OS4CSAPI

Open Source for OGC API – Connected Systems.

OS4CSAPI is a continuing initiative led from inside the OGC API Connected Systems Standards Working Group that aims to collaborate with open-source projects to advance shared goals around the CSAPI standard. The OGC Builder Days Code Sprint in May 2026 is one event in the open-ended series in which OS4CSAPI participates.

This page is an open invitation. If you are working on anything CSAPI-related, in the open, during the timeframe of the sprint — and you would like that work to be visible to the OGC community at the event — then this guide is for you, and you are an OS4CSAPI participant for this sprint. There is no formal membership and no required hours.

Want to join the OS4CSAPI org?

OS4CSAPI is a GitHub organization , so joining means getting invited as a member. Send your GitHub handle to Sam ( @Sam-Bolling on GitHub, or sbolling@riversideresearch.org ) and an invitation will go out.

This is a community-maintained OS4CSAPI companion guide for participants working on OGC API – Connected Systems topics during the sprint. For official event registration, agenda, and venue information, use the OGC event page and sprint wiki .
Comments, questions, or suggestions about this site? Open an issue on the repo , drop a note in OS4CSAPI Discussions , or email sbolling@riversideresearch.org .