OpenGIS® Standards

Implementation Standards are different from the Abstract Specification. They are written for a more technical audience and detail the interface structure between software components. An interface specification is considered to be at the implementation level of detail if, when implemented by two different software engineers in ignorance of each other, the resulting components plug and play with each other at that interface.

Any Schemas (xsd, xslt, etc) that support an approved Implementation Standard can be found in the official OGC Schema Repository.

Document Title (click to download)	Version	Document #	Editor	Date
CSW-ebRIM Registry Service – Part 2: Basic extension package	1.0.1	07-144r4	Richard Martell	2009-02-05
Incorporates Corrigendum 1 (OGC 08-102r1).
CSW-ebRIM Registry Service – Part 3: Abstract Test Suite	1.0.1	08-103r2	Richard Martell	2009-02-05
This document is an abstract test suite (ATS): a compendium of abstract test cases pertaining to implementations of the CSW-ebRIM 1.0 catalogue profile. It provides a basis for developing an executable test suite (ETS) to verify that the implementation under test (IUT) conforms to all relevant functional specifications. While passing all of the conformance tests defined in this ATS provides some assurance of overall functional correctness, it cannot guarantee that an implementation is faultless.
CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW	1.0.1	07-110r4	Richard Martell	2009-02-05
This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards.
GeoAPI 3.0 Implementation Standard	3.0	09-083r3	Adrian Custer	2011-04-25
The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards.
Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum	1.0.1	11-017	Andreas Matheus, Jan Herrmann	2011-05-12
The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]).
GeoXACML Implementation Specification - Extension A (GML2) Encoding	1.0	07-098r1	Andreas Matheus	2008-02-23
This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard.
GeoXACML Implementation Specification - Extension B (GML3) Encoding	1.0	07-099r1	Andreas Matheus	2008-02-23
This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries.
Observations and Measurements - XML Implementation	2.0	10-025r1	Simon Cox	2011-03-22
This standard specifies an XML implementation for the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156), including a schema for Sampling Features. This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard. More specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.
OGC®: Open GeoSMS Standard - Core	1.0	11-030r1	Kuan-Mei Chen, Carl Reed	2012-01-19
The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS).
OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products	1.0.0	06-131r6	Frédéric Houbie, Lorenzo Bigagli	2010-02-10
This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management.
OGC® PUCK Protocol Standard	1.4	09-127r2	Tom O’Reilly	2012-01-25
This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself.
OGC® Sensor Planning Service Implementation Standard	2.0	09-000	Ingo Simonis, Johannes Echterhoff	2011-03-28
The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.
OGC® SWE Common Data Model Encoding Standard	2.0	08-094r1	Alexandre Robin	2011-01-04
This standard defines low level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework. These models allow applications and/or servers to structure, encode and transmit sensor datasets in a self describing and semantically enabled way.
OGC® WCS 2.0 Interface Standard - Core	2.0	09-110r3	Peter Baumann	2010-10-27
This document specifies how a Web Coverage Service (WCS) offers multi-dimensional coverage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementation. This document indicates which extensions, at a minimum, need to be considered in addition to this core to allow for a complete WCS implementation.
OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension	1.0	09-147r1	Peter Baumann	2010-10-27
This document specifies how Web Coverage Service (WCS) clients and servers can communicate over the Internet using HTTP GET with key/value pair (KVP) encoding.
OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension	1.0	09-148r1	Peter Baumann	2010-10-27
This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding.
OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension	1.0	09-149r1	Peter Baumann	2010-10-27
This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding.
OGC KML	2.2.0	07-147r2	Tim Wilson	2008-04-14
KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user's navigation in the sense of where to go and where to look.
OGC KML 2.2 – Abstract Test Suite	1.0.0	07-134r2	Richard Martell	2008-04-14
This document is an abstract test suite (ATS): a compendium of abstract test cases that provide a basis for verifying the structure and content of OGC KML 2.2 instance documents. Three conformance levels are defined; each level builds on the preceding ones: * Level 1 - includes test cases covering all requirements to be satisfied by a minimally conformant KML document; * Level 2 - as for Level 1, plus test cases addressing recommended requirements; * Level 3 - as for Level 2, plus test cases covering suggested constraints that are informative in nature.
OGC Location Services (OpenLS): Tracking Service Interface Standard	1.0.0	06-024r4	CS Smyth	2008-09-08
The OpenGIS Tracking Service Interface Standard supports a very simple functionality allowing a collection of movable objects to be tracked as they move and change orientation. The standard addresses the absolute minimum in functionality in order to address the need for a simple, robust, and easy-to-implement open standard for geospatial tracking.
OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0	1.0	10-090r3	Ben Domenico	2011-04-05
This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena. NetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data.
OGC Web Service Common Implementation Specification	2.0.0	06-121r9	Arliss Whiteside Jim Greenwood	2010-04-07
This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses.
OpenGIS® City Geography Markup Language (CityGML) Encoding Standard	1.0.0	08-007r1	Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel	2008-08-20
This document is an OpenGIS® Encoding Standard for the representation, storage and exchange of virtual 3D city and landscape models. CityGML is implemented as an application schema of the Geography Markup Language version 3.1.1 (GML3). CityGML models both complex and georeferenced 3D vector data along with the semantics associated with the data. In contrast to other 3D vector formats, CityGML is based on a rich, general purpose information model in addition to geometry and appearance information. For specific domain areas, CityGML also provides an extension mechanism to enrich the data with identifiable features under preservation of semantic interoperability.
OpenGIS® Georeferenced Table Joining Service Implementation Standard	1.0	10-070r2	Peter Schut	2010-11-22
This document is the specification for a Table Joining Service (TJS). This OGC standard defines a simple way to describe and exchange tabular data that contains information about geographic objects.
OpenGIS® SWE Service Model Implementation Standard	2.0	09-001	Johannes Echterhoff	2011-03-21
This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard.
OpenGIS® Web Map Tile Service Implementation Standard	1.0.0	07-057r7	Joan Masó, Keith Pomakis and Núria Julià	2010-04-06
This Web Map Tile Service (WMTS) Implementation Standard provides a standard based solution to serve digital maps using predefined image tiles. The service advertises the tiles it has available through a standardized declaration in the ServiceMetadata document common to all OGC web services. This declaration defines the tiles available in each layer (i.e. each type of content), in each graphical representation style, in each format, in each coordinate reference system, at each scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares the communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles.
OpenGIS Catalogue Service Implementation Specification	2.0.2	07-006r1	Nebert, Whiteside, Vretanos, editors	2007-04-20
The OpenGIS® Catalogue Services Interface Standard (CAT) supports the ability to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. Providers of resources use catalogues to register metadata that conform to the provider's choice of an information model; such models include descriptions of spatial references and thematic information. Client applications can then search for geospatial data and services in very efficient ways. See also the OGC Catalogue 2.0 Accessibility for OWS-3 Discussion Paper [http://www.opengeospatial.org/standards/dp], the OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) [www.opengeospatial.org/standards/dp] and the OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW (Best Practice) [http://www.opengeospatial.org/standards/bp].
OpenGIS Coordinate Transformation Service Implementation Specification	1.0	01-009	Martin Daly	2001-01-12
The OpenGIS® Coordinate Transformation Service Standard (CTS) provides a standard way for software to specify and access coordinate transformation services for use on specified spatial data. This standard addresses a key requirement for overlaying views of geodata (“maps”) from diverse sources: the ability to perform coordinate transformation in such a way that all spatial data are defined relative to the same spatial reference system.
OpenGIS Filter Encoding 2.0 Encoding Standard	2.0	09-026r1	Panagiotis (Peter) A. Vretanos	2010-11-22
This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. These components are modular and intended to be used together or individually by other standards which reference this International Standard.
OpenGIS Geographic Objects Implementation Specification	1.0.0	03-064r10	Greg Reynolds	2005-05-04
The OpenGIS® Geographic Objects Interface Standard (GOS) provides an open set of common, lightweight, language-independent abstractions for describing, managing, rendering, and manipulating geometric and geographic objects within an application programming environment. It provides both an abstract object standard (in UML) and a programming-language-specific profile (in Java). The language-specific bindings serve as an open Application Program Interface (API).
OpenGIS Geography Markup Language (GML) Encoding Standard	3.2.1	07-036	Clemens Portele	2007-10-05
The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data. A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it. Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .
OpenGIS Geography Markup Language (GML) Encoding Standard	3.2.1	07-036	Clemens Portele	2007-10-05
The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data. A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it. Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .
OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification	1.0.0	05-047r3	Martin Kyle, David Burggraf, Sean Forde, Ron Lake	2006-01-20
The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard [http://www.opengeospatial.org/standards/gml] is used within JPEG 2000 [www.jpeg.org/jpeg2000/] images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file. See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .
OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture	1.2.1	06-103r4	John Herring	2010-08-04
The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons.
OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option	1.2.1	06-104r4	John Herring	2010-08-04
The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons.
OpenGIS Location Service (OpenLS) Implementation Specification: Core Services	1.2.0	07-074	Marwa Mabrouk	2008-09-08
This OpenGIS Interface Standard defines OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform.
OpenGIS Location Services (OpenLS): Part 6 - Navigation Service	1.0.0	08-028r7	Gil Fuchs	2008-09-04
This OpenGIS Implementation Standard defines the interfaces for OpenGIS Location Services (OpenLS): Part 6 - Navigation Service (formerly the Full Profile of the Route Determination Service), which is part of the GeoMobility Server (GMS), an open location services platform.
OpenGIS Sensor Model Language (SensorML)	1.0.0	07-000	Mike Botts	2007-07-24
The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. For additional information on SensorML, see http://www.botts-inc.net/vast.html
OpenGIS Sensor Observation Service	1.0.0	06-009r6	Arthur Na, Mark Priest	2008-02-13
The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.
OpenGIS Simple Features Implementation Specification for CORBA	1.0	99-054	Peter Ladstaetter	1999-06-02
The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc).
OpenGIS Simple Features Implementation Specification for OLE/COM	1.1	99-050	TC Chair	1999-05-18
The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc).
OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification	1.1.0	05-078r4	Markus Lupp	2007-08-14
The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f] and coverage[http://www.opengeospatial.org/ogc/glossary/c] data. SLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. The OpenGIS® Symbology Encoding Standard (SE) [http://www.opengeospatial.org/standards/symbol] provides this language, while the SLD profile of WMS enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols.
OpenGIS Symbology Encoding Implementation Specification	1.1.0	05-077r4	Dr. Markus Mueller	2007-01-18
The OpenGIS® Symbology Encoding Standard (SES) defines an XML language for styling information that can be applied to digital geographic feature and coverage data. SE is independent of any OGC Web Services descriptions and could therefore be used to describe styling information in non-networked systems such as desktop geographic information systems.
OpenGIS Transducer Markup Language	1.0.0	06-010r6	Steve Havens	2007-07-02
The OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system. The protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations. The sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.
OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard	1.0.0	08-068r2	Peter Baumann	2009-03-25
The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional gridded coverages (see: http://www.opengeospatial.org/ogc/glossary/c ) representing sensor, image, or statistics data. Services implementing this language provide access to original or derived sets of geospatial coverage information, in forms that are useful for client-side rendering, input into scientific models, and other client applications. Further information about WPCS can be found at the WCPS Service page of the OGC Network(see: http://www.ogcnetwork.net/wcps).
OpenGIS Web Coverage Service (WCS) - Processing Extension (WCPS)	1.0.0	08-059r3	Peter Baumann	2009-03-25
The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional gridded [[http://www.opengeospatial.org/ogc/glossary/c | coverages]] representing sensor, image, or statistics data. Services implementing this language provide access to original or derived sets of geospatial coverage information, in forms that are useful for client-side rendering, input into scientific models, and other client applications. Further information about WPCS can be found at the [[http://www.ogcnetwork.net/wcps | WCPS Service]] page of the OGC Network.
OpenGIS Web Feature Service (WFS) Implementation Specification	1.1.0	04-094	Peter Vretanos	2005-05-03
The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: • Get or Query features based on spatial and non-spatial constraints • Create a new feature instance • Get a description of the properties of features • Delete a feature instance • Update a feature instance • Lock a feature instance The specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used.
OpenGIS Web Feature Service (WFS) Implementation Specification (Transactional)	1.1.0	04-094	Peter Vretanos	2005-05-03
The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: • Get or Query features based on spatial and non-spatial constraints • Create a new feature instance • Get a description of the properties of features • Delete a feature instance • Update a feature instance • Lock a feature instance The specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used.
OpenGIS Web Feature Service (WFS) Implementation Specification with XLinks	1.1.0	04-094	Panagiotis (Peter) A. Vretanos	2009-06-26
The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: • Get or Query features based on spatial and non-spatial constraints • Create a new feature instance • Get a description of the properties of features • Traverse XLinks The specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used.
OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142)	2.0	09-025r1	Panagiotis (Peter) A. Vretanos	2010-11-02
This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions. Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. Query operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties. Locking operations allow exclusive access to features for the purpose of modifying or deleting features. Transaction operations allow features to be created, changed, replaced and deleted from the underlying data store. Stored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values.
OpenGIS Web Map Context Implementation Specification	1.1	05-005	Jerome Sonnet	2005-05-03
This document is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter "WMS 1.1.1." WMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a "Web Map Context Document," or simply a "Context." Presently, context documents are primarily designed for WMS bindings. However, extensibility is envisioned for binding to other services. A Context document includes information about the server(s) providing layer(s) in the overall map, the bounding box and map projection shared by all the maps, sufficient operational metadata for Client software to reproduce the map, and ancillary metadata used to annotate or describe the maps and their provenance for the benefit of human viewers. A Context document is structured using eXtensible Markup Language (XML). Annex A of this specification contains the XML Schema against which Context XML can be validated.
OpenGIS Web Map Service (WMS) Implementation Specification	1.3.0	06-042	Jeff de La Beaujardiere	2006-03-15
The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not.
Ordering Services Framework for Earth Observation Products Interface Standard	1.0	06-141r6	Daniele Marchionni, Stefania Pappagallo	2012-01-09
This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products.
Web Coverage Service (WCS) - Transaction operation extension	1.1.4	07-068r4	Arliss Whiteside	2009-01-15
This extension of the WCS standard specifies an additional Transaction operation that may optionally be implemented by WCS servers. This Transaction operation allows clients to add, modify, and delete grid coverages that are available from a WCS server. The Transaction operation request references or includes the new or modified coverage data, including all needed coverage metadata.
Web Coverage Service (WCS) Implementation Standard	1.1.2	07-067r5	Arliss Whiteside	2008-04-29
The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a standard interface and operations that enables interoperable access to geospatial "coverages" [http://www.opengeospatial.org/ogc/glossary/c]. The term "grid coverages" typically refers to content such as satellite images, digital aerial photos, digital elevation data, and other phenomena represented by values at each measurement point.
Web Processing Service	1.0.0	05-007r7	Peter Schut	2007-10-05
The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server.