Forums

OGC: General Comments

Comments and responses to OGC in general

CITE Portal

General discussion, tips, and problem solving concerning use of the OGC CITE Portal cite.opengeospatial.org/.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in this forum.

AOS: GO-1 Application Objects

The GO-1 Application Objects specification (AOS) defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics.

CAT: Catalog Interface

Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

Common: OGC Web Services Common Specification

Defines many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. Those specifications currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). These common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses.

CT: Coordinate Transformation Services

Provides interfaces for general positioning, coordinate systems, and coordinate transformations.

Filter: Filter Encoding

Defines an XML encoding for filter expressions based on the BNF definition of the OpenGIS Common Catalog Query Language as described in the OpenGIS Catalog Interface Implementation Specification, Version 1.0 [2].

GC: Grid Coverages

This specification was designed to promote interoperability between software implementations by data vendors and software vendors providing grid analysis and processing capabilities.

GML: Geography Markup Language

The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.

Other topics of interest: CityGML, KML

O&M: Observations and Measurements

Describes a conceptual model and encoding for observations and measurements. This is formalized as an Application Schema, but is applicable across a wide variety of application domains. An Observation is an action with a result which has a value describing some phenomenon. The observation is modelled as a Feature within the context of the General Feature Model [ISO 19101, ISO 19109]. An observation feature binds a result to a feature of interest, upon which the observation was made.

OLS Core: OpenGIS Location Services (OpenLS): Core Services

This OpenGIS Implementation Specification describes OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, also known as the GeoMobility Server (GMS), an open platform for location-based application services. It also outlines the scope and relationship of OpenLS with respect to other specifications and standardization activities. The primary objective of OpenLS is to define access to the Core Services and Abstract Data Types (ADT) that comprise the GeoMobility Server, an open location services platform.

SensorML: Sensor Model Language Encoding Standard

The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) suite of standards.

SFC: Simple Features - CORBA

The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc).

SFO: Simple Features - OLE/COM

The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc).

SFS: Simple Features - SQL

The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc).

SLD: Styled Layer Descriptor

The SLD is an encoding for how the Web Map Server (WMS 1.0 & 1.1) specification can be extended to allow user-defined symbolization of feature data.

SOS: Sensor Observation Service

The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) suite of standards.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

SPS: Sensor Planning Service

The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) suite of standards.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

TML: Transducer Markup Language

The OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system. The protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations. The sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion. This is one of the OGC Sensor Web Enablement (SWE) suite of standards.

WCS: Web Coverage Service

Extends the Web Map Server (WMS) interface to allow access to geospatial "coverages" that represent values or properties of geographic locations, rather than WMS generated maps (pictures).

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

WFS: Web Feature Service

The OGC Web Feature Service (WFS) interface is a collection of operations (implemented as messages carried over HTTP) for retrieving and manipulating geographic features. An implementation of the OGC WFS IS allows a client to retrieve and update geospatial data encoded in Geography Markup Language (GML) from one or more Web Feature Services.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

WMC: Web Map Context Documents

This is a companion specification to the OGC Web Map Service Interface Implementation Specification The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a "Web Map Context Document," or simply a "Context." Presently, context documents are primarily designed for WMS bindings.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

WMS: Web Map Service

Provides three operations protocols (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous.

Please post all Compliance & Interoperability Testing & Evaluation (CITE) issues in the CITE web forum.

WPS: Web Processing Service

The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server.