You are here

Discussion Papers

Documents that present technology issues being considered in the Working Groups of the Open Geospatial Consortium Technical Committee. Their purpose is to create discussion in the geospatial information industry on a specific topic. These papers do not represent the official position of the Open Geospatial Consortium nor of the OGC Technical Committee. Schemas for some of these documents can be at the Discussion Paper Schema Repository.

The Starfish Fungus Language was developed in response to the high number of complaints addressing issues with the OGC standard Sensor Model Language, SensorML. Most complaints circled around the high flexibility of the language in combination with unnecessary abstractions of technical terms, e.g. every sensor is not a sensor but a process. Most beginners struggled with the composite pattern of those processes, as there is no well-defined rule what needs to be described where. As a beginner, it is almost impossible to write a simple sensor description without getting major guidance through the SensorML development team or other experts.

The OGC Catalog-Web Profile is a complex specification that implies usage of many concepts, such as ressources, metadata, registry, registry information model, harvesting, etc. This document is a user-friendly introduction to these concepts. It will help the understanding of the Catalog specification in general and of the Catalog Web profile with ebRIM in particular.

NetCDF (network Common Data Form) 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. Together, the interfaces, libraries, and format support the creation, access, and sharing of scientific data.

As a work item in the OWS4/Conformance and Interoperability Test and Evaluation (CITE) project, Northrop Grumman Information Technology (NGIT) provided an open source web services compliance engine. NGIT refers to this engine as the Test Evaluation And Measurement (TEAM) Engine. It executes scripts written in Compliance Test Language (CTL), a grammar also developed by NGIT. This IPR describes TEAM Engine in detail and provides information on how it was used in OWS-4/CITE.

This document describes the initial version of the WaterML messaging schema as implemented in version 1 of WaterOneFlow web services. It also lays out strategies for harmonizing WaterML with OGC specifications, the Observations and Measurement specification in particular.

A Web 3D Service (W3DS) is a portrayal service for three-dimensional geodata, such as landscape models, city models, textured building models, vegetation objects, and street furniture. Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates.

The Event Pattern Markup Language (EML) allows one to describe event patterns for event (stream) processing and analysis. It can be used to build multi stage filters for incoming events but also to derive higher information through combining and correlating multiple events. It can be applied on single events but is focused on handling of continuous event streams.

Feature Styling is based on a distributed computational platform that employs a number
of standard interfaces and encodings to allow for flexible, scalable and interoperable
management of symbology (styles and symbols) in the process of producing maps from
different kinds of data, most important being source GML data.

This document describes a Feature Type Catalogue extension package for the OGC® ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 05-025r3]. It defines the way an ISO 19110 [ISO 19110:2005] Feature Type Catalogue is included within a Registry, and provides an information model and stored queries for such an inclusion.

This document was developed during the FedEO - GEO AIP initiative of the OGC. It was contributed by the organizations involved in the Earth Observation and Natural Resources and Environment Domain Working Group (EO/NRE DWG) in the OGC Specification Program. The document describes recommendation for architecture and specification that enables interoperability

This document specifies a GML 3.2 Application Schema for frame image geopositioning metadata, for XML encoding of the georeferencing coordinate transformation parameters of an unrectified frame image. A frame image is one whose entire two-dimensional extent was collected at one time. A georeferencing coordinate transformation can transform position coordinates between a specific ground-based (or object) Coordinate Reference System (CRS) and the image CRS.

This GeoDRM engineering viewpoint document describes use cases and concepts for GeoDRM, as well as references to distributed computing concepts which are not GeoDRM sensu stricto but are required for any GeoDRM implementation.

This document extends the rights expression language (REL) to encompass the concerns of holders of geographic data and service resources to equally ensure their protection. This allows the geographic information market to operate with minimal constraints derived from need for the protection of intellectual property.

