OGC Standards
Below is a list of OGC Implementation Standards.
Implementation Standards are different from the Abstract Specification. They are written for a more technical audience and detail the interface structure between software components. An interface specification is considered to be at the implementation level of detail if, when implemented by two different software engineers in ignorance of each other, the resulting components plug and play with each other at that interface.
Any Schemas (xsd, xslt, etc) that support an approved Implementation Standard can be found in the official OGC Schema Repository.
Implementation Standards are different from the Abstract Specification. They are written for a more technical audience and detail the interface structure between software components. An interface specification is considered to be at the implementation level of detail if, when implemented by two different software engineers in ignorance of each other, the resulting components plug and play with each other at that interface.
Any Schemas (xsd, xslt, etc) that support an approved Implementation Standard can be found in the official OGC Schema Repository.
| Document Title (click to view/download) | Version | Doc.# | Editor | Date |
|---|---|---|---|---|
 CDB Multi-Spectral Imagery Extension |
1.0 | 17-080r2 | Ryan Franz | 2018-09-20 |
| The “Multi-Spectral Imagery” extension defines how to encode and store reflected electromagnetic radiation from the infrared wavelengths into a CDB. The portion of the spectrum targeted is between the visible spectrum (current imagery and texture in CDB), and longer wavelength infrared that is primarily emissive and can be simulated based on the material temperature. See more... | ||||
 CF-netCDF3 Data Model Extension standardnetcdf-data-model-ex |
