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 a Standard for Well Known Text (WKT) representation of Coordinate Reference System (CRS) definitions.
The purpose of this SWG is to explore and manage a Standard to enable interoperability through the use of Discrete Global Grid Systems (DGGS). The goal of the SWG is to increase awareness of the advantages of DGGSs in general, to define the qualities of a DGGS, to make them
The Environmental Data Retrieval API SWG will standardize several APIs, defined with OpenAPI (Version 3), to query and retrieve various common data patterns from a relatively persistent data store. The data patterns will include, but are not restricted to, data at a point in space and time, time series at
The Earth Observation Metadata profile of Observations & Measurements is an OGC Implementation Standard that provides a concise model for documenting Earth Observation Product metadata.
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 OGC GeoAPI SWG aims to maintain the GeoAPI Standard, which defines a set of programming language API along with an associated test suite, to provide a standardized, programming language level realization of some core OGC Standards.
Geocoding is a core activity for linking an address or text description to a location on earth. It is in many cases the entry point into the location dimension, unlocking the application of location to many problems including business intelligence, mapping, and routing.
The GeoDataCube SWG has the goal to facilitate the handling of different GeoDataCubes via a Standardized API that will serve the core functionalities of GeoDataCubes.
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