The purpose of this Standards Working Group is to update the SOS Version 1.0 Standard and to develop Version 2.0. It will achieve this objective by evaluating and processing the Change Requests listed in Section 3, ...
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.
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.
Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. In this discussion paper we try to extend the expressiveness of such annotations by including more sophisticated (semantic) descriptions.
Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma
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 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 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.
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.
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.
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.
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 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 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 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 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.
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 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 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.
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 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 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 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 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 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
The OpenGIS® Tiled Web Map Service Discussion Paper explains how the OpenGIS Web Map Service Standard (WMS) [http://www.opengeospatial.org/standards/wms] can be extended to allow fast response to a predefined set of tiled maps. It should be read in conjunction with the latest version WMS standard.
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
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.
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).
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.
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.
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.
Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos
The OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) provides guidance for creating a standard methodology for mapping geospatial domain information models to ebRIM [www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrim.pdf]. It also presents the results of mapping specific Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] and Feature Catalog domain models to ebRIM for use with OpenGIS Catalog Service Standard [http://www.opengeospatial.org/standards/cat] implementations in the OWS-4 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-4].
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 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.
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 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.
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].
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.
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.
This document explains how the Web Map Server (WMS 1.0  & 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.
Explains how Catalogue Services based on the HMA (Heterogeneous Earth Observation Missions Accessibility) Application Profile for the OGC Catalogue Services Specification v2.0.1 [OGC 04-021r3] are organized and implemented for the discovery, retrieval and management of Earth Observation products metadata.
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 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.
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.
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).
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.
This document specifies the interface to a Feature Portrayal Service (FPS), which applies styles to digital features to produce a map image. The styles applied are identified or specified by the client, and are applied to digital feature data retrieved from a Web Feature Service (WFS) identified by the client.
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.
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 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.
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 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.
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 Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph.
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 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 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.
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 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.
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.
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.
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 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.
There is a requirement to manage many different types of objects. These include styles, symbols and images. To satisfy this requirement, a repository interface is required. The intent of the Web Object Service interface is to provide a means to define this interface.
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 . 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.
OGC’s Interoperability Program is a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate specifications into OGC’s Specification Program, where they are formalized for public release. In OGC’s Interoperability Initiatives, an international team of technology providers&rsqu...
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 version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.
The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same...
The mission of the Workflow DWG is to establish a forum for describing, discussing, and solving any issues related to geospatial workflows. By geospatial workflow we mean any workflows that contain any or all processes that relate to geospatial processes and/or data. The primary focus of this DWG is to help individuals and organizations to identify smar...