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 this SWG is to manage the OGC KML Implementation Standard and to accommodate known issues and extensions identified in formal OGC Change Request Proposals (CRPs) and tested through implementation experience.
The LADM SWG will develop an encoding Standard (or multi-part Standard) of the five Parts of the ISO LADM Standard (some Parts currently under development). The content of the encoding Standard will derive requirements from the conceptual model items in the source LADM Parts.
This SWG maintains the Land and Infrastructure (LandInfra) Conceptual Model Standard and the associated parts of the InfraGML encoding Standard to describe the built environment.
With the development of communication and positioning technology such as Global Navigation Satellite System (GNSS), Wi-Fi, and Beacon, collecting movement data for moving features, typically vehicles and pedestrians, has become easy. The Moving Features SWG develops Standards to manage information about features whose locations continuously change over time.
The MUDDI (Model for Underground Data Definition and Integration) SWGwill standardize a conceptual model, a modular framework, one or more logical models, one or more implementation Standards and mappings to/from other models for geospatial data that represent underground infrastructure assets and characterize the underground environment that contains those assets.
The OGC netCDF SWG works to develop extensions of the existing OGC netCDF suite of Standards for additional data models, encodings, and conventions. It is focused on Earth Observation specific conventions in netCDF, and the NetCDF Classic Linked Data coding standard.
Standards-based exchange of observed, measured, or modeled data are key enablers for many critical online consumer and governmental services. The Observations and Measurements Standard defines a conceptual level data model for these datasets.
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 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