Skip navigation.
Home
"Making location count"
 OGC® Home | OGC Network™ | OGC User™ | OGC Forum
HOME » STANDARDS

Deprecated Documents

WARNING!

The documents listed below are deprecated and provided for historical purposes only. Please go the Standards pages to the left for the most current versions of the Implementation Specifications, Best Practice or Discussion Papers.

Document Title (click to download) Version Document # Editor Date
A URN namespace for the Open Geospatial Consortium (OGC)  2  06-166  Carl Reed  2007-01-30
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".
A URN namespace for the Open Geospatial Consortium (OGC)  1  04-013r4  Carl Reed  2004-09-20
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 (such as OGC Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). The formal Namespace identifier (NID) is "ogc".
Basic Services Model  0.0.8  01-022r1  Jeff de La Beaujardiere  2001-05-05
The Basic Services Model is an implementation of the ISO TC211 services architecture as found in ISO 19119 Geographic Information
Binary-XML Encoding Specification  0.0.8  03-002r8  Craig Bruce  2003-05-07
This 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.
Catalog 2.0 IPR for ebRIM  0.0.4  05-109r1  Panagiotis (Peter) A. Vretanos, Rento Primavera  2006-05-09
The purpose of this document is to show how to map the various types of metadata documents to be used in the OWS3 project into the ebRIM.
Catalog Interface  1.1.1  02-087r3  Doug Nebert  2002-12-13
Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers.
Catalog Interface  1.0  99-051  Doug Nebert  1999-07-16
Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers.
City Geography Markup Language  0.3.0  06-057r1  Thomas Kolbe, Gerhard Groeger and Angela Czerwinski  2006-08-18
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 3 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.
CT Definition Data for Coordinate Reference  1.1.0  01-014r5  Arliss Whiteside  2001-10-10
A data model for coordinate reference systems to provide a common framework across all OGC specifications.
Definition identifier URNs in OGC namespace  1.1.0  06-023r1  Arliss Whiteside  2006-08-08
*** Corrigendum - updated 2006-08-08 ***

This revised version of this document adds additional allowed "authority" and "objectType" values, plus specifies URNs for data types, as proposed in change requests OGC 05-091r2 and 05-060. In addition, corrections have been made to the XML documents listed in Annex A. The changes made in this version are tracked in the Microsoft Word (.doc) format of this document.