A Geolinked Data Access Service (GDAS) provides a way to publish and access data that refers to spatial features (e.g. population data for countries). A GDAS can expose data from non-GIS databases so that it can be manipulated and mapped with the aid of a Geolinking Service.

A Geolinking Service takes attribute data which refers to spatial features, and joins it to a geospatial dataset, so that it can be mapped by a WMS or used in a GIS. When a Geolinking Service uses data from a GDAS, and serves as a front end to a WMS, it enables real-time mapping of data stored in non-spatial databases.

The scope of this document is the update and the definition of GeoRM roles as a sub model of the GDI.NRW reference model (process model and architecture model). Key relationships are defined between these roles.

This Guide has been developed by the members of the Open Geospatial Consortium, Inc. to assist the global geospatial technology community in implementing standards-based geospatial portal solutions that are compatible with Spatial Data Infrastructures in every nation. We offer this document as a resource for rapid development and informed acquisition of portals and portal-exploiting applications that can plug and play with geospatial data and services in your organization and other organizations in your community and around the world.

The Semantic Web seeks to make the meaning as accessible as the material, by enabling connections - which are both logical and (machine) actionable - between concepts which a user presently understands and those which may be new and foreign. The Geospatial Semantic Web extends this capability to both content and concepts that are specifically spatial, temporal, and geographic in nature, giving both people and machines true access to a wider range of knowledge.

A GeoVideo Web Service (GVS) is a web service that facilitates the viewing of live and/or archived feeds from video cameras. The feeds may be composed of:
- A video stream
- Textual data in a caption stream (e.g. GPS data, camera states and characteristics, custom XML data, such as SensorMLTML)
- A combination of a video stream and associated textual data
The video streams of the feed may be viewed in the Windows Media Player. The textual data is extracted through scripting events that are generated as the caption stream is processed and displayed by the Windows Media Player.

This document summarizes the types of Coordinate Reference Systems (CRSs) that are recommended for use with grid (including image) coverages. This document specializes Best Practice Paper OGC 09-076r3 “Uses and Summary of Topic 2: Spatial referencing by coordinates” for grid coverages. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for defining and using ImageCRSs and other CRSs for grid coverages.

The ISO 19107 spatial schema, which is implemented by GML, is very complex. ISO
19107 defines an extensive list of geometries, geometric properties and operations –
many of which are not necessary for aeronautical information applications. In addition,
the ISO 19107 contains an exhaustive 3D geometry model that is probably not needed in
its entirety for AIXM either. Therefore, a GML profile for AIXM needs to be defined.
The objective of this document is to identify the elements of the AIXM-GML profile and
also to provide guidelines for the use of GML constructs in AIXM data sets.

This document investigates the potential for harmonisation of water data standards, with the goal of developing an OGC compliant standard for the exchange of water observation data. The work will be based on OGC‘s Observations and Measurements abstract model [10-004r2] . The goal is to create an O&M profile for the water domain. Development of the OGC compliant O&M profile will begin by examining the content and structure of existing standards and suggesting future methodology for developing a harmonised model for observation data. This approach will make use of existing standards where possible.
The focus of this document is in-situ style observations (which are generally related to water quantity). Ex-situ measurements, such as those common to measuring water quality, will be addressed in future work.
2 Normative

This Discussion Paper specifies image coordinate reference system (CRS) definitions designed for possible use by WCTS and WCS servers and clients, initially in the IH4DS thread of the OWS 2 interoperability initiative. This report specifies image CRS definitions suitable for both ungeorectified and georectified images, where an ungeorectified image can be georeferenced or not.

Special XML schemas have been created for individual data sets, based on ISO 19115 and a general schema for the RSE. However, a generalized metadata XML schema should be available where possible; it should not be necessary to create special schemas for each data set. ISO 19139 can serve as such a general XML implementation specification for 19115. This implementation needs to be tested in practice. In addition, the new ISO standards are incorporating much, if not all, of the metadata not in 19115 that the RSE contain. XML schemas for these metadata need to be developed that are based upon the abstract model in the ISO standards. All of these implementations need to be tested in practice. This Report describes such tests and the results. It also describes to what extent metadata on which the test metadata are based are supported by 19139, to what extent they are supported by metadata specified in the new ISO standards or the RSE, and to what extent new metadata elements are needed.

