Best Practices
OGC Best Practices highlight the practical use of one or more OGC standards within a specific domain or to address particular use cases. Best Practices can describe how the standards are applied against scenarios or define a profile of a standard to tailor that standard to the requirements of a specific community. Prior to 2019, OGC Best Practices also included reference to the use of standards and specifications originating outside the OGC. Schemas for some of these documents can be at the Best Practices Schema Repository
| Document Title (click to view/download) | OGC Doc.# | Editor | Publication Date |
|---|---|---|---|
 OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE |
21-070 | Steve Liang | 2022 |
| Methane (CH4) is one of the most potent greenhouse gases, and the comparative impact of methane is 25 times greater than CO2 over a 100-year period. Methane is an invisible and odorless gas, and it is very labor intensive and time consuming in order to detect and repair leaks. Regulations play a cri ...Click to continue reading | |||
| OGC Best Practice for Earth Observation Application Package |
20-089r1 | Pedro Gonçalves | 2021 |
| Platforms for the exploitation of Earth Observation (EO) data have been developed by public and private companies in order to foster the usage of EO data and expand the market of Earth Observation-derived information. A fundamental principle of the platform operations concept is to move the EO data ...Click to continue reading | |||
 Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2 |
21-007 | DGIWG | 2021 |
| This document provides a profile for JPEG 2000 for use as a
compression format for raster imagery. JPEG 2000 uses
discrete wavelet transform (DWT) for compressing raster data,
as opposed to the JPEG standard, which uses discrete cosine
transform (DCT). It is a compression technology which is bes ...Click to continue reading | |||
| EO Collection GeoJSON(-LD) Encoding |
17-084r1 | Y. Coene, U. Voges, O. Barois | 2021 |
| 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. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attribut ...Click to continue reading | |||
| Volume 8: CDB Spatial and Coordinate Reference Systems Guidance |
16-011r5 | Carl Reed | 2021 |
| Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous ...Click to continue reading | |||
| Volume 7: OGC CDB Data Model Guidance (Best Practice) |
16-010r5 | Carl Reed | 2021 |
| This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.
| |||
| Volume 6: OGC CDB Rules for Encoding Data using OpenFlight |
16-009r5 | Carl Reed | 2021 |
| This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of t ...Click to continue reading | |||
| Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice) |
16-004r5 | Carl Reed | 2021 |
| This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store.
| |||
| Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice) |
16-070r4 | Carl Reed | 2021 |
| This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. | |||
| Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice) |
19-066 | Michala Hill | 2021 |
| This OGC Best Practice (BP) document describes the conversion process for converting a CDB structured Shapefile into a CDB structured GeoPackage. This is the companion document to Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). Volume 13 defin ...Click to continue reading | |||
| Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values |
16-003r4 | Carl Reed | 2021 |
| This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids k ...Click to continue reading | |||
| Volume 10: OGC CDB Implementation Guidance |
16-006r5 | Carl Reed | 2021 |
| This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store.
| |||
| Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice) |
15-120r6 | Carl Reed | 2021 |
| 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. ...Click to continue reading | |||
| OGC CDB Core Model and Physical Structure Annexes (Best Practice) |
16-005r4 | Carl Reed | 2021 |
| This document provides the Annexes for the CDB Core: Model and Physical Structure Standard. The only exception is Annex A, Abstract Test Suite (ATS). The CDB ATS Annex is in Volume 1: Core document. | |||
| Defence Profile of OGC Web Feature Service 2.0 |
15-005r2 | DGIWG | 2021 |
| This document defines the DGIWG profile for the ISO
19142:2010 - Web Feature Service (WFS) including changes
made in the OpenGIS Web Feature Service 2.0 Interface
Standard - Corrigendum. The Web Feature Service provides
access to geospatial features in a manner independent of the
underlying dat ...Click to continue reading | |||
| Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1 |
20-095 | DGIWG | 2021 |
| This OGC Best Practice was developed by the Defence Geospatial Information Working Group to address defense and intelligence user community requirements. As such, the Best Practice utilizes standardized military Coordinate Reference System (CRS) definitions, which may not be applicable to other user ...Click to continue reading | |||
| Defence Profile of OGC Web Map Service 1.3 Revision |
09-102r3 | DGIWG | 2021 |
| This document defines specific DGIWG requirements,
recommendations and guidelines for implementations of the
ISO and OGC Web Map Service standards; ISO 19128:2005
Web Map Server Interface and the OpenGIS Web Map Server
Implementation Specification 1.3.0. | |||
| Volume 8: CDB Spatial and Coordinate Reference Systems Guidance |
16-011r4 | Carl Reed | 2018 |
| Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous ...Click to continue reading | |||
| Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 |
16-010r4 | Carl Reed | 2018 |
| This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.
Please note that the term “lineal” has been replaced with the term “line” or “linear” throu ...Click to continue reading | |||
| Volume 6: OGC CDB Rules for Encoding Data using OpenFlight |
16-009r4 | Carl Reed | 2018 |
| This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of t ...Click to continue reading | |||
| Volume 5: OGC CDB Radar Cross Section (RCS) Models |
16-004r4 | Carl Reed | 2018 |
| This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store.
Please note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modifi ...Click to continue reading | |||
| Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage |
16-070r3 | Carl Reed | 2018 |
| This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. | |||
| Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes |
16-005r3 | Carl Reed | 2018 |
| This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document. | |||
| Volume 10: OGC CDB Implementation Guidance |
16-006r4 | Carl Reed | 2018 |
| This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. | |||
| Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure |
15-120r5 | Carl Reed | 2018 |
| 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. ...Click to continue reading | |||
| Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values |
16-003r3 | Carl Reed | 2018 |
| This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids k ...Click to continue reading | |||
| OGC Moving Features Encoding Extension: netCDF |
16-114r3 | Martin Desruisseaux | 2018 |
| The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Best Practice is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) exte ...Click to continue reading | |||
| OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data |
16-086r3 | Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little | 2018 |
| This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are members of an ensemble of maps, each of which is a valid possible alternative for the same time and location. In the meteorologi ...Click to continue reading | |||
| JSON Encoding Rules SWE Common / SensorML |
17-011r2 | Alex Robin | 2018 |
| This document describes new JavaScript Object Notation (JSON) encodings for the Sensor Web Enablement (SWE) Common Data Model and the Sensor Model Language (SensorML). Rather than creating new JSON schemas, this document defines encoding rules that allow auto-generation of JSON instances that confor ...Click to continue reading | |||
| Spatial Data on the Web Best Practices |
15-107 | Jeremy Tandy, Linda van den Brink, Payam Barnaghi | 2017 |
| This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices presented here are intended for practitioners, including Web developers and geospatial experts, and are compiled based on ...Click to continue reading | |||
| OGC Moving Features Encoding Extension - JSON mf-json |
16-140r1 | Kyoung-Sook KIM, Hirotaka OGAWA | 2017 |
| This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]). A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry who ...Click to continue reading | |||
| Volume 5: OGC CDB Radar Cross Section (RCS) Models cdb-radar |
16-004r3 | Carl Reed | 2017 |
| (RCS) data within a conformant CDB data store.
Please note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector a ...Click to continue reading | |||
| Volume 8: CDB Spatial and Coordinate Reference Systems Guidance CDB-SRF |
16-011r3 | Carl Reed | 2017 |
| Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous ...Click to continue reading | |||
| Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 DB-model-guidance |
16-010r3 | Carl Reed | 2017 |
| This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.
Please note that the term “lineal” has been replaced with the term “line” or “linear” throu ...Click to continue reading | |||
| Volume 6: OGC CDB Rules for Encoding Data using OpenFlight cdb-openflight |
16-009r3 | Carl Reed | 2017 |
| This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of t ...Click to continue reading | |||
| Volume 10: OGC CDB Implementation Guidance cdb-implementation-guidance |
16-006r3 | Carl Reed | 2017 |
| This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. | |||
| Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage |
16-070r2 | Carl Reed | 2017 |
| This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. | |||
| Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes |
16-005r2 | Carl Reed | 2017 |
| This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document. | |||
| Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values |
16-003r2 | Carl Reed | 2017 |
| This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids k ...Click to continue reading | |||
| Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure |
15-120r4 | Carl Reed | 2017 |
| 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. ...Click to continue reading | |||
| OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension jpip-jp2000 |
14-110r2 | Dimitri Sarafinof | 2016 |
| Coverages represent space/time-varying phenomena, such as satellite imagery, digital elevation models, or digital aerial imagery. OGC Abstract Topic 6 [OGC 07-011] – which is identical to ISO 19123 – defines an abstract model of coverages. Coverage instances may be encoded using the GML Applicat ...Click to continue reading | |||
| DGIWG - Web Feature Service 2.0 Profile |
15-005r1 | Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey | 2016 |
| This document defines the DGIWG profile for the ISO
19142:2010 - Web Feature Service (WFS) including changes
made in the OpenGIS Web Feature Service 2.0 Interface
Standard - Corrigendum. The Web Feature Service provides
access to geospatial features in a manner independent of the
underlying dat ...Click to continue reading | |||
| DGIWG - Web Map Service 1.3 Profile - Revision |
09-102r3 | Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey | 2016 |
| This document defines specific DGIWG requirements,
recommendations and guidelines for implementations of the
ISO and OGC Web Map Service standards; ISO 19128:2005
Web Map Server Interface and the OpenGIS Web Map Server
Implementation Specification 1.3.0. | |||
| OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response |
15-037 | George Percivall | 2015 |
| Responding to an oil spill requires access to and understanding of many types of information. Effective, coordinated operations for the response are based on a shared, common picture of the situation. Interoperability provides shared situational awareness of the crisis and the response activities. W ...Click to continue reading | |||
| OGC Common DataBase Volume 1 Main Body |
15-003 | David Graham | 2015 |
| The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plu ...Click to continue reading | |||
| OGC Common DataBase Volume 2 Appendices |
15-004 | David Graham | 2015 |
| The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plu ...Click to continue reading | |||
| Unified Geo-data Reference Model for Law Enforcement and Public Safety |
14-106 | Carl Reed, Jennifer Harne | 2015 |
| This document provides an overview of the Unified Geo-data Reference Model for Law Enforcement and Public Safety (Unified Model). The Unified Model was originally developed by the GIS Center for Security (GIS CS), Abu Dhabi Police. The GIS CS was initiated based on a UAE Ministry of Interior issued ...Click to continue reading | |||
| OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice |
13-039 | Nicolas Fanjeau, Sebastian Ulrich | 2014 |
| This document provides a specification of an OpenSearch extension for Earth Observation Satellites Tasking.
This OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated quer ...Click to continue reading | |||
| WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data watermlwq |
14-003 | Simon J D Cox, Bruce A Simons | 2014 |
| This Best Practice describes how to configure XML documents for single and time series water quality measurements. In addition to stating the rules for using the O&M and WML 2 standards, along with the appropriate content ontologies, this Best Practice provides guidance through examples. This d ...Click to continue reading | |||
| OGC® Sensor Observation Service 2.0 Hydrology Profile |
14-004r1 | Volker Andres, Simon Jirka , Michael Utech | 2014 |
| This OGC document defines an OGC Sensor Observation Service (SOS) 2.0 hydrology profile for SOS 2.0 implementations serving OGC WaterML 2.0. The development of this OGC Best Practice (BP) is based on previous activities and results (i.e. Hydrology Interoperability Experiments[1] as well as the Europ ...Click to continue reading | |||
| OGC RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking rest-sps-for-eo-tasking |
14-012r1 | Nicolas FANJEAU, Sebastian ULRICH | 2014 |
| This OGC® Best Practices document specifies the interfaces, bindings, requirements and conformance classes that enable complete workflows for the tasking of sensor planning services for Earth Observation (EO) satellites. In fact it provides the interfaces for supporting the following EO sensor plan ...Click to continue reading | |||
| OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products |
13-042 | Daniele Marchionni | 2014 |
| This OGC Best Practices document specifies the interfaces, bindings, requirements, conformance classes that enable complete workflows for ordering Earth Observation (EO) data products. In fact it provides the interfaces for supporting the following EO Product ordering scenarios:
• Ordering produc ...Click to continue reading | |||
| OGC User Management Interfaces for Earth Observation Services |
07-118r9 | P. Denis, P. Jacques | 2014 |
| This OGC Best Practice describes how user and identity management information may be included in the protocol specifications for OGC Services. The proposed approach is applicable to the orchestration of EO services, to system of systems and federation scenarios. The approach is meant to be independe ...Click to continue reading | |||
| OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data wms-tnz |
12-111r1 | Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B | 2014 |
| This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are time-dependent or elevation-dependent. In particular, clarifications and restrictions on the use of WMS are defined to allow una ...Click to continue reading | |||
| OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS) |
13-015 | EO2HEAVEN Consortium | 2014 |
| This document comprises experiences and recommendations when using
Sensor Web Enablement (SWE) concepts. This document focuses on
one basic issue: the provision of observations in an OGC SOS.
This includes the definition of a lightweight OGC SOS profile (OGC 11-
169r1), an analysis of and contri ...Click to continue reading | |||
| OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors |
11-169r1 | Simon Jirka, Christoph Stasch, Arne Bröring | 2014 |
| This Best Practice document describes a lightweight SOS 2.0 profile for stationary in-situ
sensors. Besides the SOS itself this document also addresses the data formats used by the
SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the
Sensor Model Language 2.0 ( ...Click to continue reading | |||
| Modeling an application domain extension of CityGML in UML |
12-066 | Linda van den Brink, Jantien Stoter, Sisi Zlatanova | 2014 |
| This paper presents key aspects of the development of a Dutch 3D standard IMGeo as a CityGML ADE. The new ADE is modeled using UML class diagrams. However the OGC CityGML specification does not provide clear rules on modeling an ADE in UML. This paper describes how the extension was built, which pro ...Click to continue reading | |||
| OGC Download Service for Earth Observation Products Best Practice |
13-043 | Daniele Marchionni, Raul Cafini | 2014 |
| This OGC® Best Practices document specifies the interfaces, bindings, requirements,
conformance classes for online download of Earth Observation products. This protocol
covers several scenarios implemented by European Space Agency - ESA for providing its
products to users:
- The EO Product to b ...Click to continue reading | |||
| OGC® Name Type Specification for Coordinate Reference Systems |
11-135r2 | Peter Baumann | 2013 |
| This document specifies a Name Type Specification (NTS) for predefined, combined, and parameterized Coordinate Reference System (CRS) definitions. This NTS augments the /def/ namespace with http URI definitions for CRSs. The NTS is based on the Name Type Specification – definitions – part 1 – ...Click to continue reading | |||
| EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue |
11-035r1 | Frédéric Houbie, Steven Smolders | 2013 |
| This is an OGC Best Practice document describing the relations that exist between several metadata conceptual models (EO Product, EO Product Collections, Sensors and Services). The specification of the linking between different artifacts is important for the process of cataloguing and discovering th ...Click to continue reading | |||
| WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice |
12-032r2 | Rahul Thakkar, Michael Maraist | 2012 |
| This OGC Best Practice (BP) describes web interface specifications for the access and dissemination of Wide Area Motion Imagery (WAMI) products and metadata. This BP also describes a framework and interface specifications common to all WAMI services. A <a href="https://portal.ogc.org/files/? ...Click to continue reading | |||
| Semantic annotations in OGC standards |
08-167r2 | Frédéric Houbie, Philippe Duchesne, Patrick Maué | 2012 |
| In this OGC Best Practice, the concept of semantic annotations is introduced. Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. | |||
| Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues cat-eo-ebxml-rim-3.0 |
10-189r2 | Frédéric Houbie; Fabian Skivee | 2012 |
| This OGC® document specifies the Earth Observation Products Extension Package for ebXML Registry Information Model 3.0, based on the [OGC 10-157r1] Earth Observation Metadata profile of Observations and Measurements.
It enables CSW-ebRIM catalogues to handle a variety of metadata pertaining to ear ...Click to continue reading | |||
| Gazetteer Service - Application Profile of the Web Feature Service Best Practice wfs gaz ap |
11-122r1 | Panagiotis (Peter) A. Vretanos, Jeff Harrison | 2012 |
| This document defines a Gazetteer Service profile of the OGC Web Feature Service Standard. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names.
This profile extends the WFS interface in a way that a client is able to
– ...Click to continue reading | |||
| OGC® Web Coverage Service 2.0 Primer: Core and Extensions Overview WCS Primer |
09-153r1 | Peter Baumann | 2012 |
| This document provides an overview on the OGC Web Coverage Service (WCS) 2.0 suite by describing WCS core and extensions.
Intended target audience are developers intending to implement WCS servers and/or clients. This document aims at providing an overview and giving useful hints and best practice ...Click to continue reading | |||
| PDF Geo-registration Encoding Best Practice Version 2.2 |
08-139r3 | George Demmy, Carl Reed | 2011 |
| The intended audience of this document is a developer of software for creating and consuming geo=registered PDF documents that conform to PDF geo-registration 2.2. It specifies how to create the necessary PDF objects that identify a region of the PDF page as a map and describe the map’s coordinate ...Click to continue reading | |||
| User Management for Earth Observation Services |
07-118r8 | P Denis | 2010 |
| This document describes how user and identity management information may be included in the protocol specifications for OGC Services. The use cases addressed will make reference to EO (Earth Observation) services, for example catalogue access (EO Products Extension Package for ebRIM (ISO/TS 15000-3) ...Click to continue reading | |||
| GIGAS Methodology for comparative analysis of information and data management systems |
10-028r1 | Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits | 2010 |
| This document has been written on the basis of a methodology developed within the GIGAS Support Action financed by the European Commission in order to address the convergence of global initiatives like GEOSS and the European interoperability initiatives developed in the context of the GMES programme ...Click to continue reading | |||
| Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed |
10-003r1 | Louis Hecht, Jr., Raj Singh | 2010 |
| The Architecture, Engineering, Construction, Owner Operator, Phase 1 (AECOO-1) Testbed developed and implemented methods to streamline communications between parties in the conceptual design phase to get an early understanding of the tradeoffs between construction cost and energy efficiency. To that ...Click to continue reading | |||
| Web Map Services - Application Profile for EO Products WMS AP EO |
07-063r1 | Thomas H.G. Lankester | 2009 |
| This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. | |||
| DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment WMS DGIWG Profile |
09-102 | Cyril Minoux | 2009 |
| This document specifies requirements for systems providing maps using OGC Web Map Service. The document defines a profile of OGC WMS 1.3 implementation standard [WMS1.3], a list of normative system requirements and a list of non-normative recommendations. The Defence Geospatial Information Working G ...Click to continue reading | |||
| Compliance Test Language (CTL) Best Practice |
06-126r2 | Chuck Morris | 2009 |
| This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification. | |||
| OGC® KML Standard Development Best Practices |
08-125r1 | Tim Wilson, David Burggraf | 2009 |
| This OGC® Best Practices Document provides guidelines for developing the OGC KML standard in a manner that best serves and supports the KML application developer and user communities. It applies to the extension of KML by application developers and the subsequent enhancement of the KML standard by ...Click to continue reading | |||
| Definition identifier URNs in OGC namespace |
07-092r3 | Arliss Whiteside | 2009 |
| This document specifies Universal Resource Names (URNs) in the “ogc” URN namespace to be used for identifying definitions. These definitions include definitions of Coordinate Reference Systems (CRSs) and related objects, as specified in OGC Abstract Specification Topic 2: Spatial referencing by ...Click to continue reading | |||
| Sensor Web Enablement Architecture |
06-021r4 | Ingo Simonis | 2008 |
| This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard. | |||
| A URN namespace for the Open Geospatial Consortium (OGC) |
07-107r3 | Carl Reed | 2008 |
| This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is "ogc". | |||
| OpenGIS Sensor Planning Service Application Profile for EO Sensors SPS AP EO |
07-018r2 | Philippe M | 2008 |
| The SPS configuration proposed in this profile is intended to support the programming process of Earth Observation (EO) sensors system. This profile describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the manageme ...Click to continue reading | |||
| Reference Model for the ORCHESTRA Architecture |
07-097 | Thomas Uslander (Ed.) | 2007 |
| This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It is an extension of the OGC Reference Model and contains a specification framework for the design of geospatial service-oriented architectures and service networks. The RM-OA comprises the generic aspects of servic ...Click to continue reading | |||
| GML Encoding of Discrete Coverages (interleaved pattern) DiscreteCoverages |
06-188r1 | Simon Cox | 2007 |
| This specification describes a GML encoding for discrete coverages. The encoding pattern is a variation from the standard GML Coverage, in that the values in the domain and range are effectively "interleaved" rather than represented as two blocks and encoded sequentially. | |||
| GML PIDF-LO Geometry Shape Application Schema for use in the IETF GML PIDF-LO |
06-142r1 | Carl Reed, PhD. and Martin Thomson | 2007 |
| This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for XML encoding of various geometric shapes required in the Presence Information Description Format (IETF RFC 3863) Location Object extension - A Presence-based GEOPRIV Location Object Format (RFC 4119) ...Click to continue reading | |||
| Sensor Alert Service |
06-028r3 | Ingo Simonis | 2007 |
| The Sensor Alert Service (SAS) can be compared with an event notification system. The sensor node is the object of interest. Each node has to advertise its publications at a SAS (advertise). | |||
| Web Notification Service |
06-095 | Ingo Simonis, Johannes Echterhoff | 2007 |
| A service by which a client may conduct asynchronous dialogues (message interchanges) with one or more other services. This service is useful when many collaborating services are required to satisfy a client request, and/or when significant delays are involved is satisfying the request. This servic ...Click to continue reading | |||
| FGDC CSDGM Application Profile for CSW 2.0 CAT2 AP FGDC |
06-129r1 | Patrick Neal, John Davidson, Bruce Westcott | 2006 |
| The OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW 2.0 explains how Catalogue Services based on the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/... ...Click to continue reading | |||
| Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification |
05-035r2 | Jens Fitzke, Rob Atkinson | 2006 |
| This document defines a Gazetteer Service profile of the OGC Web Feature Service Specification. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names. | |||
| Binary Extensible Markup Language (BXML) Encoding Specification |
03-002r9 | Craig Bruce | 2006 |
| This OGC Best Practices document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format. | |||
| OpenGIS Web services architecture description |
05-042r2 | Arliss Whiteside | 2005 |
| This document summarizes the most significant aspects of the Open Geospatial Consortium (OGC) web services architecture, which the OGC is currently developing. This architecture is a service-oriented architecture, with all components providing one or more services to other services or to clients. | |||
| Units of Measure Recommendation |
02-007r4 | John Bobbitt | 2002 |
| Common semantic for units of measurement to be used across all OGC specifications. | |||
