OGC Public Forum : Helping the world to communicate geographically...    FAQ   Search   Memberlist   Usergroups   Digests   Register   Profile   Log in to check your private messages   Log in  The time now is Thu Jul 02, 2009 5:56 pm OGC Public Forum : Forum Index View unanswered posts  Forum   Topics   Posts   Last Post  OGC   OGC: General Comments Comments and responses to OGC in general Moderator Staff 300 894 Mon Jun 15, 2009 2:07 pm creed OGC Compliance Testing   CITE Portal General discussion, tips, and problem solving concerning use of the OGC CITE Portal http://cite.occamlab.com/ Moderator Staff 40 98 Thu Apr 23, 2009 3:36 pm mmaskey OGC Specifications   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. Moderator Staff 6 13 Mon Feb 23, 2009 4:55 pm creed 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. Moderator Staff 15 39 Mon Jun 22, 2009 5:18 pm creed 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. Moderator Staff 9 37 Wed Apr 22, 2009 4:48 pm creed CT: Coordinate Transformation Services Provides interfaces for general positioning, coordinate systems, and coordinate transformations. Moderator Staff 8 18 Thu Jun 25, 2009 12:14 pm cavila 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]. Moderator Staff 14 21 Fri Aug 22, 2008 1:21 pm JeffHarrison 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. Moderator Staff 1 2 Sun Oct 05, 2008 10:58 am creed 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 Moderator Staff 73 191 Wed Jun 24, 2009 9:58 am Tom 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. Moderator Staff 6 17 Tue Feb 12, 2008 12:44 pm creed 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.     2 6 Fri Mar 13, 2009 11:35 am kevin 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.     1 3 Wed Feb 18, 2009 4:11 am trandriana 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.     0 0 No Posts 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.     0 0 No Posts 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). Moderator Staff 0 0 No Posts 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). Moderator Staff 1 2 Tue Jun 22, 2004 9:49 am mbuehler 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). Moderator Staff 25 58 Wed Jun 24, 2009 11:05 am creed 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. Moderator Staff 15 29 Thu Mar 12, 2009 12:00 pm JeffHarrison 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.     1 1 Thu Feb 26, 2009 10:05 am jpulles 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). Moderator Staff 11 39 Mon Apr 13, 2009 2:43 pm rmeinsen 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. Moderator Staff 55 123 Wed Jul 01, 2009 2:36 am hyacinthus 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. Moderator Staff 3 5 Mon Apr 06, 2009 9:21 am rajsingh 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. Moderator Staff 49 107 Wed Mar 04, 2009 12:40 pm creed 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.     1 2 Mon Jan 12, 2009 6:55 pm creed Retired   OGC: Near the Tipping Point Comments and responses to the David Sonnen article. Moderator Staff 7 15 Wed Aug 03, 2005 12:16 pm guest All times are GMT - 5 Hours Who is Online Our users have posted a total of 1745 articles We have 853 registered users The newest registered user is thiagosil In total there are 8 users online :: 0 Registered, 0 Hidden and 8 Guests   [ Administrator ]   [ Moderator ] Most users ever online was 61 on Thu Apr 03, 2008 7:11 pm Registered Users: None This data is based on users active over the past five minutes Log in Username:    Password:      Log me on automatically each visit     New posts    No new posts    Forum is locked OGC® websites: OGC Home | OGC Network™ | OGC User™ | ORM | OGC Forum | OGC Schemas Powered by phpBB © 2001, 2005 phpBB Group