This Discussion Paper proposes model for license-based access control to SOAP services, based on OASIS SAML 2.0. This approach is a potential solution for license-based access control, which requires the possession of a valid license for getting access to a service. Use of digital licenses allow users to act on or with web services to which they are associated
This document re-uses content produced by the OGC GeoRM Common 1.0 Standards Working Group and combined that with the document OGC 10-125, which was posted to an internal OGC document archive (Pending Documents) but is not publicly available.
This document does not claim compliance to the GeoDRM reference model (ISO 19153), although the authors are not yet aware of any conflicts to it.

This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO/DIS 19131 (Geographic Information

This OGC discussion paper presents the results of the GeoPackage Plugfest. In this
initiative, participants had the opportunity to evaluate the compliance and interoperability
of software that produces and consumes GeoPackages containing tiled raster data.

This standard defines the version 3.0 of a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 standard. It thereby enables the interoperable definition of access rights / constraints using the XACML 3.0 language, processing model and policy schema but extends the ability to phrase conditions on geographic characteristics of subjects, resources and objects.
In that sense, a GeoXACML policy could restrict access to geospatial information, e.g. provided by OGC Web Services. However, a GeoXACML policy could also restrict access to non geospatial assets by stating restrictions for access based on the location of the user (or the mobile device used) trying to access the protected assets. Therefore, this standard applies to main stream IT.
For enabling processing of access control decisions based on geometry, Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core inherits by normative reference ISO 19125 which defines a geometry model and functions on geometry instances which enrich the XACML 3.0 specification.

This standard defines the version 3.0 of a valid GML 3.2.1 geometry encoding as defined in Geography Markup Language (GML) simple features profile (with Corrigendum) to be used with the GeoXACML 3.0 Core standard.
The use of this encoding extension to GeoXACML 3.0 Core enables the direct use of GML 3.2.1 encoded geometries into a GeoXACML 3.0 Policy, an Authorization Decision Request or in an Authorization Decision’s Obligation element. It thereby improves the performance of deriving access control decisions, where geometries are involved as existing GML 3.2.1 geometry encodings must not be transformed to Well Known Text (WKT) as supported by GeoXACML 3.0 Core. Furthermore, the use of this encoding extension simplifies the implementation of a Policy Enforcement Point as it must not provide the transformation functions from GML to WKT and vice versa.
This encoding extension has its normative base in Geography Markup Language (GML) simple features profile (with Corrigendum).

This specification defines the interfaces of the OGC (Geo)XACML Policy Administration Web Service (OGC (Geo)XACML PAWS or simply PAWS in the following) that supports the creation, modification, exchange, analysis, testing, transformation, encrypting and signing of XACML and GeoXACML encoded access control policies.
This draft specification was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This document presents the results of the work within add-on project of the OWS-9 Security and Services Interoperability (SSI) thread.
Please note that currently the document only contains the definition of the mandatory operations i.e. the basic conformance class. The writing of the sections describing the optional operations is still a to do. These sections need to define the following operations:
• AnalyzePolicyElement operation
• OptimizePolicyElement operation
• TransformPolicyElement operation
• TestPolicyElement operation
• EncryptPolicy operation
• SignPolicy operation
Suggested additions, changes, and comments on this report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.

Common semantics support the reference of features to the concept they represent and the integration of data proceed using the semantic framework such mappings provide. However there is no standard conceptual model for hydrologic feature identification. Different models of hydrologic processes, and different scales of detail, lead to a variety of information models to describe these features, and to different and mostly incompatible sets of feature identifiers.
This document describes requirements and a proposed design for a domain model of hydrologic features as a set of interrelated Application Schemas using the ISO 19109 General Feature Model,

This OGC discussion paper presents an OpenSearch query protocol extension for the
execution of correlation queries between different Search Feeds. Services that support the
OpenSearch Specification and Correlation extension defined in this document are called
OpenSearch Correlation Services. With the proposed extensions it will be possible to
execute distributed queries with correlation and search criteria defining the results
aggregation.

Applications using moving feature data, typically on vehicles and pedestrians, have
recently been rapidly increasing. Innovative applications are expected to require the
overlay and integration of moving feature data from different sources to create more
social and business values. Efforts in this direction should be encouraged by ensuring
smoother data exchange because handling and integrating moving feature data will
broaden the market for geo-spatial information. This discussion paper provides an
overview of some actual and potential geo-spatial applications using moving feature data
and the existing international standards or specifications on moving feature data handling.
It also summarizes the requirements set on the standards for moving feature data, and
finally proposes the development of a new OGC standard for moving features.

This OGC discussion paper provides a proposal for a temporality extension for the WFS
2.0 and FES 2.0 standard. It is based on the work of and experiences made in several
OWS test beds, in particular OWS-7, OWS-8 and OWS-9, Aviation threads and
discussions at the 2011 OGC TC meeting in Brussels, Belgium. It partially replaces and
advances the document “OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via
an OGC WFS 2.0” [4].

This document contains a description of the UGAS (UML Application Schema to GML ApplicationSchema conversion) tool development in the decision support services thread (GeoDSS) during the OWS-3 initiative.

The purpose of this document is to generally describe how the various OGC specifications may be used to address the needs of a large enterprise system. It highlights the key elements of the OWS-4 effort as they relate to web service architecture implementation at NGA and in the NSG. The goal is that this document will enable organization that interface with the NSG to understand how to produce and consume data and services in an interoperable environment.

This document lists the design principles and requirements for future versions of a potential architecture for integrating workflows and information models from Computer Aided Design and Building Information Modelling with the principles of the OGC Web Services Architecture.

This document lists the design principles, requirements, and experimental results for future versions of a potential OGC - UDDI (Universal Discovery, Description, and Integration) profile of the OGC Catalog Implementation Specification. Specifically, it describes the usage scenarios, workplan, and experimental results for discovery of OGC services (including registries) through the UDDI interface using SOAP (Simple Object Access Protocol) messaging protocols. The baseline for this experiment is the specification for UDDI version 2 and use of private UDDI implementations.

This report summarizes the work performed under the Canadian Geospatial Data Infrastructure Pilot. The purpose of this pilot was to test the utility of certain OGC standards, in particular the Geography Markup Language (GML) and Web Feature Service (WFS), in the implementation of a spatial data infrastructure. OGC documents 08-001 and 08-002 are more technical companions to this document.

This document describes an Application Profile for the Web Ontology Language (OWL) [W3C OWL] for CSW. It is intended to define a specification for how ontologies built using RDF and OWL may be included within an OGC CSW catalogue to semantically-enable the catalogue.

This Discussion Paper provides information on what has so far been called “Event Service” at OGC.
The presented work is supported by the European Commission through the ESS project (integrated project, contract number 217951) and the GENESIS project (integrated project, contract number 223996) .

This Discussion Paper documents results from the Interoperability Program CGDI Pilot and describes a suite of services that enable the sharing of geographic information across organizations for the purposes of: geographic database synchronization in support of a spatial data infrastructure; geographic database modification suggestions from trusted and un-trusted sources; and the transmission of geographic information in emergency notification events.
These services are called the Update Feed Service; Feedback Feed Service; and Emergency Alert Service respectively. Their information encodings are all based on the Atom Syndication Format, extended with GML and WFS Filter encodings to support geospatial requirements, and were implemented in the Canadian Geospatial Data Infrastructure Pilot.

This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO 19131 (Geographic Information – Data Product Specification).

This OGC® document describes and discusses the OWS-5 enhancements in the process of creating application schemas in support of the NSG from NGA data based on the GEOINT Structure Implementation Profile (GSIP) which has been based on the NSG Application Schema and accompanying NSG Entity Catalog.

The Sensor Event Service (SES) provides operations to register sensors at the service application and let clients subscribe for observations available at the service. The service performs filtering of sensor data (streams) based upon the filter criteria defined in these subscriptions. Filters can be applied on single observations but also on observation streams, potentially aggregating observations into higher-level information (which itself can be regarded as observation data). Whenever matches are discovered, a notification is sent to the subscriber, using asynchronous, push-based communication mechanisms.

The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org.

The OWS-2 Application Schema Development Discussion Paper describes the process for creating ISO 19109:2005 Application Schemas [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39891] in UML. It also describes the process used during the OWS-2 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-2] for creating GML [http://www.opengeospatial.org/standards/gml] Application Schemas from ISO 19109:2005 Application Schemas.
See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .

This document describes the results of an experiment addressing issues relating to the application workflow processing incorporating a variety of OGC specifications. It details the inputs provided to the Open Geospatial Consortium's (OGC) OWS-3 Testbed and the architecture of the testbed related to the ESA Service Support Environment (SSE).
It is a formal deliverable of work package 6610 of the Enhanced Service Infrastructure Technology (ESIT) project and is a joint Spacebel and Spot Image document.

This OGC Engineering Report describes the process of conflation, outlines a framework for conflation and conflation rules services within a service oriented architecture, and describes the implementation of conflation services during the OGC OWS-5 testbed.

This OGC document presents a summary of the Data View Architecture experiment conducted as part of the Geo-Processing Workflow (GPW) thread in the OWS-5 test bed. The main activities in this experiment were the storage of Data Views in an ebRIM Catalog and the discovery and use of those Data Views by an Integrated Client.

This document serves to describe the use of web processing services and the OGC Web Processing Service (WPS) in earth observation (EO) applications. It provides an overview of web processing services and a description of developments related to earth observation implementations of OGC WPS in the OGC OWS-5 testbed.

This OGC® document describes the Workflow Architecture developed in support of Geoprocessing Workflow and Sensor Web Enablement threads of OWS-5. This information includes the overall architecture description, concepts, and issues. It also provides detail on the Conflation Workflow created as an example implementation for geoprocessing in a workflow. This document establishes a sample architecture and associated lessons learned as general guidance.

This document describes a License Broker Service (LB-Service) as specified and implemented in the OWS-5 test bed. The LB-Service provides configurable license models, which may contain configuration parameters to be defined by the licensee. The setting of these parameters affects the actual license to be created by the LB-Service.

This Discussion Paper is about the use of KML, an encoding used to express geographic annotation and visualization on existing or future web-based online maps (2d) and earth browsers (3d). KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.

This OGC document represents an OWS-5 SWE thread Engineering Report on sub-setting georeferencable imagery. It discusses how to handle georeferencable imagery in the JPEG2000 format as well as using JPIP within the WCS-T and the SWE set of services.

Image Handling is a thread in the OGC Web Services 1.2 (OWS1.2). This document defines the system design for Image Handling in OWS1.2. The system design responds to the requirements in OWS 1.2 Image Handling Requirements. The system design specifies two main services: Image Archive Service and Image Catalogue Service. Interfaces for these two services are defined using previously defined OWS service interfaces.

This document was developed as part of the Image Handling Thread of the OGC Web Services Initiative Phase 1 Thread Set 2 (OWS 1.2). This document specified the requirements for the image handling functions to be supported by draft specifications prepared under that thread.

This OGC document reports the work that occurred in the OWS2 Test Bed Common Architecture thread. This thread focused on the use of UDDI/WSDL/SOAP in the OGC Web Services architecture. It also provides guidelines for the use of these technologies.

In this experiment, the retrieval time of GML features from a Web Feature Service (WFS) to a WFS client will be studied by varying certain control parameters including methods of encoding and compression. Four different control parameters including encoding format, data set size, bandwidth, and feature type will be varied to test the relative performance in each case.

Part 1 of this investigation is conducted by Galdos Systems. In this part, the OWS3 MSD3 geometric description is extended to include a topology encoding as defined by the MSD3 schema. Part 2 (Clause 6.2) of this investigation is conducted by Intergraph Corp. and describes and discusses the impacts of encoding topology within the GML data.

The objective of the proposed temporal extensions to the WFS is to enable temporal/geospatial queries using the GML temporal types against GML dynamic features employing either the snapshot or time history model (time slices).

The scope of this document is to capture considerations and recommendations on approaches for supporting georeferenceable imagery within the OGC encodings and web services. Georeferenceable imagery is typically imagery coming from a remote sensor that has not been previously geo-rectified, resampled, or regridded. Georeferenceable imagery must be accompanied with information sufficient to allow georectification of the imagery.

This standard specifies the behavior 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 and transaction operations. 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. Retrieval operations allow features to be retrieved from the opaque underlying data store based upon constraints on spatial and non-spatial feature properties defined by the client. Transaction operations allow features to be created, changed and deleted from the opaque underlying data store.

This document defines a messaging framework to conduct communications between the OGC web services. It is independent of any transport protocol and any messaging encoding. By using the framework, the service designer could focus only on the message definitions and messaging flows for every action supported by the service, without worry on the messaging transport and delivery. The framework should considerably simplify the implementations of the OGC web services and should enable service chaining.

This document reports the considered SANY best practice for using OGC standards to provide generic fusion processing services. Concrete case studies are documented and a detailed appendix is provided with example of XML request and responses.

This Discussion paper introduces the Sensor Instance Registry (SIR), a web service interface for managing the metadata and status information of sensors. Furthermore this service is capable of automatically harvesting sensor metadata, transforming the collected metadata sets into a data model compatible to OGC Catalogs and to push harvested metadata into OGC Catalog instances.

This document presents the Sensor Interface Descriptor (SID) schema that enables the declarative description of sensor interfaces, including the definition of the communication protocol, sensor commands, processing steps and metadata association. This schema is designed as a profile and extension of SensorML. Based on this schema, SID interpreters can be implemented, independently of particular sensor technology, which are able to translate between sensor protocol and SWE protocols. They establish the connection to a sensor and are able to communicate with it by using the sensor protocol definition of the SID. SID instances for particular sensor types can be reused in different scenarios and can be shared among user communities. The ability of an SID interpreter to connect sensors and Sensor Web services in an ad hoc manner based on the sensor’s SID instance is a next step towards realizing sensor plug & play within the Sensor Web.

This document describes the mapping of description of sensors using SensorML specification 1.0 [OGC 07-000] to an ebRIM structure within an OGCTM 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].
In addition this document contains the definition of a SensorML profile for Discovery which defines a minimum set of metadata to be provided within SensorML documents as well as the structure this data shall possess. This profile is based on the OGC OWS- 6 SensorML Profile for Discovery Engineering Report [OGC 09-033].
It defines the way sensors metadata are organized and implemented in the Catalogue for discovery, retrieval and management.