3.1 | 11-165r2 | Ben Domenico and Stefano Nativi | 2013-01-03 |
| The OGC netCDF encoding supports electronic encoding of geospatial data, that is, digital geospatial information representing space and time-varying phenomena.
This standard specifies the CF-netCDF data model extension.
This standard specifies the CF-netCDF data model mapping onto the ISO 19123 coverage schema.
This standard deals with multi-dimensional gridded data and multi-dimensional multi-point data.
In particular, this extension standard encoding profile is limited to multi-point, and regular and warped grids; however, irregular grids are important in the CF-netCDF community and work is underway to expand the CF-netCDF to encompass other coverages types, including irregular gridded datasets.
See more... | ||||
| Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual CommonC1 |
11-157 | Jim Greenwood | 2011-10-18 | |
| This document being corrected specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. The Common Implementation Specification aspects specified by this document currently include:
a) Operation request and response contents, most partial
b) Parameters and data structures included in operation requests and responses c) XML and KVP encoding of operation requests and responses See more... | ||||
| Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report CommonC2 |
11-158 | Jim Greenwood | 2011-10-18 | |
| This document defines the corrigendum change notes for <OGC Web services Common Specification v1.1.0. This document was approved by the OGC membership on December 2010 . As a result of the Corrigendum process, there were edits and enhancements made to this standard to correct typographic errors, schema errors, or some deficiency that prevented proper use of this standard. This document provides the details of those edits, deficiency corrections, and other corrects. It also documents those items that have been deprecated. See more... | ||||
| Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 WPS 1.0 Corr |
0.0.8 | 08-091r6 | Peter Schut | 2009-09-16 |
| This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Processing Service version 1.0.0 and does not modify that standard. The current OpenGIS Implementation Standard that this document provides revision notes for is 05-007r7. See more... | ||||
| CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW |
1.0.1 | 07-110r4 | Richard Martell | 2009-02-05 |
| This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. See more... | ||||
| CSW-ebRIM Registry Service - Part 2: Basic extension package CAT2 ebRIM part2 |
1.0.1 | 07-144r4 | Richard Martell | 2009-02-05 |
| Incorporates Corrigendum 1 (OGC 08-102r1). See more... | ||||
| GeoAPI 3.0 Implementation Standard |
3.0 | 09-083r3 | Adrian Custer | 2011-04-25 |
| The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards. See more... | ||||
| GeoAPI 3.0 Implementation Standard with corrigendum |
3.0.1 | 09-083r4 | Adrian Custer | 2018-04-15 |
| The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards. See more... | ||||
| Geographic information — Well-known text representation of coordinate reference systems |
2.0.6 | 18-010r7 | Roger Lot | 2019-08-13 |
| This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings.
This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations.
This jointly developed draft has been submitted by ISO TC211 for circulation as a Draft International Standard (DIS). This version incorporates comments made during the ISO TC211 New Work Item Proposal acceptance ballot. See more... | ||||
| Geographic information — Well known text representation of coordinate reference systems |
1.0 | 12-063r5 | Roger Lott | 2015-05-01 |
| This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2007 and ISO 19111-2:2009. It extends the earlier WKT to allow for the description of coordinate operations. This International Standard defines the structure and content of well-known text strings. It does not prescribe how implementations should read or write these strings.
The jointly developed draft has also been submitted by ISO TC211 for publication as an International Standard document. The version incorporates comments made during both the OGC Public Comment Period as well as the ISO ballot for DIS (ISO TC211 document N3750).
See more... | ||||
| Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum |
1.0.1 | 11-017 | Andreas Matheus, Jan Herrmann | 2011-05-12 |
| The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). See more... | ||||
| GeoXACML Implementation Specification - Extension A (GML2) Encoding GeoXACML extA |
1.0 | 07-098r1 | Andreas Matheus | 2008-02-23 |
| This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard. See more... | ||||
| GeoXACML Implementation Specification - Extension B (GML3) Encoding GeoXACML extB |
1.0 | 07-099r1 | Andreas Matheus | 2008-02-23 |
| This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries. See more... | ||||
| NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format netcdf-binary |
1.0 | 10-092r3 | Ben Domenico | 2011-04-05 |
| This document defines an OGC® Standard for encoding binary representations of space-time varying geo-referenced data. Specifically, this standard specifies the netCDF classic and 64-bit offset file binary encoding formats. This standard specifies a set of requirements that every netCDF classic or 64-bit offset binary encoding must fulfil. See more... | ||||
| Observations and Measurements - XML Implementation |
2.0 | 10-025r1 | Simon Cox | 2011-03-22 |
| This standard specifies an XML implementation for the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156), including a schema for Sampling Features. This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard.
More specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. See more... | ||||
| OGC API - Features - Part 1: Core |
1.0 | 17-069r3 | Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel | 2019-10-07 |
| OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.
The OGC API family of standards is organized by resource type. This standard specifies the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest. See more... | ||||
| OGC Augmented Reality Markup Language 2.0 (ARML 2.0) |
21.0 | 12-132r4 | Martin Lechner | 2015-02-24 |
| This OGC® Standard defines the Augmented Reality Markup Language 2.0 (ARML 2.0). ARML 2.0 allows users to describe virtual objects in an Augmented Reality (AR) scene with their appearances and their anchors (a broader concept of a location) related to the real world. Additionally, ARML 2.0 defines ECMAScript bindings to dynamically modify the AR scene based on user behavior and user input. See more... | ||||
| OGC City Geography Markup Language (CityGML) Encoding Standard |
2.0 | 12-019 | Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele | 2012-04-04 |
| CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.
The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.
See more... | ||||
| OGC Coverage Implementation Schema |
1.1 | 09-146r6 | Peter Baumann, Eric Hirschorn, Joan Masó | 2017-09-15 |
| Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimensional regular and irregular grids, point clouds, and general meshes.
This Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which specifies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.”
Coverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or NetCDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmonization and interoperability between and across these domains. See more... | ||||
| OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension |
1.0 | 16-083r2 | Eric Hirschorn | 2017-06-15 |
| The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].
This OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]. See more... | ||||
| OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum |
1.0.1 | 16-083r3 | Eric Hirschorn | 2019-01-20 |
| The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].
This OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]. See more... | ||||
| OGC Coverage Implementation Schema with Corrigendum |
1.1.1 | 09-146r8 | Peter Baumann, Eric Hirschorn, Joan Masó | 2019-10-28 |
| Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimensional regular and irregular grids, point clouds, and general meshes.
This Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which specifies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.”
Coverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or NetCDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmonization and interoperability between and across these domains. See more... | ||||
| OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard |
1.0 | 17-003r1 | Y. Coene, U. Voges, O. Barois | 2020-02-14 |
| JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR3] encoding for Earth Observation (EO) metadata for datasets (granules). This standard can be applied to encode metadata based on the Earth Observation Metadata Profile of Observations and Measurements (O&M) OGC 10-157r4 [OR1] or as an encoding of the Unified Metadata Model for Granules (UMM-G) conceptual model [OR2].
The GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF XML [OR11] and RDF Turtle [OR12].
This document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. The documented approach can be applied in combination with the following technologies:
OGC OpenSearch extensions [OR19], [OR20], [OR25],
W3C Linked Data Platform [OR21], [OR22],
OASIS searchRetrieve [OR23],
OASIS OData [OR24].
GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.
JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR18] which allows validation of instances against these schemas. See more... | ||||
| OGC Filter Encoding 2.0 Encoding Standard - With Corrigendum |
2.0.3 | 09-026r2 | Panagiotis (Peter) A. Vretanos | 2014-08-18 |
| A fundamental operation performed on a set of data or resources is that of querying in order to obtain a subset of the data which contains certain desired information that satisfies some query criteria and which is also, perhaps, sorted in some specified manner.
This International Standard defines an abstract component, named AbstractQueryExpression, from which other specifications can subclass concrete query elements to implement query operations. This International Standard also defines an additional abstract query component, named AbstractAdhocQueryExpresison, which is derived from AbstractQueryExpression and from which other specifications can subclass concrete query elements which follow a query pattern composed of a list of resource types to query, a projection clause specifying the properties of those resources to present in the result, a projection clause composed of predicates that define the subset of resources or data in the result set and a sorting clause indicating to order in which the results should be presented. This pattern is referred to as an ad hoc query pattern since the server is not aware of the query until it is submitted for processing. This is in contrast to a stored query expression, which is stored and can be invoked by name or identifier.
This International Standard describes an XML and KVP encoding of a system-neutral syntax for expressing the projection, selection and sorting clauses of a query expression. The intent is that this neutral representation can be easly validated, parsed and then translated into some target query language such as SPARQL or SQL for processing. See more... | ||||
| OGC GeoPackage Extension for Tiled Gridded Coverage Data |
1.0 | 17-066r1 | Carl Reed | 2018-03-07 |
| The “GeoPackage Extension for Tiled Gridded Coverage Data” extension (previously titled Elevation Extension)" defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. In the ISO 19123 Schema for Coverage Geometry standard and in the OGC Coverage Implementation Schema, this type of regular gridded data is classed as grid-regular[1]. The tiles contain values, such as elevation, temperature or pressure, and may be stored as 16-bit PNG files or 32-bit TIFF files. The extension defines two ancillary data tables: one for regular gridded coverages and one for tiles. When using the PNG encoding, a scale and offset may be applied. The extension also allows for a TIFF encoding but constrains many of the TIFF options that are available to simplify development. See more... | ||||
| OGC GeoPackage Related Tables Extension |
1.0 | 18-000 | Jeff Yutzler | 2019-05-08 |
| A GeoPackage [geopackage] is a platform-independent SQLite [sqlite] database file that contains GeoPackage data and metadata tables. GeoPackages, as described by the GeoPackage Encoding Standard [GPKG1_2] are designed to be extensible, including support for additional data types. This document defines the Related Tables Extension (RTE) for the GeoPackage Encoding Standard.
The RTE defines the rules and requirements for creating relationships in a GeoPackage data store between geospatial data tables and other tables that contain or reference related content such as attributes or media. Geospatial data tables (such as features or tiles tables) contain location information and/or geometries. There are many examples of where the RTE can be used including relating parcel (land lot) features to pictures of that parcel or linking census boundaries to the related demographic census data. See more... | ||||
| OGC Geoscience Markup Language 4.1 (GeoSciML) |
4.1 | 16-008 | GeoSciML Modeling Team | 2017-01-31 |
| GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios.
The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases.
See more... | ||||
| OGC Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum |
4.1.1 | 16-008r1 | eoSciML Modeling Team | 2017-01-31 |
| GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios.
The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases.
See more... | ||||
| OGC GeoSPARQL - A Geographic Query Language for RDF Data |
1.0 | 11-052r4 | Matthew Perry and John Herring | 2012-06-12 |
| This standard defines a set of SPARQL extension functions [W3C SPARQL], a set of RIF rules [W3C RIF Core], and a core RDF/OWL vocabulary for geographic information based on the General Feature Model, Simple Features [ISO 19125-1], Feature Geometry and SQL MM. See more... | ||||
| OGC GeoTIFF Standard |
1.1 | 19-008r4 | Emmanuel Devys, Ted Habermann, Chuck Heazel, Roger Lott, Even Rouault | 2019-09-14 |
| This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset. See more... | ||||
| OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile |
1.0 | 16-060r2 | Daniel Lee | 2018-11-27 |
| This OGC standard is a profile of the OGC GML Application Schema - Coverages version 1.0 [OC 09-146r2]. That document was renamed "OGC Coverage Implementation Schema (CIS)" for clarification in version 1.1. This standard specifies the usage of the GRIB2 data format for the encoding of OGC coverages. The GRIB2 specification is maintained by the World Meteorological Organization (WMO) and is the standard encoding for the exchange and storage of general regularly distributed information expressed in binary form. See more... | ||||
| OGC GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core |
2.0.1 | 08-085r5 | Lucio Colaiacomo, Joan Masó, Emmanuel Devys | 2016-04-07 |
| This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.
This document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000.
See more... | ||||
| OGC Hierarchical Data Format Version 5 (HDF5®) Core Standard |
1.0 | 18-043r3 | Aleksandar Jelenak, Ted Habermann, Gerd Heber | 2019-10-28 |
| Hierarchical Data Format Version 5 (HDF5®) is a data model, a programming interface, and a storage model for keeping and managing data. It supports an unlimited variety of data types, and is designed to be flexible and efficient for large and complex data. HDF5 is extensible via customizing data types, allowing communities and their applications to evolve in the use of HDF5.
This document describes the HDF5 data model as an encoding standard particularly suitable to scientific and engineering geospatial applications that employ multidimensional numeric arrays to describe temporally and spatially varying phenomena. The data model is simple yet versatile, capable of supporting complex data relationships and dependencies through its grouping and linking mechanisms. It is also self-describing by accommodating user-defined metadata. See more... | ||||
| OGC I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 csw-ebrim-i15 |
1.0 | 13-084r2 | Uwe Voges, Frédéric Houbie, Nicolas Lesage, Marie-Lise Vautier | 2014-04-28 |
| The OGC Catalogue Services 2.0 specification (OGC 07-006r1) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains.
The ebRIM application profile (OGC 07-110r4) is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. The ebRIM application profile also includes a Basic extension package (OGC 07-144r4) of the OASIS ebXML Registry Information Model (ebRIM) providing artefacts of general utility in the geomatics domain.
This document provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of ISO 19115, ISO19115-2 and ISO 19119 compliant metadata. It was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [HMA] and related projects. Some input came from the OGC OWS9 initiative.
This document supersedes the former document OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W, OGC 07-038r3 (Version: 0.1.12).
See more... | ||||
| OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard |
1.0 | 16-100r2 | Paul Scarponcini | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 0 addresses the Core Requirements Class from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard |
1.0 | 16-101r2 | Paul Scarponcini | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 1 addresses the LandFeature Requirements Class from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard |
1.0 | 16-102r2 | Paul Scarponcini | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 2 addresses the Facility and Project Requirements Classes from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 3 - Alignments - Encoding Standard |
1.0 | 16-103r2 | Paul Scarponcini | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 3 addresses the Alignment Requirements Class from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard |
1.0 | 16-104r2 | Paul Scarponcini | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 4 addresses the Road and RoadCrossSection Requirements Class from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 5 - Railways - Encoding Standard |
1.0 | 16-105r2 | Peter Axelsson, Lars Wikström | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 5 addresses the Railway Requirements Class from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard |
1.0 | 16-106r2 | Hans-Christoph Gruler | 2017-08-16 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 6 addresses the Survey, Equipment, Observations and Survey Results Requirements Classes from LandInfra. See more... | ||||
| OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard |
1.0 | 16-107r2 | Paul Scarponcini | 2017-09-22 |
| This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
InfraGML is published as a multi-part standard. This Part 7 addresses the LandDivision and Condominium Requirements Classes from LandInfra.
See more... | ||||
| OGC KML |
2.2.0 | 07-147r2 | Tim Wilson | 2008-04-14 |
| KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user's navigation in the sense of where to go and where to look. See more... | ||||
| OGC KML 2.3 |
1.0 | 12-007r2 | David Burggraf | 2015-08-04 |
| KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.
The KML community is wide and varied. Casual users create KML Placemarks to identify their homes, describe journeys, and plan cross-country hikes and cycling ventures. Scientists use KML to provide detailed mappings of resources, models, and trends such as volcanic eruptions, weather patterns, earthquake activity, and mineral deposits. Real estate professionals, architects, and city development agencies use KML to propose construction and visualize plans. Students and teachers use KML to explore people, places, and events, both historic and current. Organizations such as National Geographic, UNESCO, and the Smithsonian have all used KML to display their rich sets of global data.
KML documents and their related images (if any) may be compressed using the ZIP format into KMZ archives. KML documents and KMZ archives may be shared by e‑mail, hosted locally for sharing within a private internet, or hosted on a web server. See more... | ||||
| OGC Location Services (OpenLS): Tracking Service Interface Standard |
1.0.0 | 06-024r4 | CS Smyth | 2008-09-08 |
| The OpenGIS Tracking Service Interface Standard supports a very simple functionality allowing a collection of movable objects to be tracked as they move and change orientation. The standard addresses the absolute minimum in functionality in order to address the need for a simple, robust, and easy-to-implement open standard for geospatial tracking. See more... | ||||
| OGC Moving Features Access |
1.0 | 16-120r3 | Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru | 2017-03-12 |
| This document defines Moving Features Access, i.e., access methods to moving feature data for retrieving feature attributes, information on a relation between a trajectory object and one or more geometry objects, and information on a relation between two trajectory objects from a database storing trajectory data of moving features.
Abstract methods of accessing moving features data are defined in ISO 19141:2008 (Geographic information - Schema for moving features) [ISO 19141:2008]. However, the methods are insufficient to access a database storing moving feature data from multiple sources. If implementations for access to moving features data using various programming languages or protocols (e.g., SQL, Java, and HTTP) are developed without any standards, these implementations might be inconsistent with each other, resulting in poor interoperability. Therefore, methods to access a database storing moving feature data are necessary to improve interoperability.
Applications using moving feature data, typically representing vehicles or pedestrians, are rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create greater social and business value. Moreover, systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications.
Moving Features Access ensures better data exchange by handling and integrating moving feature data to broaden the market for geo-spatial information such as Geospatial Big Data Analysis. OGC 14-083r2 (OGC® Moving Features Encoding Part I: XML Core) [OGC 14-083r2] and OGC 14-084r2 (OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)) [OGC 14-084r2] are existing implementation standards. Moving Features Access uses these standards to encode moving features. See more... | ||||
| OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 |
1.0 | 10-090r3 | Ben Domenico | 2011-04-05 |
| This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena.
NetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data.
See more... | ||||
| OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard netcdf-enhanced |
1.0 | 11-038R2 | Ben Domenico | 2012-10-02 |
| This standard deals with enhancements to the netCDF (Network Common Data Form) data model for array-oriented scientific data..
Two important data models for netCDF are:
- the “classic” netCDF model, used for netCDF-3 and earlier versions
- an enhanced data model, used in netCDF-4 and later versions.
The netCDF classic data model is defined in OGC 10-091r3, “NetCDF Core.”
This document specifies a netCDF extension standard for the enhanced data model. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena.
NetCDF (network Common Data Form) is a data model for array-oriented scientific data. The netCDF classic data model is specified in the netCDF core specification. This standard specifies the enhanced data model. A freely distributed collection of access libraries implementing support for that data model in a machine-independent format are available. Together, the interfaces, libraries, and format support the creation, access, and sharing of multi-dimensional scientific data. See more... | ||||
| OGC Open Modelling Interface Interface Standard |
2.0 | 11-014r3 | Stanislav Vanecek, Roger Moore | 2014-05-26 |
| <p>The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation.
</p>
<p>
This document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-‐compliant components are provided by the OpenMI Association and third-‐party software vendors – visit www.openmi.org for further documentation.</p>
<p>
<a href="https://portal.opengeospatial.org/files/?artifact_id=59022">pdf</a> <br>
<a href="https://portal.opengeospatial.org/files/?artifact_id=59022&format=docx">...
</p> See more... | ||||
| OGC OWS Context Atom Encoding Standard |
1.0 | 12-084r2 | Roger Brackin, Pedro Gonçalves | 2014-01-14 |
| This standard describes the Atom encoding of the OWC Context conceptual model. The goal of this standard is to provide a definition of how to encode a context document, which can be extended to allow a context referencing a fully configured service set to be defined and consistently interpreted by clients.
See more... | ||||
| OGC OWS Context Conceptual Model |
1.0 | 12-080r2 | Roger Brackin, Pedro Gonçalves | 2014-01-22 |
| This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard.
The OGC Web Services Context Document (OWS Context) was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is developed to support in-line content as well. The goal is to support use cases such as the distribution of search results, the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes.
OWS Context is aimed at replacing previous OGC attempts at providing such a capability (the Web Map Context WMC) which was reasonably successful but limited to WMS. Other work on the ‘Location Organizer Folder (LOF)’ was also taken into consideration. The concept of OWS Context, and the first prototype document was produced as part of OGC testbed OWS-7. See OGC 10-035r1, Information Sharing Engineering Report. In order to achieve mass market appeal, as well as being useful to a wider community, the use of OWS Context support to other existing standards was considered. Multiple encoding formats for OWS Context have been developed (ATOM, JSON). Each of these is described in a separate OWS Context Extensions to the Core model.
This document concentrates on describing the OWS Context Model in abstract terms using UML. The document defines requirements and use cases. It also includes an abstract test suite to verify that encodings are compliant with the core specification. The intent of OWS Context is to allow many types of OGC Data Delivery service to be referenced and therefore exploited (for example, not just WMS but also WFS, WCS and WPS) but it does not explicitly define the encoding of these services in the core (only the general approach to be used for different types of service interface). Service explicit encodings are defined within the extension documents for ATOM and JSON.
The abbreviation owc is used throughout this document for OWS Context.
See more... | ||||
| OGC OWS Context GeoJSON Encoding Standard |
1.0 | 14-055r2 | Pedro Gonçalves, Roger Brackin | 2017-04-07 |
| This standard describes the GeoJSON encoding of the OGC Web Services (OWS) Context conceptual model. This standard defines how to encode an OWS context document that 1.) can be extended to allow a context referencing a fully configured service set, and 2.) can be defined and consistently interpreted by clients.
The OWS Context Document standard (OWS Context) was created to allow a set of configured information resources to be passed between applications primarily as a collection of services (but also potentially in-line content). The objective is to support use cases such as the distribution of search results, the exchange of a set of resources in a Common Operating Picture (COP), or delivery of a set of configured processing services to allow the processing to be reproduced on different processing nodes.
The goal for OWS Context is to replace previous OGC standards and best practices that provide similar capability. Web Map Context (WMC) has been reasonably successful but is limited to working with only Web Map Service (WMS) instances. Other work on the Location Organizer Folder1 (LOF) was also taken into consideration. The concept of OWS Context and the first prototype document was produced as part of OWS Testbed 7 and documented in [OGC10-035r1], Information Sharing Engineering Report.
A principal goal of the OWS Context SWG was to develop encodings that would appeal for use in mass market applications yet also provide facilities for more advanced uses. OWS-7 originally considered the application of existing encoding standards for OWS Context. The OGC Standards Working Group (SWG) has concluded that this standard can have multiple encoding formats and that each encoding format will be described in a separate OGC Extension to the Core model.
See more... | ||||
| OGC PipelineML Conceptual and Encoding Model Standard |
1.0 | 18-073r2 | John Tisdale | 2019-08-08 |
| The OGC PipelineML Conceptual and Encoding Model Standard defines concepts supporting the interoperable interchange of data pertaining to oil and gas pipeline systems. PipelineML supports the common exchange of oil and gas pipeline information. This initial release of the PipelineML Core addresses two critical business use cases that are specific to the pipeline industry: new construction surveys and pipeline rehabilitation. This standard defines the individual pipeline components with support for lightweight aggregation. Additional aggregation requirements such as right-of-way and land management will utilize the OGC LandInfra standards with utility extensions in the future. Future extensions to PipelineML Core will include (non-limitative): cathodic protection, facility and safety. PipelineML was advanced by an international team of contributors from the US, Canada, Belgium, Norway, Netherlands, UK, Germany, Australia, Brazil, and Korea.
This standard assumes the reader has a basic understanding of oil and gas pipeline industry concepts. See more... | ||||
| OGC SensorThings API Part 1: Sensing |
1.0 | 15-078r6 | Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi | 2016-07-26 |
| The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part is planned as a future work activity and will be defined in a separate document as the Part II of the SensorThings API. See more... | ||||
| OGC SensorThings API Part 2 – Tasking Core |
1.0 | 17-079r1 | Steve Liang, Tania Khalafbeigi | 2019-01-08 |
| The OGC SensorThings API [OGC 15-078r6] provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level, the OGC SensorThings API provides two main functions and each function is handled by the Sensing part or the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as individual sensors and actuators, composite consumer / commercial / industrial / smart cities in-situ platforms, mobile and wearable devices, or even unmanned systems platforms such as drones, satellites, connected and autonomous vehicles, etc. This document specifies core of the SensorThings Tasking part. See more... | ||||
| OGC TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements |
1.2 | 15-042r5 | James Tomkins and Dominic Lowe | 2018-12-18 |
| TimeseriesML 1.2 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements. See more... | ||||
| OGC Two Dimensional Tile Matrix Set |
1.0 | 17-083r2 | Joan Masó | 2019-10-06 |
| The OGC Tile Matrix Set 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 limited list of scales in a Coordinate Reference System (CRS) as defined in [OGC 08-015r2] Abstract Specification Topic 2: Spatial Referencing by Coordinates. Each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column a tile row and a tile matrix identifier. This document presents a data structure defining the properties of the tile matrix set in both UML diagrams and in tabular form. This document also presents a data structure to define a subset of a tile matrix set called tile matrix set limits. XML and JSON encodings are suggested both for tile matrix sets and tile matrix set limits. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions. See more... | ||||
| OGC WaterML2.0: part 2 - Ratings, Gaugings and Sections |
1.0 | 15-018r2 | Peter Taylor | 2016-02-03 |
| This standard defines an information model and XML encoding for exchanging the
following three hydrological information resources:
1. Conversion tables, or conversion curves, that are used for the conversion of
related hydrological phenomenon.
2. Gauging observations – the observations performed to develop conversion table
relationships.
3. Cross sections - survey observations made of the geometric structure of features,
such as river channels, storages etc.
Metadata and vocabularies are defined that together provide a means for parties to
exchange these concepts using common semantics.
This standard is the second part of the WaterML2.0 suite of standards, building on part 1
that addresses the exchange of time series.
See more... | ||||
| OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2) |
2.2 | 16-032r2 | Boyan Brodaric | 2017-03-06 |
| This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples. See more... | ||||
| OGC Web Coverage Service (WCS) 2.1 Interface Standard - Core |
2.1 | 17-089r1 | Peter Baumann | 2018-08-16 |
| The OGC Web Coverage Service (WCS) supports electronic retrieval of geospatial data as "coverages." Coverages are digital geospatial information representing space/time-varying phenomena, specifically spatio-temporal regular and irregular grids, point clouds, and general meshes.
This document specifies the WCS core. Every implementation of a WCS shall adhere to this standard. This standard defines core requirements. Extensions to the core define extensions to meet additional requirements, such as the response encoding. Additional extensions are required in order to completely specify a WCS for implementation.
This WCS 2.1 standard extends WCS 2.0 in a backwards compatible manner by accommodating coverages as per the OGC Coverage Implementation Schema (CIS) 1.1 in addition to CIS 1.0 coverages as addressed by WCS 2.0.
See more... | ||||
| OGC Web Coverage Service Interface Standard – Transaction Extension |
2.0 | 13-057r1 | Peter Baumann | 2016-11-17 |
| This OGC Web Coverage Service (WCS) – Transaction Extension (in short: WCS Transaction) defines an extension to the WCS Core [OGC 09-110] for updating coverage offerings on a server.
This WCS Transaction standard defines three requests:
InsertCoverage for adding a coverage provided as parameter to the WCS server’s coverage offering. After successful completion of the insert request, this coverage will be accessible for all WCS operations.
DeleteCoverage for entirely removing a coverage. The coverage is identified by its coverage id passed in the request, from the WCS server’s coverage offering. After successful completion of this request, this coverage will not be accessible through any WCS operation. However, subsequently a new coverage may be created using the same identifier; such a coverage will bear no relation to the one previously deleted.
UpdateCoverage for modifying parts of a coverage existing in a WCS server’s coverage offering. The coverage is identified by its coverage id passed in the request. As per the OGC Coverage Implementation Schema [OGC 09-146r2], all updates must maintain internal consistency of the coverage.
All requests defined in this Transaction Extension adhere to the ACID[1] (atomicity, consistency, isolation, durability) concepts of database transactions.
The extension name, Transaction, traces back to the database concept of transactions, which has been adopted here. See more... | ||||
| OGC Web Feature Service Implementation Specification with Corrigendum |
1.1.3 | 04-094r1 | Panagiotis A. Vretanos | 2016-10-26 |
| The OGC Web Map Service allows a client to overlay map images for display served from multiple Web Map Services on the Internet. In a similar fashion, the OGC Web Feature Service allows a client to retrieve and update geospatial data encoded in Geography Markup Language (GML) from multiple Web Feature Services.
The requirements for a Web Feature Service are:
The interfaces must be defined in XML.
GML must be used to express features within the interface.
At a minimum a WFS must be able to present features using GML.
The predicate or filter language will be defined in XML and be derived from CQL as defined in the OpenGIS Catalogue Interface Implementation Specification.
The datastore used to store geographic features should be opaque to client applications and their only view of the data should be through the WFS interface.
The use of a subset of XPath expressions for referencing properties.
See more... | ||||
| OGC Web Service Common Implementation Specification |
2.0.0 | 06-121r9 | Arliss Whiteside Jim Greenwood | 2010-04-07 |
| This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. See more... | ||||
| OGC Web Services Security |
1.0 | 17-007r1 | Andreas Matheus | 2019-01-28 |
| This standard applies to a deployed OGC Web Service instance for which the protocol scheme of all operation endpoint URLs, exposed in the Capabilities document, is ‘https’ as defined in RFC 7230, section 2.7.2.
A security-annotated Capabilities document is one which uses the <Constraint> element(s) to express the existence of security controls on the operation of the service instance or support for a particular security feature. Applying the tests as defined in the Annexes can validate compliance for a service, the client and the OGC management process. Basically, a service can be described by a Capabilities document that includes security annotations as defined in this standard. A client loading these Capabilities and parse for the <Constraint> element(s) can determine the security controls implemented for each operation of the service instance. The string value of this element’s name attribute contains the identifier of the implemented requirements class.
How the client obtains the security-annotated capabilities is out of scope for this standard.
This standard defines one common abstract Requirements Class and three Capabilities document structure specific Requirements Classes. The structure specific classes address how the requirements are implemented for WMS 1.1.1, WMS 1.3 and OWS Common based service Capabilities documents.
See more... | ||||
| OGC® 3D Portrayal Service 1.0 |
1.0 | 15-001r4 | Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell | 2017-09-13 |
| The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal.
It does not define or endorse particular content transmission formats, but specifies how geospatial 3D content is described, selected, and delivered. It does not prescribe how aforementioned content is to be organized and represented, but provides a framework to determine whether 3D content is interoperable at the content representation level. More details are available in Design of this standard. See more... | ||||
| OGC®: Open GeoSMS Standard - Core |
1.0 | 11-030r1 | Kuan-Mei Chen, Carl Reed | 2012-01-19 |
| The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS). See more... | ||||
| OGC® Catalogue Services 3.0 - General Model |
3.0 | 12-168r6 | Douglas Nebert, Uwe Voges, Lorenzo Bigagli | 2016-06-10 |
| OGC® Catalogue Services support the ability to publish and search collections of
descriptive information (metadata records) for geospatial data, services, and related
information. Metadata in catalogues represent resource characteristics that can be queried
and presented for evaluation and further processing by both humans and software.
Catalogue services are required to support the discovery and binding to registered
information resources within an information community.
This part of the Catalogue Services standard describes the common architecture for OGC
Catalogue Services. This document abstractly specifies the interfaces between clients and
catalogue services, through the presentation of abstract models. This common
architecture is Distributed Computing Platform neutral and uses UML notation. Separate
(Part) documents specify the protocol bindings for these Catalogue services, which build
upon this document, for the HTTP (or CSW) and OpenSearch protocol bindings.
An Abstract Conformance Test Suite is not included in this document. Such Suites shall
be developed by protocol bindings and Application Profiles (see 8.5, ISO/IEC TR 10000-
2:1998) that realize the conformance classes listed herein. An application profile
consists of a set of metadata elements, policies, and guidelines defined for a particular
application1.
OGC document number 14-014r3 – HTTP Protocol Binding – Abstract Test Suite is
available to address conformance with the provisions of OGC document number 12-
176r7 – HTTP Protocol Binding. All annexes to this document are informative. See more... | ||||
| OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding |
3.0 | 12-176r7 | Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott | 2016-06-10 |
| This document specifies the HTTP profile of the CSW General Model part (see OGC 12-
168r6). The General Model specifies the abstract interfaces between clients and catalogue
services. This standard specifies the mappingof the Catalogue abstract model interface
into the HTTP protocol binding.
In this HTTP protocol binding, operation requests and responses are sent between clients
and servers using the HTTP GET and/or HTTP POST methods. Two equivalent request
encodings are defined in this standard. The first using keyword-value pairs (KVP)
which is suitable for use with the HTTP GET method. The second using XML which is
suitable for use with the HTTP POST method.
This standard defines operations that allow a client to get a service description document
for the catalogue (i.e. GetCapabilities); operations that allow a client to, at runtime,
interrogate the service about the kinds of data available (i.e. GetDomain); operations that
allow a client to retrieve records from the catalogue (i.e. GetRecordById and
GetRecords); operations that allow a client to add, modify and remove records from the
catalogue service (i.e. Transaction, Harvest, UnHarvest). See more... | ||||
| OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products |
1.0.0 | 06-131r6 | Frédéric Houbie, Lorenzo Bigagli | 2010-02-10 |
| This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management. See more... | ||||
| OGC® CF-netCDF 3.0 encoding using GML Coverage Application Schema |
2.0 | 14-100r2 | Ben Domenico, Stefano Nativi | 2015-11-18 |
| The OGC CF-netCDF data model supports multi-dimensional gridded data and multidimensional multi-point data, representing space and time-varying phenomena. In particular, this extension standard is limited to multi-point, and regular and warped grids.
This standard specifies the CF-netCDF data model encoding using the OGC GML 3.2.1 coverage application schema, as well as CF-netCDF data exchange format and protocol encoding.
This standard specifies: (a) the CF-netCDF GML encoding to be used by OGC standards; (b) the CF-netCDF data format exchanged using OGC standards; (c) the Internet protocol characteristics to effectively exchange CF-netCDF data.
As per the GML 3.3. standard, GML 3.3 imports the 3.2 schema. The canonical location of the 3.2 all components schema document for 3.3 is
http://schemas.opengis.net/gml/3.2.1/gml.xsd See more... | ||||
| OGC® Earth Observation Metadata profile of Observations & Measurements |
1.1 | 10-157r4 | Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders | 2016-06-09 |
| This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156:2010 and OGC 10-025r1) for describing Earth Observation products (EO products).
This profile is intended to provide a standard schema for encoding Earth Observation product metadata to support the description and cataloguing of products from sensors aboard EO satellites.
The metadata being defined in this document is applicable in a number of places where EO product metadata is needed.
1. In the EO Product Extension Package for ebRIM (OGC 10-189). This extension package defines how to catalog Earth Observation product metadata described by this document. Using this metadata model and the Catalogue Service defined in OGC 10-189, client applications can provide the functionality to discover EO Products. Providing an efficient encoding for EO Product metadata cataloguing and discovery is the prime purpose of this specification.
2. In the EO Application Profile of WMS (OGC 07-063r1). The GetFeatureInfo operation on the outline (footprint layer) should return metadata following the Earth Observation Metadata profile of Observation and Measurements.
3. In a coverage downloaded via an EO WCS AP (OGC 10-140). In WCS 2.0 (OGC 10-084), the GetCoverage and DescribeCoverage response contains the metadata element intended to store metadata information about the coverage. The Earth Observation Application profile of WCS (OGC 10-140) specifies that the metadata format preferred for Earth Observation is defined by this document.
4. Potentially enclosed within an actual product to describe georeferencing information as for instance within the JPEG2000 format using GMLJP2. GMLJP2 defines how to store GML coverage metadata inside a JP2 file.
Earth Observation data products are generally managed within logical collections that are usually structured to contain data items derived from sensors onboard a satellite or series of satellites. The key characteristics differentiating products within the collections are date of acquisition, location as well as characteristics depending on the type of sensor, For example, key characteristics for optical imagery are the possible presence of cloud, haze, smokes or other atmospheric or on ground phenomena obscuring the image.
The common metadata used to distinguish EO products types are presented in this document for generic and thematic EO products (i.e optical, radar, atmospheric, altimetry, limb-looking and synthesis and systematic products). From these metadata the encodings are derived according to standard schemas. In addition, this document describes the mechanism used to extend these schemas to specific missions and for specific purposes such as long term data preservation.
See more... | ||||
| OGC® Geography Markup Language (GML) - Extended schemas and encoding rules |
3.3 | 10-129r1 | Clemens Portele | 2012-02-07 |
| The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. See more... | ||||
| OGC® GeoPackage Encoding Standard |
1.0 | 12-128r10 | Paul Daisey | 2014-02-10 |
| This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a "native" storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth.
<br /><br />
For the online version of the standard and the developer resources, visit <a href="http://www.geopackage.org/">http://www.geopackage.org/</a> See more... | ||||
| OGC® GeoPackage Encoding Standard |
1.1 | 12-128r12 | Jeff Yutzler | 2015-08-04 |
| This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector
geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access
and update data in a "native" storage format without intermediate format translations in an environment (e.g. through an API) that
guarantees data model and data set integrity and identical access and update results in response to identical requests from different
client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly
useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. See more... | ||||
| OGC® GeoPackage Encoding Standard |
1.2 | 12-128r14 | Jeff Yutzler | 2017-08-25 |
| This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a "native" storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. See more... | ||||
| OGC® GeoPackage Encoding Standard - With Corrigendum |
1.0.1 | 12-128r12 | Paul Daisey | 2015-04-20 |
| This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. See more... | ||||
| OGC® GeoPackage Encoding Standard - with Corrigendum |
1.2.1 | 12-128r15 | Jeff Yutzler | 2018-09-06 |
| This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a "native" storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. See more... | ||||
| OGC® Geospatial User Feedback Standard: Conceptual Model |
1.0 | 15-097r1 | Joan Masó and Lucy Bastin | 2016-12-22 |
| This standard defines a conceptual Geospatial User Feedback (GUF) data model. Geospatial User Feedback is metadata that is predominantly produced by the consumers of geospatial data products as they use and gain experience with those products. This standard complements existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher or curator of a data product. As a part of metadata, the GUF data model reuses some elements of ISO 19115-1:2014 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. This standard is designed to be used combination with an encoding standard. Initially an XML encoding following the ISO 19139 encoding rules is specified in a separate OGC implementation standard (OGC 15-098). In the future other encodings may be defined, including examples such as the use of JSON-LD based on parts of schema.org. See more... | ||||
| OGC® Geospatial User Feedback Standard: XML Encoding Extension |
1.0 | 15-098r1 | Joan Masó and Lucy Bastin | 2016-12-22 |
| The Geospatial User Feedback XML encoding standard is based on the OGC Geospatial User Feedback conceptual model [OGC 15-097]. Geospatial User Feedback (GUF) is metadata that is predominantly produced by the consumers of geospatial data products based on their use and experience with those products. This standard complements the existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher, or curator of a data product. As a part of metadata, the GUF data model internally reuses some elements of ISO 19115-1 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models.
This standard can be used in combination with the OGC 15-097 Conceptual Model Standard. In the future, other encodings may be considered, being an alternative using the JSON-LD encoding based on parts of schema.org.
See more... | ||||
| OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile wcs_geotiff |
1.0 | 12-100r1 | Stephan Meissl | 2014-05-28 |
| This Interface Standard is a profile of the OGC® GML Application Schema –Coverages version 1.0 [OC 09-146r2]. This document specifies the usage of the GeoTIFF data format for the encoding of GML coverages. This encoding is used by several OGC services like the Web Coverage Service (WCS) 2.0 Interface Standard – Core [OGC 09-110r4]. See more... | ||||
| OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard |
2.1 | 08-085r8 | Lucio Colaiacomo, Joan Masó, Emmanuel Devys, Eric Hirschorn | 2018-08-27 |
| This OGC GML in JPEG 2000 (GMLJP2) Encoding Standard defines how the OGC/ISO Geography Markup Language (GML) standard is used within JPEG 2000 images and other gridded coverage data for adding geospatial content to imagery. Specifically, this OGC standard defines requirements for the encoding and decoding of JPEG 2000 images and other gridded coverage data that contain XML documents that use GML and GML-based schema.
This document defines the use of GML within the XML boxes of the JP2 and JPX file format for JPEG 2000 (extending the JP2 file format, as specified in [ISO 15444-1] and [ISO 15444-2] in Annexes M and N). Further, an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations is specified. The document also specifies the encoding and packaging rules for GML use in JPEG 2000.
See more... | ||||
| OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core |
2.0 | 08-085r4 | Lucio Colaiacomo, Joan Masó, Emmanuel Devys | 2014-09-23 |
| This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.
This document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. See more... | ||||
| OGC® IndoorGML |
1.0 | 14-005r3 | Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker | 2014-12-02 |
| This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. See more... | ||||
| OGC® Land and Infrastructure Conceptual Model Standard (LandInfra) |
1.0 | 15-111r1 | Paul Scarponcini | 2016-12-20 |
| This OGC Land and Infrastructure Conceptual Model Standard presents the implementation-independent concepts supporting land and civil engineering infrastructure facilities. Conceptual model subject areas include facilities, projects, alignment, road, rail, survey, land features, land division, and wet infrastructure (storm drainage, wastewater, and water distribution systems). The initial release of this standard includes all of these subject areas except wet infrastructure, which is anticipated to be released as a future extension.
This standard assumes the reader has a basic understanding of surveying and civil engineering concepts.
See more... | ||||
| OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV) |
1.0 | 14-084r2 | Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf | 2015-02-17 |
| This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. See more... | ||||
| OGC® Moving Features Encoding Part I: XML Core |
1.0 | 14-083r2 | Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf | 2015-02-17 |
| This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. See more... | ||||
| OGC® Moving Features Encoding Part I: XML Core |
1.0.2 | 18-075 | Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf | 2019-01-14 |
| This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. See more... | ||||
| OGC® OpenSearch Extension for Earth Observation |
1.0 | 13-026r8 | Pedro Gonçalves, Uwe Voges | 2016-12-16 |
| This document is the specification for the OpenSearch extension for Earth Observation collections and products search.
This standard is intended to provide a very simple way to make queries to a repository that contains Earth Observation information and to allow syndication of repositories. See more... | ||||
| OGC® OpenSearch Geo and Time Extensions |
1.0 | 10-032r8 | Pedro Gonçalves | 2014-04-14 |
| <p>This OGC standard specifies the Geo and Time extensions to the OpenSearch query protocol. OpenSearch is a collection of simple formats for the sharing of search results.</p>
<p>The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch description format allows the use of extensions that allow search engines to request a specific and contextual query parameter from search clients.</p>
<p>The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results.
Services that support the OpenSearch Specification, the Geo and Time extensions defined in this document are called OpenSearch GeoTemporal Services.</p>
See more... | ||||
| OGC® Publish/Subscribe Interface Standard 1.0 - Core |
1.0 | 13-131r1 | Aaron Braeckel , Lorenzo Bigagli , Johannes Echterhoff | 2016-08-22 |
| Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern specified by many existing OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to interested Subscribers.
Publish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore, OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate.
This specification defines Publish/Subscribe functionality independently of the binding technology (e.g., KVP, SOAP, REST). Extensions to this specification may realize these core concepts with specific binding technologies. See more... | ||||
| OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension |
1.0 | 13-133r1 | Aaron Braeckel, Lorenzo Bigagli | 2016-08-22 |
| Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers.
Publish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate.
This specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol. See more... | ||||
| OGC® PUCK Protocol Standard |
1.4 | 09-127r2 | Tom O’Reilly | 2012-01-25 |
| This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself. See more... | ||||
| OGC® SensorML: Model and XML Encoding Standard |
2.0 | 12-000 | Mike Botts, Alexandre Robin | 2014-02-04 |
| The primary focus of the Sensor Model Language (SensorML) is to provide a robust and
semantically-tied means of defining processes and processing components associated
with the measurement and post-measurement transformation of observations. This
includes sensors and actuators as well as computational processes applied pre- and postmeasurement.
The main objective is to enable interoperability, first at the syntactic level and later at the
semantic level (by using ontologies and semantic mediation), so that sensors and
processes can be better understood by machines, utilized automatically in complex
workflows, and easily shared between intelligent sensor web nodes.
This standard is one of several implementation standards produced under OGC’s Sensor
Web Enablement (SWE) activity. This standard is a revision of content that was
previously integrated in the SensorML version 1.0 standard (OGC 07-000). See more... | ||||
| OGC® Sensor Observation Service Interface Standard |
2.0 | 12-006 | Arne Bröring, Christoph Stasch, Johannes Echterhoff | 2012-04-20 |
| The SOS standard is applicable to use cases in which sensor data needs to be managed in an
interoperable way. This standard defines a Web service interface which allows querying
observations, sensor metadata, as well as representations of observed features. Further, this
standard defines means to register new sensors and to remove existing ones. Also, it defines
operations to insert new sensor observations. This standard defines this functionality in a binding
independent way; two bindings are specified in this document: a KVP binding and a SOAP
binding. See more... | ||||
| OGC® Sensor Planning Service Implementation Standard |
2.0 | 09-000 | Ingo Simonis, Johannes Echterhoff | 2011-03-28 |
| The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. See more... | ||||
| OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking ExtensionOGC® Sensor Planning Service SPS EO Tasking Ext |
2.0 | 10-135 | Alexandre Robin, Philippe Mérigot | 2011-03-28 |
| The SPS 2.0 Earth Observation Satellite Tasking Extension Standard specifies extensions to the OGC Sensor Planning Service (SPS) 2.0 Interface Standard. The SPS configuration proposed in this extension is intended to support the programming process of Earth Observation (EO) sensor systems. This standard describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. The resulting extended web service interface can be used for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or canceling such a request, and for requesting information on means of obtaining the data collected by the requested task. See more... | ||||
| OGC® SWE Common Data Model Encoding Standard |
2.0 | 08-094r1 | Alexandre Robin | 2011-01-04 |
| This standard defines low level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework. These models allow applications and/or servers to structure, encode and transmit sensor datasets in a self describing and semantically enabled way. See more... | ||||
| OGC® WaterML 2.0: Part 1- Timeseries |
2.0.1 | 10-126r4 | Peter Taylor | 2014-02-24 |
| WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document. See more... | ||||
| OGC® WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model |
1.0 | 14-111r6 | David Blodgett, Irina Dornblut | 2018-01-08 |
| The OGC Surface Hydrology Features (HY_Features) standard defines a common conceptual information model for identification of specific hydrologic features independent of their geometric representation and scale. The model describes types of surface hydrologic features by defining fundamental relationships among various components of the hydrosphere. This includes relationships such as hierarchies of catchments, segmentation of rivers and lakes, and the hydrologically determined topological connectivity of features such as catchments and waterbodies. The standard also defines normative requirements for HY_Features implementation schemas and mappings to meet in order to be conformant with the conceptual model.
The HY_Features model is based on an abstract catchment feature type that can have multiple alternate hydrology-specific realizations and geometric representations. It supports referencing information about a hydrologic feature across disparate information systems or products to help improve data integration within and among organizations. The model can be applied to cataloging of observations, model results, or other study information involving hydrologic features. The ability to represent the same catchment, river, or other hydrologic feature in several ways is critical for aggregation of cross-referenced or related features into integrated data sets and data products on global, regional, or basin scales. See more... | ||||
| OGC® WCS 2.0 Interface Standard- Core: Corrigendum |
2.0.1 | 09-110r4 | Peter Baumann | 2012-07-12 |
| This document specifies how a Web Coverage Service (WCS) offers multi-dimensional cov-erage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementa-tion. This document indicates which extensions, at a minimum, need to be considered in ad-dition to this core to allow for a complete WCS implementation.
This core does not prescribe support for any particular coverage encoding format. This also holds for GML as a coverage delivery format: while GML constitutes the canonical format for the definition of WCS, it is not required by this core that a concrete instance of a WCS service implements the GML coverage format. WCS extensions specifying use of data encod-ing formats in the context of WCS are designed in a way that the GML coverage information contents specified in this core is consistent with the contents of an encoded coverage.
See more... | ||||
| OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile |
1.1 | 10-140r2 | Peter Baumann, Stephan Meissl, Jinsongdi Yu | 2018-10-04 |
| The OGC Web Coverage Service (WCS) Application Profile - Earth Observation (EO- WCS) defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data. See more... | ||||
| OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum |
1.0.1 | 09-147r3 | Peter Baumann | 2013-03-26 |
| This document specifies an extension to the OGC Web Coverage Service (WCS) 2.0 core to allow for client/server communication using HTTP GET with key/value pair (KVP) encod-ing. See more... | ||||
| OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension |
1.0.0 | 09-148r1 | Peter Baumann | 2010-10-27 |
| This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding. See more... | ||||
| OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension WCS XML SOAP ext |
2.0 | 09-149r1 | Peter Baumann | 2010-10-27 |
| This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding. See more... | ||||
| OGC® Web Coverage Service Interface Standard - CRS Extension WCS-CRS-extension |
1.0 | 11-053r1 | Peter Baumann, Jinsongdi Yu | 2014-03-11 |
| This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request that allows a client, a service, or other application to specify the Coordinate Reference System (CRS) in which coverages are delivered. Note that the CRS of the input bounding box is already defined in the OGC WCS Core Implementation Standard [OGC 09-110r3]. See more... | ||||
| OGC® Web Coverage Service Interface Standard - Interpolation Extension WCS Interopolation |
1.0 | 12-049 | Peter Baumann, Jinsongdi Yu | 2014-02-26 |
| This OGC standard specifies parameters to the OGC Web Coverage Service (WCS) GetCov-erage request which give control over interpolation of a coverage during its server-side pro-cessing. This allows the client (user) to control and specify the interpolation mechanism to be applied to a coverage during server processing.
This WCS Interpolation extension relies on WCS Core [OGC 09-110r4] and the GML Appli-cation Schema for Coverages [OGC 09-146r2].
See more... | ||||
| OGC® Web Coverage Service Interface Standard - Range Subsetting Extension WCS range subsetting |
1.0 | 12-040 | Peter Baumann, Jinsongdi Yu | 2014-02-26 |
| This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow extraction of specific fields, according to the range type specification, from the range set of a coverage during server-side processing of a coverage in a GetCover-age request. See more... | ||||
| OGC® Web Coverage Service Interface Standard - Scaling Extension WCS scaling |
1.0 | 12-039 | Peter Baumann, Jinsongdi Yu | 2014-02-26 |
| This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow scaling of a coverage during its server-side processing in a GetCoverage request. See more... | ||||
| OGC® Web Coverage Service WCS Interface Standard - Processing Extension WCS WCPS |
2.0 | 08-059r4 | Peter Baumann, Jinsongdi Yu | 2014-02-26 |
| The OGC Web Coverage Service (WCS)– Processing Extension defines an extension to the WCS Core [OGC 09-110], the ProcessCoverages request type, which allows clients to initi-ate server-side processing and filtering of coverages and to download the resulting coverage or value sets based on the query language defined in the Web Coverage Processing Service (WCPS) interface standard [OGC 08-068]. See more... | ||||
| OGC® Web Feature Service 2.0 Interface Standard - With Corrigendum |
2.0.2 | 09-025r2 | Panagiotis (Peter) A. Vretanos | 2014-07-10 |
| The Web Feature Service (WFS) represents a change in the way geographic information is created, modified and exchanged on the Internet. Rather than sharing geographic information at the file level using File Transfer Protocol (FTP), for example, the WFS offers direct fine-grained access to geographic information at the feature and feature property level.
This International Standard specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored, parameterized query expressions.
Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers.
Query operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties.
Locking operations allow exclusive access to features for the purpose of modifying or deleting features.
Transaction operations allow features to be created, changed, replaced and deleted from the underlying data store.
Stored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values.
This International Standard defines eleven operations:
GetCapabilities (discovery operation)
DescribeFeatureType (discovery operation)
GetPropertyValue (query operation)
GetFeature (query operation)
GetFeatureWithLock (query & locking operation)
LockFeature (locking operation)
Transaction (transaction operation)
CreateStoredQuery (stored query operation)
DropStoredQuery (stored query operation)
ListStoredQueries (stored query operation)
DescribeStoredQueries (stored query operation)
In the taxonomy of services defined in ISO 19119, the WFS is primarily a feature access service but also includes elements of a feature type service, a coordinate conversion/transformation service and geographic format conversion service. See more... | ||||
| OGC® WPS 2.0 Interface Standard |
2.0.0 | 14-065 | Matthias Mueller | 2015-03-05 |
| See more... | ||||
| OGC® WPS 2.0.1 Interface Standard: Corrigendum 1 |
2.0.1 | 14-065r1 | Matthias Mueller | 2015-10-05 |
| In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment.
The WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment.
See more... | ||||
| OGC® WPS 2.0.2 Interface Standard: Corrigendum 2 |
2.0.2 | 14-065r2 | Matthias Mueller | 2018-02-16 |
| In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment.
The WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment.
See more... | ||||
| OpenGIS Catalogue Service Implementation Specification |
2.0.2 | 07-006r1 | Nebert, Whiteside, Vretanos, editors | 2007-04-20 |
| The OpenGIS® Catalogue Services Interface Standard (CAT) supports the ability to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. Providers of resources use catalogues to register metadata that conform to the provider's choice of an information model; such models include descriptions of spatial references and thematic information. Client applications can then search for geospatial data and services in very efficient ways.
See also the OGC Catalogue 2.0 Accessibility for OWS-3 Discussion Paper [http://www.opengeospatial.org/standards/dp], the OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) [www.opengeospatial.org/standards/dp] and the OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW (Best Practice) [http://www.opengeospatial.org/standards/bp].
See more... | ||||
| OpenGIS Coordinate Transformation Service Implementation Specification |
1.0 | 01-009 | Martin Daly | 2001-01-12 |
| The OpenGIS® Coordinate Transformation Service Standard (CTS) provides a standard way for software to specify and access coordinate transformation services for use on specified spatial data. This standard addresses a key requirement for overlaying views of geodata (“maps”) from diverse sources: the ability to perform coordinate transformation in such a way that all spatial data are defined relative to the same spatial reference system. See more... | ||||
| OpenGIS Filter Encoding 2.0 Encoding Standard |
2.0 | 09-026r1 | Panagiotis (Peter) A. Vretanos | 2010-11-22 |
| This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression.
These components are modular and intended to be used together or individually by other standards which reference this International Standard. See more... | ||||
| OpenGIS Geography Markup Language (GML) Encoding Standard |
3.2.1 | 07-036 | Clemens Portele | 2007-10-05 |
| The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data.
A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it.
Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber... ].
See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .
See more... | ||||
| OpenGIS Geography Markup Language (GML) Encoding Standard - with corrigendum |
3.2.2 | 07-036r1 | Clemens Portele | 2018-04-14 |
| The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data.
A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it.
Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber... ].
See more... | ||||
| OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification |
1.0.0 | 05-047r3 | Martin Kyle, David Burggraf, Sean Forde, Ron Lake | 2006-01-20 |
| The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard http://www.opengeospatial.org/standards/gml is used within JPEG 2000 http://www.jpeg.org/jpeg2000/ images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file.
See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .
See more... | ||||
| OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture |
1.2.1 | 06-103r4 | John Herring | 2011-05-28 |
| The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. See more... | ||||
| OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option |
1.2.1 | 06-104r4 | John Herring | 2010-08-04 |
| The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. See more... | ||||
| OpenGIS Location Service (OpenLS) Implementation Specification: Core Services |
1.2.0 | 07-074 | Marwa Mabrouk | 2008-09-08 |
| This OpenGIS Interface Standard defines OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. See more... | ||||
| OpenGIS Location Services (OpenLS): Part 6 - Navigation Service OLSNav |
1.0.0 | 08-028r7 | Gil Fuchs | 2008-09-04 |
| This OpenGIS Implementation Standard defines the interfaces for OpenGIS Location Services (OpenLS): Part 6 - Navigation Service (formerly the Full Profile of the Route Determination Service), which is part of the GeoMobility Server (GMS), an open location services platform. See more... | ||||
| OpenGIS SensorML Encoding Standard v 1.0 Schema Corregendum 1 SensorML Corr 1 |
1.01 | 07-122r2 | Mike Botts, Simon Cox | 2007-11-12 |
| Changes to the 1.0 schemas See more... | ||||
| OpenGIS Sensor Model Language (SensorML) |
1.0.0 | 07-000 | Mike Botts | 2007-07-24 |
| The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. For additional information on SensorML, see http://www.botts-inc.net/vast.html
<!-- http://vast.uah.edu/SensorML.--> See more... | ||||
| OpenGIS Sensor Observation Service |
1.0.0 | 06-009r6 | Arthur Na, Mark Priest | 2008-02-13 |
| The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. See more... | ||||
| OpenGIS Simple Features Implementation Specification for CORBA |
1.0 | 99-054 | Peter Ladstaetter | 1999-06-02 |
| The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). See more... | ||||
| OpenGIS Simple Features Implementation Specification for OLE/COM |
1.1 | 99-050 | TC Chair | 1999-05-18 |
| The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). See more... | ||||
| OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification |
1.1.0 | 05-078r4 | Markus Lupp | 2007-08-14 |
| The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f] and coverage[http://www.opengeospatial.org/ogc/glossary/c] data.
SLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. The OpenGIS® Symbology Encoding Standard (SE) [http://www.opengeospatial.org/standards/symbol] provides this language, while the SLD profile of WMS enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols.
See more... | ||||
| OpenGIS Symbology Encoding Implementation Specification |
1.1.0 | 05-077r4 | Dr. Markus Mueller | 2007-01-18 |
| The OpenGIS® Symbology Encoding Standard (SES) defines an XML language for styling information that can be applied to digital geographic feature and coverage data. SE is independent of any OGC Web Services descriptions and could therefore be used to describe styling information in non-networked systems such as desktop geographic information systems. See more... | ||||
| OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard |
1.0.0 | 08-068r2 | Peter Baumann | 2009-03-25 |
| The OGC® Web Coverage Processing Service (WCPS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional coverages representing sensor, image, or statistics data. See more... | ||||
| OpenGIS Web Coverage Service (WCS) - Processing Extension (WCPS) WCS WCPS |
1.0.0 | 08-059r3 | Peter Baumann | 2009-03-25 |
| The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional gridded [[http://www.opengeospatial.org/ogc/glossary/c | coverages]] representing sensor, image, or statistics data. Services implementing this language provide access to original or derived sets of geospatial coverage information, in forms that are useful for client-side rendering, input into scientific models, and other client applications.
Further information about WPCS can be found at the [[http://www.ogcnetwork.net/wcps | WCPS Service]] page of the OGC Network. See more... | ||||
| OpenGIS Web Feature Service (WFS) Implementation Specification |
1.1.0 | 04-094 | Peter Vretanos | 2005-05-03 |
| The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including:
• Get or Query features based on spatial and non-spatial constraints
• Create a new feature instance
• Get a description of the properties of features
• Delete a feature instance
• Update a feature instance
• Lock a feature instance
The specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used.
See more... | ||||
| OpenGIS Web Feature Service (WFS) Implementation Specification (Corrigendum) WFSC |
1.0.0 | 06-027r1 | Panagiotis (Peter) A. Vretanos | 2006-08-22 |
| This document is a corrigendum for OGC Document 04-094. Specifically, this document corrects the files referenced in ANNEX A and found in the OGC schema repository. See more... | ||||
| OpenGIS Web Map Context Documents Corrigendum 1 WMC Corr 1 |
1.1.0 | 08-050 | Tom Kralidis | 2008-05-02 |
| This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Map Context Documents version 1.1.0 and does not modify that standard. The current OpenGIS IS that this document provides revision notes for is 05-005. This document is a corrigendum to 05-005. See more... | ||||
| OpenGIS Web Map Context Implementation Specification |
1.1 | 05-005 | Jerome Sonnet | 2005-05-03 |
| This document is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter "WMS 1.1.1."
WMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a "Web Map Context Document," or simply a "Context." Presently, context documents are primarily designed for WMS bindings. However, extensibility is envisioned for binding to other services.
A Context document includes information about the server(s) providing layer(s) in the overall map, the bounding box and map projection shared by all the maps, sufficient operational metadata for Client software to reproduce the map, and ancillary metadata used to annotate or describe the maps and their provenance for the benefit of human viewers.
A Context document is structured using eXtensible Markup Language (XML). Annex A of this specification contains the XML Schema against which Context XML can be validated.
See more... | ||||
| OpenGIS Web Map Service (WMS) Implementation Specification |
1.3.0 | 06-042 | Jeff de La Beaujardiere | 2006-03-15 |
| The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not. <p>NOTE: WMS 1.3 and ISO 19128 are the same documents. See more... | ||||
| OpenGIS Web Map Tile Service Implementation Standard |
1.0.0 | 07-057r7 | Joan Masó, Keith Pomakis and Núria Julià | 2010-04-06 |
| This Web Map Tile Service (WMTS) Implementation Standard provides a standard based solution to serve digital maps using predefined image tiles. The service advertises the tiles it has available through a standardized declaration in the ServiceMetadata document common to all OGC web services. This declaration defines the tiles available in each layer (i.e. each type of content), in each graphical representation style, in each format, in each coordinate reference system, at each scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares the communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles. See more... | ||||
| OpenGIS Web Service Common Implementation Specification |
1.1.0 | 06-121r3 | Arliss Whiteside | 2007-04-03 |
| The OpenGIS® Web Services Common (WS-Common) Interface Standard specifies parameters and data structures that are common to all OGC Web Service (OWS) Standards. The standard normalizes the ways in which operation requests and responses handle such elements as bounding boxes, exception processing, URL requests, URN expressions, and key value encoding. Among its uses, this document serves as a normative reference for other OGC Web Service standards, including the OpenGIS Web Map Service (WMS) [http://www.opengeospatial.org/standards/wms], Web Feature Service (WFS) [http://www.opengeospatial.org/standards/wfs], and Web Coverage Service (WCS) [http://www.opengeospatial.org/standards/wcs] standards. Rather than continuing to repeat this material in each such standard, each standard will normatively reference parts of this document. See more... | ||||
| OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum |
1.0.1 | 07-045r1 | Uwe Voges, Kristian Senkler | 2018-03-09 |
| Catalogue services are the key technology for locating, managing and maintaining
distributed geo-resources (i.e. geospatial data, applications and services). With OGC
catalogue services, client applications are capable of searching for geo-resources in a
standardized way (i.e. through standardized interfaces and operations) and, ideally, they
are based on a well-known information model, which includes spatial references and
further descriptive (thematic) information that enables client applications to search for
geo-resources in very efficient ways.
Whereas interfaces and operations of OGC catalogue services are well defined, it is left
up to the developer of the system to define a specific information model which a
catalogue service instance provides. This includes, but is not limited to, the information
which can be inserted in the catalog, supported query languages, available search terms,
response/result sets, etc. This point is of major importance with respect to interoperability
between different catalogue service instances.
In Europe, running catalogue instances result from work being done within different SDI
initiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC
EU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives
have developed an ISO-based application profile for ISO19115 metadata for
geodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled
geospatial services. The foundations of this profile were the OGC catalogue
specification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services
Stateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description.
OGC's catalogue revision working group (CS-RWG) has revised and integrated the
catalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of
this OGC specification comprises the definition of application profiles according to ISO
19106 (Geographic information – Profiles). The overall goal of these profiles is to
improve interoperability between systems conforming to a specific profile. Experience
has shown that the need for application profiles results from the fact that in practice, there
is no single solution for catalogue services that fits every user’s needs. As stated in CS
2.0.2, a base profile that provides a basic set of information objects has to be supported
by each catalogue instance; in addition, application profiles for different information
communities can be specified.
Hence, this document specifies an application profile for ISO 19115:2003/ISO
19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the
CS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application
profile will form the basis of conformance tests and reference implementations. See more... | ||||
| OpenGIS® City Geography Markup Language (CityGML) Encoding Standard |
1.0 | 08-007r1 | Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel | 2008-08-20 |
| CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.
The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.
See more... | ||||
| OpenGIS® Georeferenced Table Joining Service Implementation Standard |
1.0 | 10-070r2 | Peter Schut | 2010-11-22 |
| This document is the specification for a Table Joining Service (TJS). This OGC standard defines a simple way to describe and exchange tabular data that contains information about geographic objects. See more... | ||||
| OpenGIS® SWE Service Model Implementation Standard |
2.0 | 09-001 | Johannes Echterhoff | 2011-03-21 |
| This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard. See more... | ||||
| Ordering Services Framework for Earth Observation Products Interface Standard |
1.0 | 06-141r6 | Daniele Marchionni, Stefania Pappagallo | 2012-01-09 |
| This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products. See more... | ||||
| Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2 cat revision notes |
1.0 | 07-010 | Doug Nebert | 2007-06-19 |
| This document is a corrigendum for OGC Document 04-021r3. All changes described herein are published in OGC Document 07-006r1. See more... | ||||
| Semantic Sensor Network Ontology |
16-079 | Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois | 2019-07-10 | |
| The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given. See more... | ||||
| Time Ontology in OWL |
16-071r2 | Simon Cox, Chris Little | 2019-07-10 | |
| OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars.
See more... | ||||
| TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements |
1.0 | 15-042r3 | James Tomkins and Dominic Lowe | 2016-09-09 |
| TimeseriesML 1.0 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements [OGC 15-043r3], with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements. See more... | ||||
| Timeseries Profile of Observations and Measurements |
1.0 | 15-043r3 | James Tomkins , Dominic Lowe | 2016-09-09 |
| The OGC Timeseries Profile of Observations and Measurements is a conceptual model for the representation of observations data as timeseries, with the intent of enabling the exchange of such data sets across information systems. This standard does not define an encoding for the conceptual model; however there is an accompanying OGC Standard which defines an XML encoding (OGC TimeseriesML 1.0 - XML Encoding of the Timeseries Profile of Observations and Measurements). Other encodings may be developed in future. See more... | ||||
| Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure |
1.0 | 15-113r3 | Carl Reed | 2017-02-23 |
| The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.
The application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.
The CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated .
This standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features.
The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. A CDB data store can include terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the data store can includes the specific attributes of the synthetic environment data as well as their relationships.
The associated CDB Standard Best Practice documents provide a description of a data schema for Synthetic Environmental information (i.e. it merely describes data) for use in simulation. The CDB Standard provides a rigorous definition of the semantic meaning for each dataset, each attribute and establishes the structure/organization of that data as a schema comprised of a folder hierarchy and files with internal (industry-standard) formats.
A CDB conformant data store contains datasets organized in layers, tiles and levels-of-detail. Together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB compliant data store is specifically tailored for real-time applications.
See more... | ||||
| Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure |
1.1 | 15-113r5 | Carl Reed | 2018-12-19 |
| The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. See more... | ||||
| Volume 3: OGC CDB Terms and Definitions cdb-terms |
1.0 | 15-112r2 | Carl Reed | 2017-02-23 |
| This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. See more... | ||||
| Volume 3: OGC CDB Terms and Definitions |
1.1 | 15-112r3 | Carl Reed | 2018-12-19 |
| This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. See more... | ||||
| Volume 11: OGC CDB Core Standard Conceptual Model CDB-core-model |
1.0 | 16-007r3 | Sara Saeedi | 2017-02-23 |
| This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB 1.0 Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering a UML model and documentation from the OGC CDB standard as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113]. See more... | ||||
| Volume 11: OGC CDB Core Standard Conceptual Model |
1.1 | 16-007r4 | Sara Saeedi | 2018-12-19 |
| This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5].
NOTE: The simulation community uses the term “synthetic environment data” to mean all the digital data stored in some database or structured data store that is required for use by simulation clients. From the geospatial community perspective, these data are essentially the same as GIS data but with, in some cases, special attributes, such as radar reflectivity.
See more... | ||||
| Web Coverage Service (WCS) - Transaction operation extension |
1.1.4 | 07-068r4 | Arliss Whiteside | 2009-01-15 |
| This extension of the WCS standard specifies an additional Transaction operation that may optionally be implemented by WCS servers. This Transaction operation allows clients to add, modify, and delete grid coverages that are available from a WCS server. The Transaction operation request references or includes the new or modified coverage data, including all needed coverage metadata. See more... | ||||
| Web Processing Service |
1.0.0 | 05-007r7 | Peter Schut | 2007-10-05 |
| The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. See more... | ||||
