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 revise, publish, and maintain GeoDCAT, a spatio-temporal profile of the W3C DCAT Recommendation [DCAT] , and provide guidance about its use and further specialization.
GeoPackage is an open, platform-independent, portable, self-describing, compact format for transferring geospatial information.
The OGC GeoParquet SWG will work to advance the GeoParquet encoding format for cloud-native vector data to an OGC Encoding Standard. GeoParquet builds upon Apache Parquet, described by Apache as “an open source, column-oriented data file format designed for efficient data storage and retrieval. It provides efficient data compression and
This SWG developed GeoPose 1.0, a standard for geographically-anchored pose (GeoPose) with 6 degrees of freedom referenced to one or more standardized Coordinate Reference Systems (CRSs). The SWG now supports implementers of GeoPose 1.0 standard and identifies future enhancements for the widespread adoption of this standard.
The purpose of this SWG is to maintain the GeoSciML data model and application schema for geoscience information interchange.
Since the release of GeoSPARQL [1] in 2012, there has been growth of both the Semantic Web and spatial information represented in Semantic Web [2] form. The purpose of this SWG is to revise, and likely extend, the GeoSPARQL standard.
The standardization promoted by this SWG will support transparency in international reporting indicators which rely on geospatial data, referred to as Geospatial Reporting Indicators.
The Geospatial User Feedback Model and Catalogue profile give the user community a formal process for maintaining, improving, documenting feedback on the suitability and use of geospatial data.
A Geosynchronization service, deployed by a data provider, sits between the features a provider offers via a Web Feature Service and data collectors. It allows data collectors to submit new data or make modifications to existing features without directly affecting the features in the provider’s data store(s) until validation has
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