This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena.

This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena.

This discussion paper contains the material that is still relevant from Section 6 (or Appendix A) of the previous version 4 (document OGC 99-107) of OGC Abstract Specification Topic 7, titled "The Earth Imagery Case". That version of Topic 7 has now been superseded by a new version with the same title.
In addition, some terminology has been revised to be consistent with the terminology now used in Topic 16: Image Coordinate Transformation Services. Specifically, the previous term "real-time image geometry model" has been changed to "approximate image geometry model". Also, the previous name "Universal Real-Time Image Geometry Model" has been changed to "Universal Image Geometry Model".

This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC.

Specification of a generic service-oriented architecture integrating the access to, the management and the processing of sensor-related information based upon the emerging standards of the Open geospatial Consortium (OGC), and resulting from the requirements analysis of diverse application domains such as maritime risk management, observation of geo-hazards and monitoring of air quality.

The OGC Web Services, Phase 5 (OWS-5) Testbed was an initiative of the OGC Interoperability Program (IP). The primary focus of an IP activity is to collaboratively extend and demonstrate OGC‘s baseline for geospatial interoperability.

This document summarizes recommendations for extending geospatial standards with regard to time-varying information. These proposals are the result of the National Technology Alliance program called Temporal Evaluation and Assessment (TEA).

