Standards Working Groups consist of OGC members. They consider revisions to existing OGC Standards and bring new ones forward for adoption.
Members can access SWG sites by visiting Agora (Member Community).
If you would like to join a SWG but are not currently an OGC member, please get in touch.
The purpose of the OGC PubSub SWG is to define an OGC Implementation Standard that enables publish/subscribe functionality for resources supported by OGC API Standards in a well-defined manner.
The Routing SWG is chartered to develop and maintain an OGC API – Routes core standard and its extensions. Further, the SWG plans to publish and maintain a route exchange model.
The OGC SensorThings API provides an open and unified way to interconnect Internet of Things (IoT) devices, data, and applications over the Web. The OGC SensorThings API is an open Standard, and that means it is non-proprietary, platform-independent, and perpetual royalty-free.
The purpose of the ISO 19125 SWG is to update the common Standard that is both the OGC Simple Features Implementation Standard and the ISO 19125 Standards (Part 1: Common Architecture, and Part 2 SQL Option).
This working group defines a conceptual model and encodings for symbolizing digital Feature and Coverage data. It is also responsible for maintaining SLD/SE, an XML encoding for styles & symbology.
The purpose of this SWG is to adapt a set of existing Standards to provide the capability to represent and encode temporal metadata within data sets and protocols which uses a customized calendar.
The purpose of this SWG is to manage and update the TimeSeriesML Standard. The work derived, in part, from WaterML 2.0 Part 1.
The TrainingDML-AI SWG is chartered to develop the model and encodings for geospatial Machine Learning training data.
The OGC Features and Geometries JSON SWG is chartered to develop a JSON encoding for geospatial feature data. This encoding is intended to build upon the foundational OGC standards (such as Simple Features), be inclusive of other geospatial JSON encodings (such as GeoJSON), and support content delivery per the OGC
The purpose of the OGC Features API SWG is to develop new and maintain existing parts of the OGC API Features multipart Standard, develop corrigenda for the WFS 2.0 and FES 2.0 Standards, and review draft Engineering Reports from the OGC Innovation Program related to OGC API Features.
The purpose of this SWG is to develop a new Common core Standard for the OGC API suite of Standards as well as to manage any changes required for the OWS Common Standard.
The purpose of the TJS SWG is to update and maintain the OpenGIS Georeferenced Table Joining Service Implementation Standard [OGC 10-070r2]. Updates will consider Change Requests (CRs) to the current standard as well as requirements identified by the SWG.
The OGC-API Maps SWG will develop and document a Maps API candidate standard that will provide a web based, common, and consistent interface to services that aligns with the current architecture of the Web and the Spatial Data on the Web Best Practices ( https://www.w3.org/TR/sdw-bp/ ).
The OGC API – Processes Standard will enable the execution of computing processes and the retrieval of metadata describing their purpose and functionality. Typically, these processes combine raster, vector, and/or coverage data with well-defined algorithms to produce new raster, vector, and/or coverage information.
OGC API – Records provides discovery and access to metadata about geospatial data and services. OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. OpenAPI is used to define the reusable API building blocks.
The OGC API – Styles Standard will describe the interface and exchange of styling parameters and instructions. The construction of symbology components of styles is addressed in OGC Symbol Encoding Conceptual Model: Core Part and multiple OGC and other style encoding standards.
The OGC API – Tiles draft Standard references the OGC Two Dimensional Tile Matrix Set (TMS) standard. The TMS standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a
Members of the public can review candidate standards and share feedback to ensure they are practical and widely applicable.
Request For Comment (RFC)
OGC Seeks Public Comment on Candidate OGC SensorThings API Extension: WebSub Asynchronous Messaging Standard