This Best Practices Paper specifies Universal Resource Names (URNs) in the "ogc" URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS.
EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0  0.0.3  06-131  Renato Primavera  2006-10-24
This document describes the Data Model of Earth Observation Products for the OGC
Filter Encoding  1.0  02-059  Peter Vretanos  2001-05-01
A filter is a construct used to describe constraints on properties of a feature class for the purpose of identifying a subset of feature instances to be operated upon in some way.
Gazetteer  0.8  01-036  Rob Atkinson  2001-03-15
An authority for place names. Returns their associated geometries
Gazetteer Service Profile of a WFS  0.9.1  05-035r1  Jens Fitzke, Rob Atkinson  2006-01-12
Provides web access to an authority for place names. Returns their associated feature representations
Geography Markup Language  2.1.2  02-069  Ron Lake  2002-08-19
The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.
Geography Markup Language  1.0  00-029  Ron Lake  2000-05-12
The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.
Geography Markup Language  2.1.1  02-009  Ron Lake  2002-01-14
The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.
Geography Markup Language  2.0  01-029  Ron Lake  2001-02-20
The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.
GEOINT Structure Implementation Profile Schema Processing  0.5  07-028r1  Clemens Portele  2007-05-17
This document contains a description of the schema tailoring process for application schema development based on the U.S. National System for Geospatial-Intelligence (NSG) GEOINT Structure Implementation Profile (GSIP) as developed in conjuction with the Open Geospatial Consortium Interoperability Program initiative OWS-4.
GML Application Schema for EO Products  0.1.4  06-080r1  Jerome Gasperi  2007-02-05
This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]
GML Application Schema for EO Products  0.1.1  06-080  Jerome Gasperi  2006-07-27
This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3].
GML in JPEG 2000 for Geographic Imagery  0.3.0  05-047r2  Ron Lake  2005-03-28
The GML (Geography Markup Language) is an XML grammar for the encoding geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects.
JPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file.
This specification defines the means by which GML is to be used within JPEG 2000 images for geographic imagery. This includes the following:
GML simple features profile  0.0.19  05-033r9  Peter Vretanos  2005-07-04
This profile defines a restricted but useful subset of XML-Schema and GML to lower the
GO-1 Application Objects  0.5.0  03-064r5  Eric Bertel  2004-06-25
The GO-1 Application Objects specification defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics.
GO-1 Application Objects Report  0.2.0  03-064r1  Phillip C. Dibner  2003-06-12
This document is a draft of the OpenGIS
High-Level Ground Coordinate Transformation Interface  0.0.3  01-013r1  Arliss Whiteside  2001-02-27
This document specifies a
ISO19115/ISO19119 Application Profile for CSW 2.0  0.9.2  04-038r1  Uwe Voges, Kristian Senkler  2004-10-05
This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS
ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)  0.9.3  04-038r2  Uwe Voges, Kristian Senkler  2005-04-27
This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS
KML 2.1 Reference - An OGC Best Practice  2.1.0  07-039r1  Carl Reed  2007-05-07
KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.
KML 2.2 Reference - An OGC Best Practice  2.2  07-113r1  Google, Galdos  2007-11-23
KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.
Minimal Application Profile for EO Products  0.3.0  05-057r3  Jolyon Martin  2006-02-09
The services proposed in this profile are intended to support the identification and subsequent ordering of
EO data products from previously identified data collections. The intent of this initial profile is to
describe a minimum interface that can be supported by many data providers (satellite operators, data
distributors
Observations and Measurements  0.86  02-027  Simon Cox  2002-05-31
This document describes a framework and encoding for measurements and observations.
Observations and Measurements  0.9.2  03-022r3  Simon Cox  2003-02-04
This document describes a framework and encoding for measurements and observations.
Observations and Measurements  0.14.7  05-087r4  Simon Cox  2006-10-11
The general models and XML encodings for observations and measurements, including but not restricted to those using sensors.
Observations and Measurements  0.13.0  05-087r3  Simon Cox  2006-04-05
The general models and XML encodings for observations and measurements, including but not restricted to those using sensors.
OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW  0.9.1  04-017r1  Richard Martell  2004-10-12
The OGC Catalogue Services 2.0 specification (OGC 04-021) establishes a framework for implementing catalogue services that can meet the needs of stakeholders in a wide variety of application domains. This application profile is based on the CSW schemas for web-based catalogues and it complies with the requirements of clause 11 in OGC 04-021.
OGC Technical Document Baseline  1.3  04-014r1  Carl Reed, George Percivall  2004-04-22
Spreadsheet of OGC Technical Document Baseline
OGC Technical Document Baseline  1.2  03-053r1  Carl Reed, George Percivall  2003-05-22
Spreadsheet of OGC Technical Document Baseline
OGC Web Services Common  0.1.0  03-088r1  Arliss Whiteside  2003-10-16
This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses.
OGC Web Services Common  0.2.0  03-088r6  Arliss Whiteside  2004-01-19
This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses.
OpenGIS Catalogue Service Implementation Specification  2.0.1  04-021r3  Doug Nebert  2004-08-02
The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources.
OpenGIS Catalogue Services - Best Practices for for Earth Observation Products  0.3  05-057r4  Jolyon Martin  2006-03-20
The services proposed in this profile are intended to support the identification and subsequent ordering of EO data products from previously identified data collections. The intent of this initial profile is to describe a minimum interface that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data.
OpenGIS Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW  1.0.0  05-025r3  Richard Martell  2006-10-24
The OGC Catalogue Services 2.0 specification (OGC 04-021r3) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. This application profile 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.
OpenGIS Geography Markup Language (GML) Encoding Specification  3.1.1  03-105r1  Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside  2004-04-19
The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.
OpenGIS Geography Markup Language (GML) Encoding Specification  3.0  02-023r4  Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside  2003-01-29
The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.
OpenGIS GML 3.2 image geopositioning metadata application schema  0.0.0  06-055r1  Arliss Whiteside  2006-07-12
This document specifies a GML 3.2 Application Schema for image geopositioning metadata, which is also an Application Schema of ISO 19139. This geopositioning metadata schema is used by the separately specified Image Geopositioning Service (IGS) interface that adjusts the georeferencing coordinate transformations of images.
OpenGIS Image Geopostioning Service  0.0.0  06-054r1  Arliss Whiteside  2006-07-12
This document specifies the interface to an Image Geopositioning Service that adjusts the georeferencing coordinate transformations of multiple images. This adjustment is normally done using a photogrammetric triangulation process, although other methods could be used. Such triangulation adjusts the parameter values of the image georeferencing coordinate transformations using a least-squares fitting process to measured image positions with known error statistics.
OpenGIS Implementation Specification for Geographic information - Simple feature access -  1.1.0  05-134  Keith Ryden  2005-11-30
This part of OpenGIS
OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architectu  1.1.0  05-126  Keith Ryden  2005-11-30
This part of OpenGIS
OpenGIS Location Services (OpenLS): Core Services [Part 2 Gateway Service]  1.0  03-006r3  Marwa Mabrouk  2004-01-16
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.
OpenGIS Location Services (OpenLS): Core Services [Part 3 Location Utility Service]  1.0  03-006r3  Marwa Mabrouk  2004-01-16
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.
OpenGIS Location Services (OpenLS): Core Services [Part 4 Presentation Service]  1.0  03-006r3  Marwa Mabrouk  2004-01-16
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.
OpenGIS Location Services (OpenLS): Core Services [Parts 1 Directory Service]  1.0  03-006r3  Marwa Mabrouk  2004-01-16
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.
OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]  1.0  03-006r3  Marwa Mabrouk  2004-01-16
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.
OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]  0.0  03-006r1  Marwa Mabrouk  2003-06-12
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.
OpenGIS Location Services (OpenLS): Core Services [Parts 5 Route Service]  1.0  03-006r3  Marwa Mabrouk  2004-01-16
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.
OpenGIS Location Services (OpenLS): Navigation Service [Part 6]  0.0  03-007r1  Tom Bychowski  2003-06-12
OpenGIS
OpenGIS Sensor Model Language (SensorML)  0.9.0 (1.0 beta 1)  05-086  Mike Botts  2005-11-21
The general models and XML encodings for sensors.
OpenGIS Sensor Planning Service Application Profile for EO Sensors  0.9.4  07-018  Philippe M  2007-05-17
This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain.
OpenGIS Sensor Planning Service Application Profile for EO Sensors  0.9.0  07-018r1  Philippe M  2007-08-15
This SPS EO profile document specifies at a lower level the interfaces and parameters for requesting information describing the capabilities of a Sensor Planning Service dedicated to the EO Sensor domain, 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 cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task.
OpenGIS Simple Features Implementation Specification for SQL  1.1  99-049  Keith Ryden  1999-05-05
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).
OpenGIS Styled Layer Descriptor (SLD) Implementation Specification  1.0  02-070  Bill Lalonde  2002-08-19
The SLD is an encoding for how the Web Map Server (WMS 1.0 & 1.1) specification can be extended to allow user-defined symbolization of feature data.
OpenGIS Web Coverage Service (WCS) Implementation Specification  1.1.0  06-083r8  John Evans  2007-02-06
The Web Coverage Service (WCS) supports electronic retrieval of geospatial data as "coverages"
OpenGIS Web Coverage Service (WCS) Implementation Specification  1.0  03-065r6  John Evans  2003-10-16
Extends the Web Map Server (WMS) interface to allow access to geospatial "coverages" that represent values or properties of geographic locations, rather than WMS generated maps (pictures).
OpenGIS Web Coverage Service (WCS) Implementation Specification (Corrigendum)  1.0.0  05-076  John Evans  2006-03-31
Extends the Web Map Server (WMS) interface to allow access to geospatial "coverages" that represent values or properties of geographic locations, rather than WMS generated maps (pictures).

