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 incorporate the GeoTIFF specification into the OGC Standards suite by updating the specification to bring it into conformance with current OGC practices and to provide a forum for evolving the standard in the future, if need be.
The purpose of the GeoXACML SWG is to develop and maintain an OGC GeoXACML standard and associated coordination.
The GeoZarr Standard Working Group (SWG) is chartered to develop a Zarr encoding for geospatial gridded data in the form of Zarr conventions.
The purpose of the OGC GML SWG is to maintain the OpenGIS® Geography Markup Language (GML) Encoding Standard.The SWG may decide that the revision should be a joint project with ISO/TC 211 and result in a revision of ISO 19136, too.
The purpose of OGC GMLJP2 SWG is to manage revision to the GMLJP2 Standard. The SWG will process impacts to this standard from updates of dependent standards, address omissions from the initial standard, process comments from Innovation Program initiatives, and assess future work items for the Standard.
The Groundwater SWG aims to maintain a data exchange standard for the groundwater domain. The Standard is known as GroundWater Markup Language 2 (GWML2) and consists of conceptual and logical information models, as well as language specific implementations, which initially minimally include a GML-XML encoding specification.
The purpose of the OGC HDF SWG is to Standardize the HDF5 data model, its binary encodings, related extensions, and other appropriate items, and support other OGC working groups (SWG and DWG) in understanding the HDF5 data model and applying it in their domains of interest.
Water information needs to be shared across organizational and jurisdictional boundaries, which can be facilitated by OGC’s interoperability Standards. The Hydrologic Features SWGbrings together interested parties to develop and promote the technology for improving the way in which surface water information is organized, managed, and shared.
The purpose of this IndoorGML SWG is to develop an application schema of OGC GML and manage the adopted OGC Standard. This Standard provides a common schema framework for indoor navigation applications.
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