Home
"Making location count"

OGC Requests

WCS 1.1.2 Processing extension Request for Comment

Please note: This Request is scheduled to close on 30 July 2008.

The Open Geospatial Consortium, Inc. (OGC) membership approved a 30 day public comment period for a revision to the OpenGIS® Web Coverage Service (WCS) Interface Standard. The revision includes two extensions to WCS: the WCS 1.1 Transaction Extension and the Web Coverage Processing Service Processing (WCPS) Extension.

The WCS Interface Standard (http://www.opengeospatial.org/standards/wcs) specifies an application programming interface (API) for requesting coverage data, such as imagery, from one or more distributed sources.

The WCS 1.1 Transaction Extension defines how WCS clients can request that a WCS server import one or more new coverages into that server, update existing coverages, and/or delete existing coverages.



Request for Comment on CityGML Standard

Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.

The Open Geospatial Consortium, Inc. (OGC) is requesting public comment on the candidate CityGML Encoding Standard. CityGML is a Geography Markup Language 3 (GML3) application schema for the storage and exchange of virtual 3D city models.

CityGML is a common information model for the representation of 3D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantical and appearance properties. Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. These thematic information go beyond graphic exchange formats and allow to employ virtual 3D city models for sophisticated analysis tasks in different application domains like simulations, urban data mining, facility management, and thematic inquiries.



OGC Request for Quotation for Empire Challenge 08 Pilot

 

Slides for the Bidders Conference on 16 January are now available.

The Open Geospatial Consortium, Inc. (OGC) has issued a Request For Quotations and Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the Empire Challenge 08 Pilot (EC08 OGC Pilot).

The EC08 OGC Pilot is sponsored by a US agency which will provide cost-sharing funds to offset expenses associated with the initiative. The sponsor and the OGC intend to involve as many participants in the initiative as possible and thus are soliciting proposals that will enhance and/or make use of the initiative outcomes. This RFQ/CFP is soliciting partners to provide and deploy hardware / software and to collaborate on the final technology design for the pilot network. Personnel without clearances will be able to install and maintain software on the network. Responses are due by January 24, 2008 and the Pilot Kickoff Meeting will be held the week of February 26-28, 2008, in the Washington, DC area. Technology deployments will be complete by June 27, 2008, followed by a four-week demonstration phase in July.



Request for Comment on KML 2.2

Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.

The Open Geospatial Consortium (OGC) is contemplating adoption of the KML 2.2 candidate standard. The OGC invites public comment on this candidate standard. All comments will be collated and used in the evaluation of KML 2.2 as an OGC standard. In late first quarter 2008, the OGC committee working on the KML 2.2 candidate standard will seek approval by OGC members for KML 2.2 an OpenGIS(R) Encoding Standard.

The OpenGIS Candidate Implementation Standard specifies XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.



Request for Comment on Sensor Alert Service


Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS Sensor Alert Service (SAS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Sensor Alert Service (SAS) Draft Implementation Specification specifies interfaces for requesting information describing the capabilities of a Sensor Alert Service, for determining the nature of offered alerts, the protocols used, and the options to subscribe to specific alert types.



OWS-5 Testbed Addendum Released

Please note: This Request is closed.
RFQ Issuance Date: 7 September, 2007
Clarifications Posted: 17 September, 2007
Proposal Due Date: 5 October, 2007

 

Overview

This document is an addendum to the previously issued OWS-5 RFQ/CFP and includes new requirements to be included in the Agile Geography thread of the ongoing OWS-5 testbed. The requirements within this addendum should be addressed within the overall context of the original OWS-5 RFQ/CFP. It should be noted that schedule information contained within this document supercedes that which was found in the original OWS-5 RFQ/CFP.

The content within this RFQ covers two topics and are described in further detail below:



Request for Comment on Image Geopositioning Service (IGS)

Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS Image Geopositioning Service (IGS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Image Geopositioning Service (IGS) Draft Implementation Specification defines an Image Geopositioning Service (IGS) interface to services that perform triangulation. (NOTE: The name of this service has not yet been formally agreed upon.) Accompanying this draft specification is a separate OpenGIS Image Geopositioning Metadata Geography Markup Language (GML) Draft Application Schema, which is structured to provide consistency between the IGS and other OGC Web Services (OWS) specifications.



Request for Comment on Geospatial eXtensible Access Control Markup Language (GeoXACML)

Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called Geospatial eXtensible Access Control Markup Language (GeoXACML). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Geospatial eXtensible Access Control Markup Language (GeoXACML) Draft Implementation Specification (OGC Document 07-026) defines a geo-specific extension to the eXtensible Access Control Markup Language (XACML) OASIS standard. "Access control systems" enable management of access to information only until it is obtained by the user and stored locally, as opposed to "rights management systems" that remain in force regardless of where the content of the original resource is located or reproduced.



OGC Web Services, Phase 5 (OWS-5) Request For Quotation and Call For Participation

This Request is Closed.
RFQ Issuance Date: 11 May, 2007
OWS-5 Bidder's Conference: 22 May, 2007
Proposal Due Date: 8 June, 2007

 

Overview

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' work together to solve specific geo-processing interoperability problems posed by the initiative's sponsoring organizations. OGC Interoperability Initiatives include test beds, pilot projects, interoperability experiments, and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of open, consensus based standards specifications.



Architecture Implementation Pilot Call for Participation (CFP)

Please note: The submission period for this request is closed.

CFP Issuance Date: 18 April 2007
Response Due Date: 11 May 2007
Pilot Kickoff Meeting: 5-6 June 2007

This Call for Participation (CFP) seeks participants in a coordinated Geospatial Architecture Implementation Pilot. A Pilot is a collaborative effort that applies open standards for interoperability to achieve user objectives in an environment representative of operational use. Outcomes include best-practices and interoperability arrangements suitable for an operational capability. An aim of the Pilot is to reach consensus on architectural elements that initiatives supporting geospatial information systems can carry forward into operations, thereby increasing the overall level of interoperability.



Syndicate content