The original document is available at: http://portal.opengeospatial.org/files/?artifact_id=3837
OpenGIS Web Coverage Service (WCS) Implementation Specification Corrigendum 1  1.1.1 c1  07-067r2  Arliss Whiteside, John Evans  2007-08-29
This version 1.1.1c1 of the Web Coverage Service (WCS) Specification supersedes previous
version 1.1.0 [OGC 06-083r8]. Technical changes from the version 1.0 include building on
the OGC Web Services Common Specification [OGC 06-121r3] and a substantially revised
Capabilities schema; new schemas and syntax for operation requests (GetCoverage,
DescribeCoverage); and integration with GML 3.1. The changes in WCS 1.1.1c1 from WCS
1.1.0 are summarized in [OGC 07-066r2].
OpenGIS Web Map Services - Application Profile for EO Products  0.1.0  06-093  Thomas H.G. Lankester  2006-10-24
The WMS configuration proposed in this profile is intended to support the interactive visualization and evaluation of Earth Observation (EO) data products. The profile sets out to describe a consistent Web Map Server (WMS) configuration that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data.
OpenGIS Web Service Common Implementation Specification  1.0  05-008c1  Arliss Whiteside  2005-05-03
This document specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. Those specifications currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). These common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses.
OWS Common Recomendation Paper  0.3.0  04-016r3  Arliss Whiteside  2004-06-17
This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses.
Recommended XML/GML 3.1.1 encoding of common CRS definitions  1.0.0  05-011  Arliss Whiteside  2005-01-28
This document recommends standard XML encodings of data defining some commonly-used coordinate reference systems, including geographic, projected, and vertical CRSs. These recommended encodings are based on GML 3.1.1. These common CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data.

