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.
View this List Sorted by Date
| Document Title (click to download) | Version | Document # | Editor | Date |
|---|---|---|---|---|
3D-Symbology Encoding Discussion Draft |
0.0.1 | 09-042 | Steffen Neubauer, Alexander Zipf | 2009-10-13 |
| This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile. | ||||
Access Control & Terms of Use (ToU) "Click-through" IPR Management |
1.0.0 | 05-111r2 | Roland M. Wagner | 2006-05-09 |
| This document demonstrats a number of functional capabilities related to rights management (Terms-of-Use, Authentication, content services) that need to be described and chained. | ||||
Catalog 2.0 Accessibility for OWS3 |
0.0.1 | 05-084 | Vincent Delfosse | 2006-05-09 |
| 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. | ||||
CF-netCDF Encoding Specification |
0.1.0 | 09-122 | Ben Domenico | 2009-10-13 |
| 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. | ||||
Compliance Test Engine Interoperability Program Report |
1.0 | 07-012 | Jennifer Marcus, Chuck Morris | 2007-09-04 |
| 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. | ||||
CUAHSI WaterML |
0.3.0 | 07-041r1 | Ilya Zaslavsky, David Valentine, Tim Whiteaker | 2007-05-30 |
| 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. | ||||
Discussions, findings, and use of WPS in OWS-4 |
0.9.1 | 06-182r1 | Steven Keens | 2007-06-06 |
| This document reviews the material discussed during the OWS-4 project, describes the WPS processes deployed in the workflows, and offers suggestions to the OGC to move forward with the WPS. | ||||
EO Application Profile for CSW 2.0 |
1.4 | 06-079r1 | Marc Gilles | 2006-06-06 |
| 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. | ||||
Event Pattern Markup Language (EML) |
0.3.0 | 08-132 | Thomas Everding, Johannes Echterhoff | 2008-11-05 |
| 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 Portrayal Service |
0.0.30 | 05-110 | Arliss Whiteside, Bill Woodward, co-editor | 2006-04-19 |
| 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. | ||||
Feature Styling IPR |
0.4.1 | 06-140 | Dr. Markus M | 2007-06-08 |
| 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. |
||||
Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 |
0.1 | 07-172r1 | Kristin Stock | 2008-05-13 |
| 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. | ||||
FedEO Pilot Engineering Report |
0.4 | 07-152 | Corentin Guillo | 2008-01-21 |
| 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 | ||||
Frame image geopositioning metadata GML 3.2 application schema |
0.0.0 | 07-032 | Arliss Whiteside | 2007-06-06 |
| 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. | ||||
GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report |
0.0.1 | 07-004 | Panagiotis (Peter) A. Vretanos | 2007-05-07 |
| This OpenGIS(r) document describes the API for two web services capable of generating several simplified data formats including GeoRSS and the Basic XML Feature Schema (BXFS). |
||||
GeoDRM Engineering Viewpoint and supporting Architecture |
0.9.2 | 06-184r2 | Christian Elfers, Roland M. Wagner | 2007-08-14 |
| 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. | ||||
Geographic information - Rights expression language for geographic information - Part xx: GeoREL |
0.9.0 | 06-173r2 | John Herring | 2007-01-25 |
| 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. | ||||
Geolinked Data Access Service |
0.9.1 | 04-010r1 | Peter Schut | 2004-05-04 |
| 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. | ||||
Geolinking Service |
0.9.1 | 04-011r1 | Peter Schut | 2004-05-04 |
| 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. | ||||
GeoRM Role Model |
0.3.0 | 09-123 | Roland M. Wagner | 2009-10-13 |
| 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. | ||||
Geospatial Portal Reference Architecture |
0.2 | 04-039 | Louis Rose | 2004-09-22 |
| 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. | ||||
Geospatial Semantic Web Interoperabiltiy Experiment Report |
0.5.0 | 06-002r1 | Joshua Lieberman | 2006-08-21 |
| 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. | ||||
Geo Video Web Service |
0.0.9 | 05-115 | Joe Lewis | 2006-03-28 |
| 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. |
||||
GML 3.2 implementation of XML schemas in 07-000 |
1.0.1 | 08-127 | Simon Cox | 2008-08-25 |
GML 3.2 implementation of XML schemas in 07-002r3 |
1.0.1 | 08-129 | Simon Cox | 2009-03-06 |
GML 3.2 implementation of XML schemas in 07-022r1 |
1.0.1 | 08-128 | Simon Cox | 2009-03-06 |
GML Performance Investigations by CubeWerx |
1.0.0 | 05-050 | Craig Bruce | 2006-05-02 |
| This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways. | ||||
GML Point Profile |
0.4 | 05-029r4 | Ron Lake, Carl Reed, George Percivall | 2005-08-29 |
| This document defines a profile of the Geography Markup Language (GML) for a point geometry. Attention is drawn to the fact that this is a profile of GML version 3.1.1. | ||||
Grid coverage Coordinate Reference Systems (CRSs) |
0.3.2 | 09-085r2 | Arliss Whiteside | 2009-10-13 |
| 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. | ||||
Image CRSs for IH4DS |
0.1.0 | 05-014 | Arliss Whiteside | 2005-01-31 |
| 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. | ||||
Imagery Metadata |
1.0 | 05-015 | Barry Schlesinger | 2005-01-27 |
| 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. | ||||
Integrated Client for Multiple OGC-compliant Services |
0.1.18 | 03-021 | Jeff Yutzler | 2003-01-20 |
| Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services | ||||
Local MSD Implementation Profile (GML 3.2.1) |
0.7.0 | 07-027r1 | Clemens Portele | 2007-05-25 |
| 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 | ||||
OGC® Canadian Geospatial Data Infrastructure Summary Report |
0.0.9 | 08-000 | Raj SIngh | 2008-04-29 |
| 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. | ||||
OGC® Canadian Geospatial Data Infrastructure WFS and GML Best Practices |
0.0.9 | 08-002 | Peter Rushforth | 2008-04-29 |
| This document gives guidelines and recommendations for administrators, users and implementers of Web Feature Services serving Geography Markup Language encoded response documents. | ||||
OGC® Catalogue Services – OWL Application Profile of CSW |
0.3.0 | 09-010 | Kristin Stock | 2009-07-27 |
| 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. | ||||
OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot |
0.0.9 | 08-001 | Raj Singh | 2008-04-29 |
| 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. |
||||
OGC® OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1) |
0.0.2 | 08-077 | Clemens Portele | 2008-07-02 |
| 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). | ||||
OGC® OWS-5 ER: GSIP Schema Processing |
0.0.3 | 08-078r1 | Clemens Portele | 2008-07-08 |
| 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. | ||||
OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W |
0.1.7 | 07-038 | Nicolas Lesage, Marie-Lise Vautier | 2007-06-06 |
| This document extends the ebRIM application profile of CS-W for the cataloguing of ISO 19115 and ISO 19119 compliant metadata. | ||||
OGC OWS-5 Engineering Report on WCPS |
0.9.0 | 07-166r2 | Peter Baumann | 2008-08-04 |
| This document represents the Engineering Report for the WCPS activity within the OWS-5 SWE thread. It summarizes tasks and outcomes. | ||||
OGC Web Services (OWS) 3 UGAS Tool |
0.0.3 | 05-118 | Clemens Portele, Rafael Renkert | 2006-04-28 |
| 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. | ||||
OGC Web Services Architectural Profile for the NSG |
1.3 | 07-009r3 | Shayne Urbanowski | 2007-08-13 |
| 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. | ||||
OGC Web Services Architecture for CAD GIS and BIM |
0.9 | 07-023r2 | Paul Cote | 2007-05-16 |
| 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. | ||||
OGC Web Services SOAP Experiment Report |
0.8 | 03-014 | J | 2003-01-15 |
| This document will discuss how OWS services can be ported to Web Services and highlight various issues/problems that have been discovered and need further discussion. | ||||
OGC Web Services Summaries |
0.3.0 | 07-095r2 | Arliss Whiteside | 2007-11-14 |
| This document provides brief and consistent summaries of several OGC Web Service interface specifications that serve data. | ||||
OGC Web Services UDDI Experiment |
0.5 | 03-028 | Josh Lieberman, Lou Reich, Peter Vretanos | 2003-01-17 |
| 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. | ||||
OpenGIS® Sensor Event Service Interface Specification |
0.3.0 | 08-133 | Johannes Echterhoff, Thomas Everding | 2008-10-10 |
| 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. | ||||
OpenGIS Tiled WMS Discussion Paper |
0.3.0 | 07-057r2 | Keith Pomakis | 2007-10-10 |
| 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. | ||||
OpenSearch Geospatial Extensions Draft Implementation Standard |
0.0.1 | 09-084r1 | Jo Walsh, Pedro Gonçalves, Andrew Turner | 2009-10-13 |
| 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. | ||||
OWS-2 Application Schema Development |
0.0.4 | 04-100 | Clemens Portele | 2005-04-13 |
| 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 . |
||||
OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe |
0.9 | 05-140 | Yves Coene | 2006-03-30 |
| 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. |
||||
OWS-4 CSW ebRIM Modelling Guidelines IPR |
0.0.6 | 06-155 | Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos | 2007-06-06 |
| 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]. | ||||
OWS-4 Workflow IPR |
0.0.9 | 06-187r1 | Steven Keens | 2007-05-07 |
| This document examines five workflows discussed during the course of the OWS-4 project. | ||||
OWS-5 CITE Summary Engineering Report |
0.1.0 | 08-084r1 | Jen Marcus | 2008-08-20 |
| This document summarizes work completed in the OWS5 Compliance & Interoperability Test & Evaluation thread. This document is applicable to the OGC Compliance Test Program. | ||||
OWS-5 Conflation Engineering Report |
0.1.0 | 07-160r1 | Pete Brennen | 2008-09-12 |
| 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. | ||||
OWS-5 Considerations for the WCTS Extension of WPS |
0.1.0 | 08-054r1 | Max Martinez | 2008-08-20 |
| This document details considerations for using the WPS specification to define a standard coordinate transformation service. | ||||
OWS-5 Data View Architecture Engineering Report |
0.0.0 | 07-163 | David Rosinger, Stan Tillman | 2008-05-02 |
| 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. | ||||
OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report |
0.1.0 | 08-058r1 | Stefan Falke | 2008-09-12 |
| 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. | ||||
OWS-5 GeoProcessing Workflow Architecture Engineering Report |
0.1.0 | 07-138r1 | Michael Werling | 2008-09-12 |
| 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. | ||||
OWS-5 GeoRM License Broker Discussion Paper |
0.9 | 08-076 | Rüdiger Gartmann | 2008-09-12 |
| 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. | ||||
OWS-5 KML Engineering Report |
0.1.0 | 07-124r2 | Chris Holmes | 2008-09-12 |
| 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. | ||||
OWS-5 WCS JPIP Coverage Subsetting Engineering Report |
0.9.0 | 07-169 | Steven Keens | 2008-09-12 |
| 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. | ||||
OWS1.2 Image Handling Design |
0.5 | 04-051 | George Percivall | 2004-09-26 |
| 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. | ||||
OWS1.2 Image Handling Requirements |
0.1.4 | 04-052 | Arliss Whiteside | 2004-09-26 |
| 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. | ||||
OWS 2 Common Architecture: WSDL SOAP UDDI |
1.0 | 04-060r1 | Jerome Sonnett | 2005-02-17 |
| 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. | ||||
OWS 3 GML Investigations - Performance Experiment by Galdos Systems |
0.0.4 | 05-101 | David Burggraf | 2006-04-19 |
| 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. | ||||
OWS3 GML Topology Investigation |
0.0.5 | 05-102r1 | David Burggraf, Stan Tillman | 2006-05-09 |
| 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. | ||||
OWS4 - Topology Quality Assessment Interoperability Program Report |
0.3.0 | 07-007r1 | Paul Watson | 2007-06-06 |
| This document describes the purpose and function of the Topology Quality Assessment Service developed and deployed within the Geo-processing workflow thread of the OWS4 interoperability testbed. | ||||
OWS 4 WFS Temporal Investigation |
0.1.0 | 06-154 | David S. Burggraf, Ron Lake, Darko Androsevic | 2007-08-14 |
| 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). | ||||
OWS 5 Engineering Report: Supporting Georeferenceable Imagery |
0.1.0 | 08-071 | Mike Botts | 2008-09-12 |
| 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. | ||||
OWS 5 SOAP/WSDL Common Engineering Report |
0.1.0 | 08-009r1 | Bastian Schaeffer | 2008-02-21 |
| This OGC document reports the results achieved in the OWS5 GPW-SOAP/WSDL thread which is focused on creating general recommendations and guidelines for WSDL/SOAP support to existing OGC Web Services. | ||||
OWS5: OGC Web feature service, core and extensions |
0.9.0 | 08-079 | John Herring | 2008-09-12 |
| 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. | ||||
OWS Integrated Client (GeoDSS Client) |
0.0.3 | 05-116 | Stan Tillman, Jody Garnett | 2007-03-08 |
| This Interoperability Program Report (IPR) provides an overview of the general requirements, architecture, and design considerations of | ||||
OWS Messaging Framework |
0.0.3 | 03-029 | Stephane Fellah, Steven Keens | 2003-01-20 |
| 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. | ||||
Requirements for some specific simple solid, plane and line geometry types |
0.5.0 | 07-001r3 | Simon Cox | 2007-05-02 |
| This specification describes requirements for specific geometry types, including some simple solids, and planes and lines defined using an implicit parameterization. | ||||
Schema Maintenance and Tailoring |
0.0.7 | 05-117 | Clemens Portele | 2006-05-02 |
| Description of the schema tailoring process for the application schema development in the decision support services thread (GeoDSS) during the OWS-3 initiative | ||||
Semantic annotations in OGC standards |
0.3.0 | 08-167r1 | Patrick Maué | 2009-07-16 |
| 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. | ||||
Sensor Observable Registry Discussion Paper |
0.3.0 | 09-112 | Simon Jirka, Arne Bröring | 2009-10-13 |
| 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. | ||||
Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan |
0.3.0 | 09-082 | Hsu-Chun James Yu, Zhong-Hung Lee, Cai-Fang Ye, Lan-Kun Chung, Yao-Min Fang | 2009-07-27 |
| This application document describes:
1) What is a Debris Flow Monitoring System. |
||||
Service Information Model |
0.3.0 | 03-026 | Joshua Lieberman | 2003-01-17 |
| SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata. | ||||
Some image geometry models |
1 | 04-071 | Arliss Whiteside | 2004-10-04 |
| 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". |
||||
Specification of the Sensor Service Architecture (SensorSA) |
3 (Rev 3.1) | 09-132r1 | Thomas Usländer (Ed.) | 2009-10-02 |
| 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. | ||||
Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed |
1.0 | 08-073r2 | Jessica Cook, Raj Singh | 2008-09-12 |
| 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. | ||||
Temporal Standard Recommendations |
0.0.9 | 06-022r1 | James Resler | 2006-04-21 |
| 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 Specification Model -- Structuring an OGC specification to encourage implementation |
0.0.9 | 07-056r1 | John Herring, OAB, Architecture WG | 2007-07-23 |
| This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. | ||||
Trusted Geo Services IPR |
0.9.0 | 06-107r1 | Cristian Opincaru | 2007-05-07 |
| 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]. | ||||
Uncertainty Markup Language (UnCertML) |
0.6 | 08-122r2 | Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma | 2009-04-08 |
| 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. | ||||
Uses and summary of Topic 2: Spatial referencing by coordinates |
0.3.0 | 09-076r3 | Arliss Whiteside | 2009-09-14 |
| 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). | ||||
Web 3D Service |
0.3.0 | 05-019 | Udo Quadt, Thomas Kolbe | 2005-02-02 |
| 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. | ||||
Web Coordinate Transformation Service |
0.4.0 | 07-055r1 | Arliss Whiteside, Markus U. M | 2007-10-09 |
| 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 | ||||
Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding |
0.2.2 | 09-018 | Ben Domenico, Stefano Nativi | 2009-04-08 |
| 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. |
||||
Web Image Classification Service (WICS) |
0.3.3 | 05-017 | Wenli Yang, Arliss Whiteside | 2005-02-10 |
| 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. | ||||
Web Object Service Implementation Specification |
0.0.3 | 03-013 | Panagiotis (Peter) A. Vretanos | 2003-01-15 |
| 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. | ||||
Web Pricing and Ordering |
0.2 | 02-039r1 | Roland Wagner | 2002-10-18 |
| This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products. | ||||
Web Services Architecture |
0.3 | 03-025 | Josh Lieberman | 2003-01-18 |
| Specifies and discusses a common architectural framework for OGC Web Services | ||||
Web Terrain Server |
0.3.2 | 01-061 | Raj Singh | 2001-08-24 |
| The purpose of theWeb Terrain Server (WTS) is to produce perspective views of georeferenced data - typically 3-dimensional coverages. | ||||
WMS - Proposed Animation Service Extension |
0.9 | 06-045r1 | Eric LaMar | 2006-07-27 |
| 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. | ||||
WMS Change Request: Support for WSDL & SOAP |
0.1.0 | 04-050r1 | Philippe Duschene, Jerome Sonnet | 2005-04-22 |
| 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. | ||||
WMS Part 2: XML for Requests using HTTP Post |
0.0.3 | 02-017r1 | Jeff de La Beaujardiere | 2002-08-24 |
| 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. | ||||
Wrapping OGC HTTP-GET/POST Services with SOAP |
0.1 | 07-158 | R | 2008-01-02 |
| Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP | ||||
XML for Image and map Annotation |
0.4 | 01-019 | John Evans | 2001-02-06 |
| Defines an XML vocabulary to encode annotations on imagery, maps, and other geospatial data. This vocabulary draws on the Geography Markup Language (OpenGIS | ||||