The OGC Trusted Geo Services Interoperability Program Report (IPR) provides guidance for the exchange of trusted messages between OGC Web Services and clients for these services. It describes a trust model based on the exchange and brokering of security tokens, as proposed by the OASIS WS-Trust specification [http://docs.oasis-open.org/ws-sx/ws-trust/200512].

The Uncertainty Markup Language (UncertML) is an XML encoding for the transport and storage of information about uncertain quantities, with emphasis on quantitative representations based on probability theory.

This document first discusses the uses for data sharing, and then provides a brief summary, of OGC Abstract Specification Topic 2: Spatial referencing by coordinates. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for using Coordinate Reference Systems (CRSs).

This document describes an information model for exchanging rating tables, or rating
curves, that are used for the conversion of related hydrological phenomenon. It also
describes a model describing the observations that are used to develop such relationships,
often referred to as gauging observations.
The information model is proposed as a second part of the WaterML2.0 suite of
standards, building on part 1 that addresses the exchange of time series1.

This discussion paper investigates the possible uses of NetCDF as a representation of WaterML timeseries data. The work is largely based on the WaterML 2.0 standard for timeseries, the NetCDF core and extensions standards and the CF-NetCDF and ADCC conventions.

This Discussion Paper describes an interface specification for a web coordinate transformation service that now builds on version 1.1 of the OWS Common Specification [OGC 06-121r3]. All versions of this document specify an

This extension of the WCS standard specifies an Information Community data model with the related encoding that may optionally be implemented by WCS servers. This extension specification allows clients to evaluate, request and use data encoded in CF-netCDF3 format from a WCS server.
This document is an extension of the Web Coverage Service (WCS) 1.1 Corrigendum 2 (version 1.1.2) Implementation Standard [OGC 07-067r5]. With small changes, this extension is expected to also apply to WCS 1.2.

The Web Image Classification Service (WICS) supports classification of digital images. A digital image is composed of pixel values organized into one or more two-dimensional arrays. The two dimensions of an image represent two axes in space based on a spatial coordinate reference system. The dimensions of the different 2-D arrays comprising an image must be the same and represent exactly the same spatial locations.

The following document contains best practices for identifying input data formats for the OGC WPS 1.0.0. It was created due to a lack of interoperability between different WPS implementation based on non-standardized input identifiers.

This document explains how the Web Map Server (WMS 1.0 [1] & 1.1 [2,3]) specification can be extended to allow map animations that move in space over time. It should be read in conjunction with the latest version WMS specification.

This change proposal is an outcome of the Common Architecture thread of the OpenGIS Web Service 2 initiative. The aim is to add support for a standard WSDL description of the WMS interface in version 1.3.1.

This part of the Web Map Service (WMS) specification applies to those clients and servers which allow operation request encodings that are more complex than those permitted by the basic keyword/value encoding defined in WMS Part 1 [17]. Part 2 only describes the encoding of the request messages using Extensible Markup Language (XML); all other aspects of the Web Map Service are fully defined in Part 1.

This document specifies a) XML schemas for providing functional and non-functional service descriptions of OGC Web Services (OWS), b) an URN namespace for identifying exposed and measurable service properties of OWS and c) a DSL for defining and evaluating service level guarantees.