The position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining some coordinate reference systems.

Recommended XML/GML 3.1.1 encoding of image CRS definitions  1.1.0  05-027r1  Arliss Whiteside  2005-04-13
This document recommends standard XML encodings of data defining monoscopic image coordinate reference systems. The scope of this encoding now includes unrectified and georectified images. The recommended CRSs for georectified images are recommended for multiple georectified images that are ready to be mosaicked together.

These recommended encodings are based on GML 3.1.1 and use XML Schemas. These image CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data.

The position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining image coordinate reference systems.

Recommended XML Encoding of CRS Definitions  2.1.0  03-010r9  Arliss Whiteside  2003-10-16
This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification.
Recommended XML Encoding of CRS Definitions  2.0.0  03-010r7  Arliss Whiteside  2003-05-21
This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC
Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general
than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification.
Reference Model for the ORCHESTRA Architecture  3.2  05-107  Thomas Uslander (Ed.)  2006-01-31
This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a specification framework for the design of ORCHESTRA-compliant service networks and provides a platform-neutral specification of its information and service viewpoints.
Reference Model for the ORCHESTRA Architecture  2.0  07-024  Thomas Uslander (Ed.)  2007-07-26
This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a platform-neutral specification of the ORCHESTRA Architecture and a specification framework for the design of ORCHESTRA-compliant service networks across all viewpoints.
Sensor Alert Service  0.2.0  06-028  Ingo Simonis  2006-04-05
A service providing active (push-based) access to sensor data.
SensorML  0.4d  02-026r1  Mike Botts  2002-04-22
The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances.
Sensor Model Language (SensorML) for In-situ and Remote Sensors  0.8.0 (1.0 beta)  04-019r2  Mike Botts  2004-11-02
The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances.
Sensor Model Language (SensorML) for In-situ and Remote Sensors  0.7  02-026r4  Mike Botts  2002-12-20
The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances.
Sensor Observation Service  0.1.4  05-088r1  Arthur Na, Mark Priest  2006-01-18
A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor 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.
Sensor Planning Service  0.3.0  05-089r1  Ingo Simonis  2005-12-01
The Sensor Planning Service (SPS) is intended to provide a standard interface to collection assets (i.e., sensors, and other information gathering assets) and to the support systems that surround them.
The SPS is designed to be flexible enough to handle a wide variety of configurations.
Styled Layer Descriptor Profile of the Web Map Service Implementation Specification  1.1  05-078  Dr. Markus M  2006-04-21
This Document specifies how a Web Map Service can be extended to allow user-defined styling. Different modes for utilizing Symbology Encoding for this purpose are discussed.
Style Management Service  0.0.9  03-031  William Lalonde  2003-01-20
This document describes the proposed system design for the OGC Style Management Service (SMS).
The SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects.
Styles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphic "images".
Style Management Services for Emergency Mapping Symbology  1.0  04-040  Bill Lalonde  2005-02-17
This document describes the proposed system design for the OGC Style Management Service (SMS).
The SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects.
Styles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphics.
Symbology Encoding Implementation Specification  1.1.0  05-077  Dr. Markus M  2006-04-21
This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data.
Symbology Management  0.2.1  05-112  Milan Trninic  2006-04-19
This document describes Symbology Management System which is a system closely related to OpenGIS Style Management Services (SMS) (described in the document OGC 04-040). Having in mind their identical purpose, the system described in this document will also be referred to as SMS.
The SMS manages styles and symbols and defines their use in the process of producing maps from source GML data.
Topic 0 - Overview  4.0  99-100r1  Cliff Kottman  1999-06-23
Introduction and roadmap to the Abstract specification.
Topic 2 - Spatial Referencing by Coordinates  2  03-073r1  Roel Nicolai  2003-10-16
Describes modelling requirements for spatial referencing by coordinates.
Topic 2 - Spatial Referencing by Coordinates  1.0.1  02-102  Roel Nicolai  2002-03-08
Describes modelling requirements for spatial referencing by coordinates. This document supplements and corrects ISO 19111. There has never been a motion to adopt 01-063r2. A motion was approved at the Dec 01 meeting in Vancouver to adopt 01-063r1
Topic 6 - The Coverage Type  6.0  00-106  Cliff Kottman, Charles Roswell  2000-04-18
Incomplete. This document normatively references parts of the previous version of AS Topic 6, document 00-106. Need to be updated to include Roswell Change Proposal (01-011), which includes 19123 and retains material from Topic 6, v6.
Topic 7 - Earth Imagery  4.0  99-107  Cliff Kottman  1999-03-31
This Topic Volume will provide essential and abstract models for technology that is already used widely (but not interoperably) across the GIS landscape. This technology properly depends on the more general technology that supports Coverages.
Topic 9 - Accuracy  4.0  99-109r1  Cliff Kottman, Arliss Whiteside  1999-03-30
Topic 9 has been combined into AS Topic 11
Units of Measure and Quantity Datatypes  0.2  01-044r2  John Bobbitt  2001-06-15
Common semantic for units of measurement to be used across all OGC specifications.
URNs of definitions in ogc namespace  1.0.0  05-010  Arliss Whiteside  2005-01-26
*** Superceded by 06-023r1 - Definition identifier URNs in OGC namespace ***
This Recommendation Paper specifies Universal Resource Names (URNs) for definitions in the
WCS Change Request: Support for WSDL & SOAP  0.1.0  04-049r1  Philippe Duschene, Jerome Sonnet  2005-04-22
The OpenGIS has been a precursor in Web Services matter, nevertheless, the pattern that has been used is not recognized by the industry as a standard "XML Web Services". The work done during the the OpenGIS Web Service 2 initiative has provided the OpenGIS with interfaces that use the XML-related technologies supported by the industry, as SOAP for the communication protocol, WSDL for the interface description language, and UDDI for registering and searching services.

