OGC API Connected Systems Standard | Web API for Connected Systems

OGC API - Connected Systems Standard

The OGC API — Connected Systems Standard (aka “this Standard” or “CS API”) specifies the fundamental API building blocks for interacting with Connected Systems and associated resources. A Connected System represents any kind of system that can either directly transmit data via communication networks (being connected to them in a permanent or temporary fashion), or whose data is made available in one form or another via such networks. This definition encompasses systems of all kinds, including in-situ and remote sensors, actuators, fixed and mobile platforms, airborne and space-borne systems, robots and drones, and even humans who collect data or execute specific tasks.

Documents

(Hover over Type for full description)
Document title	Version	OGC Doc No.	Type
OGC SensorML Encoding Standard	3.0	23-000	IS
OGC API - Connected Systems - Part 1: Feature Resources	1.0	23-001	IS
OGC API - Connected Systems - Part 2: Dynamic Data	1.0	23-002	IS
OGC SWE Common Data Model Encoding Standard	3.0	24-014	IS
OGC API - Connected Systems Standard v1.0 Reviewers Guide		23-053r1	UG

Official model files and encoding schemas

Submit a Change Request, Requirement, or Comment for this OGC standard.

Overview

OGC API – Connected Systems is intended to act as a bridge between static data (geographic and other domain features) and dynamic data (observations of these feature properties, and commands/actuations that change these feature properties). “Part 1 — Feature Resources” defines resource types and encodings for providing metadata about systems and their deployments, as well as the procedures and sampling strategies used by these systems. Resource types defined in Part 1 are modeled on concepts from the Semantic Sensor Network Ontology (SOSA/SSN). “Part 2 — Dynamic Data” defines additional resource types and encodings that implement the SSN concepts needed for exchanging dynamic data related to the features defined in Part 1. It defines efficient ways of encoding this dynamic (time-varying) information (including observations, commands and system events), and mechanisms allowing bi-directional streaming of real-time data as well as access to historical data. Part 2 also defines a snapshot mechanism for dynamic feature properties.