Best Practices

Documents containing discussion of best practices related to the use and/or implementation of an adopted OGC document and for release to the public. Best Practices Documents are an official position of the OGC and thus represent an endorsement of the content of the paper. Schemas for some of these documents can be at the Best Practices Schema Repository.

Document Title (click to view/download)	Version	Doc.#	Editor	Date
Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure	1.1	15-120r5	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.
Volume 6: OGC CDB Rules for Encoding Data using OpenFlight	1.1	16-009r4	Carl Reed	2018-12-19
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 that document for a general overview.
Volume 8: CDB Spatial and Coordinate Reference Systems Guidance	1.1	16-011r4	Carl Reed	2018-12-19
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 specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. In previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC.
Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2	1.1	16-010r4	Carl Reed	2018-12-19
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” throughout this document Please note that the term “areal” has been replaced with the term “polygon” throughout this document.
Volume 10: OGC CDB Implementation Guidance	1.1	16-006r4	Carl Reed	2018-12-19
This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store.
Volume 5: OGC CDB Radar Cross Section (RCS) Models	1.1	16-004r4	Carl Reed	2018-12-19
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 modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.
Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage	1.1	16-070r3	Carl Reed	2018-12-19
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	1.1	16-005r3	Carl Reed	2018-12-19
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	1.1	16-003r3	Carl Reed	2018-12-19
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 key words.
OGC Moving Features Encoding Extension: netCDF	1.0	16-114r3	Martin Desruisseaux	2018-12-18
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) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored.
OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data	1.0	16-086r3	Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little	2018-04-05
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 meteorological and oceanographic communities, it is Best Practice to produce a large number of simultaneous forecasts, whether for a short range of hours, a few days, seasonal or climatological predictions. These ensembles of forecasts indicate the probability distributions of specific outcomes. This document describes how to unambiguously specify an individual member of an ensemble, or one of a limited set of map products derived from a full ensemble. In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service.
JSON Encoding Rules SWE Common / SensorML	1.0	17-011r2	Alex Robin	2018-01-18
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 conform to the Unified Modeling Language (UML) models. Alternatively, the mappings given in the second part of the document can be used to convert bi-directionally between XML and JSON representations.
Spatial Data on the Web Best Practices		15-107	Jeremy Tandy, Linda van den Brink, Payam Barnaghi	2017-09-28
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 evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting an approach based on general Web standards. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Web of data.
OGC Moving Features Encoding Extension - JSON mf-json	1.0	16-140r1	Kyoung-Sook KIM, Hirotaka OGAWA	2017-06-28
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 whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time. This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures). In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web.
Volume 5: OGC CDB Radar Cross Section (RCS) Models cdb-radar	1.0	16-004r3	Carl Reed	2017-02-23
(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 attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.
Volume 8: CDB Spatial and Coordinate Reference Systems Guidance CDB-SRF	1.0	16-011r3	Carl Reed	2017-02-23
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 specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. In previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC.
Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 DB-model-guidance	1.0	16-010r3	Carl Reed	2017-02-23
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” throughout this document Please note that the term “areal” has been replaced with the term “polygon” throughout this document.
Volume 6: OGC CDB Rules for Encoding Data using OpenFlight cdb-openflight	1.0	16-009r3	Carl Reed	2017-02-23
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 that document for a general overview.
Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes	1.0	16-005r2	Carl Reed	2017-02-23
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 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage	1.0	16-070r2	Carl Reed	2017-02-23
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 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values	1.0	16-003r2	Carl Reed	2017-02-23
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 key words.
Volume 10: OGC CDB Implementation Guidance cdb-implementation-guidance	1.0	16-006r3	Carl Reed	2017-02-23
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	1.0	15-120r4	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.
OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension jpip-jp2000	1.0	14-110r2	Dimitri Sarafinof	2016-11-02
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 Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108] which is based on the GML Application Schema – Coverages (GMLCOV) version 1.0 [OGC 09-146r2] which in turn is based on the Geography Markup Language (GML) version 3.2 [07-036], an XML grammar written in XML Schema for the description of application schemas as well as the transport and storage of geographic information. This extension to the Web Coverage Service (WCS) 2.0 Interface Standard – Core (WCS) version 2.0 [OC 09-110r4] specifies the usage of the JPEG2000 coverage encoding and JPIP streaming capabilities with WCS. The approach is based on the authoritative GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108].
DGIWG - Web Feature Service 2.0 Profile	2.0	15-005r1	Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey	2016-02-01
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 data store.
DGIWG - Web Map Service 1.3 Profile - Revision	2.0	09-102r3	Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey	2016-01-29
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	1.0	15-037	George Percivall	2015-10-01
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. What is needed is a common picture of reality for different organizations that have different views of the spill so that they all can deal with it collectively. Recent oil spills have provided lessons learned and recommendations on forming a Common Operating Picture for oil spill response. Through a joint project, industry is responding to the call, moving from recommendations to reusable best practices supported by open standards that can be deployed quickly in any region of the globe. This architecture report is part of The International Association of Oil & Gas Producers and IPIECA Oil Spill Response - Joint Industry Project (IOGP–IPIECA OSR-JIP) to produce a recommended practice for GIS/mapping in support of oil spill response and for the use of GIS technology and geospatial information in forming a “Common Operating Picture” to support management of the response. Interoperability seems to be at first a technical topic, but in fact, it is about organization. Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior. The Oil Spill Response Common Operating Picture (OSR COP) project seeks to facilitate the coordination of organizational response to any oil spill in the future.
OGC Common DataBase Volume 1 Main Body	1.0	15-003	David Graham	2015-07-22
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 plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (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 simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, 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 Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the 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 synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships. A CDB 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 is specifically tailored for real-time applications.
OGC Common DataBase Volume 2 Appendices	1.0	15-004	David Graham	2015-07-22
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 plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (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 simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, 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 Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the 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 synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships. A CDB 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 is specifically tailored for real-time applications.
Unified Geo-data Reference Model for Law Enforcement and Public Safety	1.0	14-106	Carl Reed, Jennifer Harne	2015-01-30
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 decree to establish GIS CS with the core mission: “To geo-enable police services and applications using International standards and best practices.” In 2010, the GIS SC initiated a program to develop a Standardized GIS Environment (SGA). Part of this effort was to define and implement a standard data model for sharing Law Enforcement and Public Safety data.
OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice	1.0	13-039	Nicolas Fanjeau, Sebastian Ulrich	2014-12-29
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 query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set. This document is the result of work undertaken within the European Space Agency (ESA) Heterogeneous Mission Accessibility for Science (HMA-S) project funded by ESA the Long Term Data Preservation (LTDP) program. The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (see ‘Normative References’ section) related projects.
WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data watermlwq	1.0	14-003	Simon J D Cox, Bruce A Simons	2014-12-02
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 document is intended to complement WaterML 2.0 as part of a suite of standards for water observation data.
OGC® Sensor Observation Service 2.0 Hydrology Profile	1.0	14-004r1	Volker Andres, Simon Jirka , Michael Utech	2014-10-20
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 European FP7 project GEOWOW[2]). The work is guided by the need to overcome semantic issues between different SOS instances serving hydrological data and the related client applications. Therefore, this profile focuses on how to use the entities and requests of the standards and defines the necessary technical details to implement the hydrology SOS profile.
OGC RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking rest-sps-for-eo-tasking	1.0	14-012r1	Nicolas FANJEAU, Sebastian ULRICH	2014-07-17
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 planning scenarios: • Planning future acquisitions with feasibility study, • Direct planning of future acquisitions, • Reservation of planning for future acquisitions. This specification includes a comprehensive list of sensor options and tasking options derived from the parent specification OGC 10-135 [NR22] which gathered inputs from several Satellite Agencies and Operators: • ESA • EUMETSAT • CNES • DLR • CSA • Airbus Defence & Space This document is based on the standard: OGC 10-135, Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking Extension, version 2.0. 2011. which was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects. With respect to the parent specification this Best Practice document proposes the following changes: • Replaces SOAP with REST for service encoding. This affects not only the way the service is implemented but also the way the standard is presented and described. In fact, basing the standard on REST implies that the service has to be described in terms of resources and methods applied on them whilst in SOAP services, the description is focusing on operations and in fact the OGC 10-135[NR22] is structured in Web Service operations. • Usage of OpenSearch Description Documents as an alternate method for describing sensors and tasking Options (§7.3.2). This specification uses the sensors and tasking options model already described in the OGC 10-135 [NR22] standard but defines an additional method for describing sensors and tasking options within OpenSearch Description Documents based on the OGC 13-039 [NR23]. Actually this part of the specification refers to the OpenSearch Extension for Earth Observation Satellite Tasking.  
OGC User Management Interfaces for Earth Observation Services	1.1	07-118r9	P. Denis, P. Jacques	2014-04-28
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 independent from the specific OGC service. The use cases potentially addressed are very wide and in general may cover geospatial services and not only EO (Earth Observation) services. The use cases may range from web map, feature or coverage services, web processing services, to catalogue services. Examples of EO specific use cases are: ordering (Ordering Services for Earth Observation Products [OGC 06-141r6]) and feasibility analysis (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 10 135]). The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects. This document is not an OGC standard. This document describes how existing specifications from W3C and OASIS can be used in combination to pass identity information to OGC Web services.
OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products	1.0	13-042	Daniele Marchionni	2014-04-28
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 products from EO Catalogues • Subscribing to automatic delivery of EO products • Bulk EO Product orders The EO products orders can be delivered on file via different online protocols (e.g. ftp, sftp, ftps, etc.).
OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data wms-tnz	1.0	12-111r1	Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B	2014-04-14
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 unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service.
OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS)	1.0	13-015	EO2HEAVEN Consortium	2014-02-25
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 contribution to the specification of the Sensor Observation Service (SOS) 2.0 as well as an approach how the data used within Earth observation (EO) applications can be integrated more easily into SOS instances. These recommendations result from the work performed in 2010-2013 as part of the research project EO2HEAVEN (Earth Observation and Environmental Modelling for the Mitigation of Health Risks), co-funded by the European Commission as part of the 7th Framework Programme (FP7) Environmental theme. EO2HEAVEN contributes to a better understanding of the complex relationships between environmental changes and their impact on human health. See http://www.eo2heaven.org/ . The lightweight OGC SOS profile has been developed in close cooperation between the FP7 projects EO2HEAVEN and UncertWeb (see http://www.uncertweb.org/ ).
OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors	1.0	11-169r1	Simon Jirka, Christoph Stasch, Arne Bröring	2014-02-25
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 (SensorML) for encoding metadata. Other SWE standards which provide more specialized functionality are not part of this minimum lightweight SWE profile. The aim of this document is to present a common minimum profile of the SOS. The profile is intended to reduce the complexity of the standard by omitting highly specific elements that are not necessary for the majority of use cases that occur in practice. At the same time, the profile is designed in such a way that all SOS implementations that conform to this profile are also compliant to the according OGC specifications.
Modeling an application domain extension of CityGML in UML	1.0	12-066	Linda van den Brink, Jantien Stoter, Sisi Zlatanova	2014-01-31
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 provides general insight how CityGML can be extended for a specific applications starting from the UML diagrams. Several alternatives for modeling ADEs in UML have been investigated and compared. The best suited for the 3D standard option is selected and applied. Open issues and challenges are discussed in the conclusions.
OGC Download Service for Earth Observation Products Best Practice	1.0	13-043	Daniele Marchionni, Raul Cafini	2014-01-31
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 be downloaded is already available and can be downloaded as it is. - The EO Product is not online available but is stored in a near online archive. - The EO Product is advertised in a Catalogue, but it is not physically available and it has to be generated on the fly by a processing facility. - The EO product is archived in several distributed online archives and it can be downloaded in parallel. The basic scenarios can be simply supported by Web Browsers, the most complex ones need a dedicated client (download manager) supporting Metalink and multisource download. This Best Practice document has been prepared basing on the work performed in the frame of ESA’s Next Generation Earth Observation user services and it was initially produced during the ESA
OGC® Name Type Specification for Coordinate Reference Systems	1.0	11-135r2	Peter Baumann	2013-06-18
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 – basic name [OGC 09-048r3] and supersedes OGC document “Definition identifier URNs in OGC name¬space” [OGC 07-092r3]. NTSs are maintained by the OGC Naming Authority (OGC-NA). This document includes one Annex: a user guide to the OGC CRS resolver.
EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue	1.0	11-035r1	Frédéric Houbie, Steven Smolders	2013-03-26
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 those artifacts.
WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice	1.0	12-032r2	Rahul Thakkar, Michael Maraist	2012-12-05
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.opengeospatial.org/files/?artifact_id=50485">WAMI - Primer</a> has been developed to help you implement this Best Practice.
Semantic annotations in OGC standards	2.0	08-167r2	Frédéric Houbie, Philippe Duchesne, Patrick Maué	2012-10-10
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	1.0	10-189r2	Frédéric Houbie; Fabian Skivee	2012-06-12
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 earth observation p/roducts as defined in [OGC 10-157r1]. This proposed application profile document describes model and encodings required to discover, search and present metadata from catalogues of Earth Observation products. The profile presents a minimum specification for catalogue interoperability within the EO domain, with extensions for specific classes of metadata.
Gazetteer Service - Application Profile of the Web Feature Service Best Practice wfs gaz ap	1.0	11-122r1	Panagiotis (Peter) A. Vretanos, Jeff Harrison	2012-02-17
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 – Determine if a WFS implementation is acting as a Gazetteer Service. – Query the Gazetteer Service in order to retrieve place-name features without closer examination of the feature type definitions – Access metadata about the gazetteer(s) provided by the service – Update place-name features using WFS transactions – Fetch place-name features that have Parent-Child relationships and then follow those links
OGC® Web Coverage Service 2.0 Primer: Core and Extensions Overview WCS Primer	2.0	09-153r1	Peter Baumann	2012-01-25
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 practices beyond the pure standards texts. It is a &quot;living document&quot; which will evolve to reflect new developments and best practices. As such, the contents of this document is informative and not of normative nature.
PDF Geo-registration Encoding Best Practice Version 2.2	1.1	08-139r3	George Demmy, Carl Reed	2011-01-17
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 systems. Map creation and rendering to a PDF page are not addressed. The underlying PDF file format is not addressed. The file format is specified in PDF Reference[1] .
User Management for Earth Observation Services	1.0	07-118r8	P Denis	2010-09-08
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) Profile of CSW 2.0 [OGC 06-131]), ordering (Ordering Services for Earth Observation Products [OGC 06-141r2]) and programming (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 07-018r2]).
GIGAS Methodology for comparative analysis of information and data management systems	0.5.0	10-028r1	Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits	2010-06-04
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 like HMA - Heterogeneous Missions Accessibility and the INSPIRE spatial data infrastructure legislation.
Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed	0.3.0	10-003r1	Louis Hecht, Jr., Raj Singh	2010-06-04
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 end, the project developed the interoperability components required for these analyses in collaborative team settings. These were Information Delivery Manuals (IDMs) for quantity takeoffs and energy analysis business processes, and used these to define Model View Definitions (MVDs)—standards-based subsets of Industry Foundation Classes (IFCs). AECOO-1 was conducted in response the felt need that overall productivity loss and fragmentation in the capital facilities development industries is no longer tolerable. All stakeholders need to practice the best way they know, and practice profitably; software interoperability problems must not hold them back. Non-interoperable software and data is cause for loss of competition across the market.
Web Map Services - Application Profile for EO Products WMS AP EO	0.3.3	07-063r1	Thomas H.G. Lankester	2009-11-05
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	0.9.0	09-102	Cyril Minoux	2009-09-02
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 Group (DGIWG) performed the work as part of through the S05 Web Data Access Service Project of the Services & Interfaces Technical Panel.
Compliance Test Language (CTL) Best Practice	0.6.0	06-126r2	Chuck Morris	2009-07-21
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	0.6	08-125r1	Tim Wilson, David Burggraf	2009-02-04
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 the OGC.
Definition identifier URNs in OGC namespace	1.3	07-092r3	Arliss Whiteside	2009-01-15
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 coordinates, plus several other resource types for which standard identifiers are useful in OGC Web Services. This document specifies the formats used by these URNs, including formats that can reference definitions recorded in the EPSG database and by other authorities. This document also specifies URNs for some specific definitions for which OGC is the custodian.
Sensor Web Enablement Architecture	0.4.0	06-021r4	Ingo Simonis	2008-08-20
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)	0.4	07-107r3	Carl Reed	2008-05-02
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	0.9.5	07-018r2	Philippe M	2008-01-21
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 management of these programming requests.
Reference Model for the ORCHESTRA Architecture	2.1	07-097	Thomas Uslander (Ed.)	2007-10-05
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 service-oriented architectures, i.e., those aspects that are independent of the risk management domain and thus applicable to other application domains.
GML Encoding of Discrete Coverages (interleaved pattern) DiscreteCoverages	0.2.0	06-188r1	Simon Cox	2007-05-17
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	0.1.0	06-142r1	Carl Reed, PhD. and Martin Thomson	2007-05-17
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).
Sensor Alert Service	0.9	06-028r3	Ingo Simonis	2007-05-16
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	0.0.9	06-095	Ingo Simonis, Johannes Echterhoff	2007-01-25
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 service was defined under OWS 1.2 in support of SPS operations. WNS has broad applicability in many such multi-service applications. It is now used in several SWE scenarios.
FGDC CSDGM Application Profile for CSW 2.0 CAT2 AP FGDC	0.0.12	06-129r1	Patrick Neal, John Davidson, Bruce Westcott	2006-12-26
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/... Application Profile for the OpenGIS® Catalogue Service Interface Standard v2.0.1 [http://www.opengeospatial.org/standards/cs] are organized and implemented for the discovery, retrieval and management of data metadata.
Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification	0.9.3	05-035r2	Jens Fitzke, Rob Atkinson	2006-07-27
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	0.0.8	03-002r9	Craig Bruce	2006-01-18
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	0.1.0	05-042r2	Arliss Whiteside	2005-11-21
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	1.0	02-007r4	John Bobbitt	2002-08-19
Common semantic for units of measurement to be used across all OGC specifications.