This change proposal present the required change to the WCS specification to interoperate with the industry standards.

Web Coordinate Transformation Service  0.3.0  05-013  Arliss Whiteside, Markus U. M  2005-04-13
This document specifies the interface to a Web Coordinate Transformation Service (WCTS), which can be used by geospatial applications and other services. Transformation of geospatial data from one coordinate reference system (CRS) to another is frequently required when using data from different sources in one application. That is, geospatial data are often stored in different coordinate reference systems (CRSs). To use together data stored in different CRSs, such data must be transformed or converted into the same CRS. Not all applications or services are capable of directly performing such transformations.

This document specifies an "OGC Web Service" type of interface to a service that performs coordinate transformations. Such transformations include all the types of coordinate operations, including both "transformations" and "conversions". This service inputs digital features or coverages in one CRS and outputs the same features in a different CRS. The service inputs include identifications of the input and output CRSs, and optionally the coordinate transformation between these CRSs.

Web Coordinate Transformation Service  0.0.4  02-061r1  Andreas Poth, Markus Muller  2002-09-15
This document specifies the transformations of geo-spatial coordinates from one Coordinate Reference System (CRS) into another by means of a Web Service
Web Coverage Service  0.7  02-024  John Evans  2002-06-31
Extends the Web Map Server (WMS) interface to allow access to geospatial "coverages" that represent values or properties of geographic locations, rather than WMS generated maps (pictures).
Web Feature Service  1.0  02-058  Peter Vretanos  2002-05-17
The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS
Web Map Context Documents  1.0  03-036r2  Jean-Philippe Humblet  2003-06-12
Create, store, and use "state" information from a WMS based client application
Web Map Context Documents  0.1.4  02-066r1  Jean-Philippe Humblet  2002-08-29
States how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent manner.
Web Map Context Documents  0.1.7  03-036  Jean-Philippe Humblet  2003-01-21
Create, store, and use "state" information from a WMS based client application
Web Map Service  1.1.1  01-068r3  Jeff de La Beaujardiere  2002-04-18
Provides three operations protocols (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous.
Web Map Service  1.3.0  03-109r1  Jeff de La Beaujardiere  2004-02-18
Provides three operations (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous.
Web Map Service  1.1  01-047r2  Jeff de La Beaujardiere  2001-06-21
Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous.
Web Map Service  1.0  00-028  Allan Doyle  2000-04-19
Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous.
Web Notification Service  0.1.0  03-008r2  Ingo Simonis, Andreas Wytzisk  2003-04-21
The Web Notification Service (WNS) is the first asynchronous messaging service specified by OGC. At the moment, the WNS message schema is optimized to fulfil the needs of services supporting the use of sensors, like "Sensor Planning Service". Future work activities should include the adaptation of the message schema to the needs of other services.
Web Processing Service  0.4  05-007r4  Peter Schut, Arliss Whiteside  2005-09-16
This document specifies the interface to a Web Processing Service (WPS). A WPS can be configured to offer any sort of GIS functionality to clients across a network, including access to pre-programmed calculations and/or computation models that operate on spatially referenced data. A WPS may offer calculations as simple as subtracting one set of spatially referenced numbers from another (e.g., determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. The data required by the WPS can be delivered across a network, or available at the server.
Web Processing Service  0.2.1  05-007  Peter Schut  2005-01-24
This document is the specification for a Web Processing Service (WPS).
A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS).
Web Processing Service  0.3.0  05-007r2  Peter Schut  2005-06-17
A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). The calculation can be as simple as subtracting one set of spatially referenced numbers from another (e.g. determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model.

This specification is intended to provide a mechanism to identify the spatially-referenced data required by the calculation, initiate the calculation, and manage the output from the calculation so that it can be accessed by the client. The Web Processing Service is targeted at both vector and raster data based processing.

Web Registry Server  0.0.2  01-024r1  Louis Reich  2001-01-26
A Registry Service defines a common mechanism to classify, register, describe, search, maintain and access information about OGC Web resources. The OGC Service Registry provides the methods for managing a repository; a Registry Client is an application used to access the Registry.

Updated: 2008-07-20 16:47:09 EDT
print Printer Friendly