OGC Requests

OWS-9 RFQ: OGC Calls for Participation in Major Interoperability Testbed

Status: 
Please note: This Request is closed.

 

Description: 


RFQ Issuance Date:
 22 February 2012
OWS-9 Bidder's Conference: will be held on March 9, 2012, see below.
Proposal Due Date: 5 pm EST on April 6, 2012.

Go Directly to the Request for Quotation Document 
Go Directly to the Bidder's Conference Information Overview 
Go Directly to the Request for Quotation Clarifications

 

Overview

The Open Geospatial Consortium (OGC®) has issued a Request for Quotations/Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the OGC Web Services, Phase 9 (OWS-9) Testbed (http://www.opengeospatial.org/projects/initiatives/ows-9).

The RFQ/CFP is available below.

Responses are due by 5 pm EST on April 6, 2012.

A bidders’ teleconference will be held on March 9, 2012. More information will be available below.

The Point of Contact is Nadine Alameh: techdesk [at] opengeospatial.org.

The OWS-9 sponsors are:

  • AGC (Army Geospatial Center, US Army Corps of Engineers)
  • CREAF-GeoViQua-EC (CREAF is the European Center for Research in Ecology and Forestry Applications)
  • EUROCONTROL
  • FAA (US Federal Aviation Administration)
  • GeoConnections - Natural Resources Canada
  • Lockheed Martin Corporation
  • NASA (US National Aeronautics and Space Administration)
  • NGA (US National Geospatial-Intelligence Agency)
  • USGS (US Geological Survey)

OWS-9 builds on the outcomes of prior OGC initiatives (http://www.opengeospatial.org/resource/demos) and is organized around the following threads:

-   Aviation: Develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) in an OGC Web Services environment, focusing on support for several Single European Sky ATM Research (SESAR) project requirements as well as the FAA's Aeronautical Information Management (AIM) and Aircraft Access to SWIM (System Wide Information Management) (AAtS) requirements.

-   Cross-Community Interoperability (CCI): Build on the CCI work accomplished in OWS–8 by increasing interoperability within communities sharing geospatial data, focusing on semantic mediation, query results delivery, data provenance and quality and Single Point of Entry Global Gazetteer 

-   Security and Services Interoperability (SSI): Investigate 5 main activities: Security Management, OGC Geography Markup Language (GML) Encoding Standard Application Schema UGAS (UML to GML Application Schema) Updates, Web Services Façade, Reference Architecture Profiling, and Bulk Data Transfer.

-   OWS Innovations: Explore topics that represent either new areas of work for the Consortium (such as GPS and Mobile Applications), a desire for new approaches to existing technologies to solve new challenges (such as the OGC Web Coverage Service (WCS) work), or some combination of the two.

-   Compliance & Interoperability Testing & Evaluation (CITE): Develop a suite of compliance test scripts for testing and validation of products with interfaces implementing the following OGC standards: Web Map Service (WMS) 1.3 Interface Standard, Web Feature Service (WFS) 2.0 Interface Standard, Geography Markup Language (GML) 3.2.1 Encoding Standard, OWS Context 1.0 (candidate encoding standard), Sensor Web Enablement (SWE) standards, Web Coverage Service for Earth Observation (WCS-EO) 1.0 Interface Standard, and TEAM (Test, Evaluation, And Measurement) Engine Capabilities.

The RFQ/CFP includes details of these threads as well as details on participation eligibility, selection process and kickoff workshop information.

OGC testbeds, pilot projects and interoperability experiments are part of the OGC Interoperability Program, a global, hands-on collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards into the OGC Specification Program, where they are formalized for public release.

Downloads: 

 

RESPONSE TEMPLATES (not included in above package)

 

 

 

Questions: Bidder's Conference

 A Bidder's Conference (webinar) was be held on March 9, 2012

A second bidder's conference will be held on March 19, 2012 

Date and Time:
Monday, March 19, 2012 10:00 pm, GMT
Monday, March 19, 2012 5:00 pm, Central Daylight Time (Chicago, GMT-05:00)
Tuesday, March 20, 2012 7:00 am, Japan Time (Tokyo, GMT+09:00)
Monday, March 19, 2012 7:00 pm, Eastern Daylight Time (New York, GMT-04:00)
Tuesday, March 20, 2012 11:00 pm, Europe Time (Berlin, GMT+01:00)

This telecon will originate from a F2F meeting as part of OGC TC meetings.

You must register for this session at:

  https://ogc-meeting.webex.com/ogc-meeting/onstage/g.php?t=a&d=668037249

 

Clarifications Document

All Q&A, updates, and other information about OWS-9 from the Bidder’s Conference and other communications will be collected into a Clarifications document, and posted here for public access. Subsequent questions may be directed by email to techdesk [at] opengeospatial.org.  The Clarifications Document is here: 

Current clarifications

OGC Requests: 

The OGC seeks comment on WaterML 2.0 Hydrologic Time Series Encoding Standard

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC WaterML 2.0: part 1 – Time Series Encoding Standard.

WaterML 2.0 is a candidate Open Geospatial Consortium standard for the representation of hydrological observations, specifically addressing time series data. The WaterML 2.0 candidate standard is implemented as an application schema of the OGC Geography Markup Language (GML) Encoding Standard version 3.2.1 and makes use of the OGC Observations and Measurements (O&M) model and encoding standards.

The OGC WaterML 2.0 candidate standard supports encoding of hydrological and hydrogeological observation data in exchange scenarios such as: exchange of data for operational monitoring and forecasting programs; supporting operation of infrastructure (e.g. dams, supply systems); exchange of observational and forecast data for surface water and groundwater; release of data for public dissemination; enhancing disaster management through data exchange; and exchange in support of national reporting.

WaterML 2.0 is the result of an international cooperative effort of the OGC Hydrology Domain Working Group, involving hydrological and government agencies, software providers, universities and research organizations from Australia, the USA, Canada, Germany, the Netherlands and other countries.

The candidate OGC WaterML Version 2.0 standard documents are available for public review and comment below:

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

 You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

The OGC seeks comment on GeoSynchronization Best Practices

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Closing Date: 
Sat, 09/01/2012
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC GeoSynchronization Best Practices Document.

Frequently, geospatial content providers must collaborate with outside entities to collect new data and/or update their existing data holdings. This may be the case, for example, when municipal, state/provincial and/or federal agencies synchronize their data with closest-to-source providers. Another case is when content providers are crowdsourcing (see http://en.wikipedia.org/wiki/Crowdsourcing) elements of their data production or supporting volunteer geographic information (VGI).

This candidate OGC Best Practice describes how to use the OGC's open interface and encoding standards to implement services that mediate interaction between geospatial data providers, the content repositories, and the external entities acting as data collectors. Such services support data entry with validation, notification of changes to interested parties and replication of the data content submitted to multiple repositories.

This document defines an OGC Best Practice on a particular technology or approach related to OGC standards. This document is not an OGC standard and may not be referred to as an OGC standard. It is subject to change without notice. However, this document is an official position of the OGC membership on this particular technology topic.

The following organizations submitted this Best Practice to the OGC: The Carbon Project, OpenGeo.org and CubeWerx Inc.

The candidate OGC GeoSynchronization Best Practices document is available for public review and comment below.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

 You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

The OGC seeks comment on Gazetteer Best Practices

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Closing Date: 
Sun, 01/01/2012
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC Gazetteer Best Practices Document.

There is growing interest in the development of a common feature-based model for geographic names databases, often referred to as gazetteers. This candidate OGC best practice describes the Gazetteer Service Application Profile of the OGC Web Feature Service Interface Standard.

This document is an OGC Best Practice on a particular technology or approach related to the use of OGC standards. 

The following organizations submitted this Best Practice to the OGC:

  • CubeWerx Inc.
  • Intergraph Government Solutions
  • The Carbon Project
  • US Army Corps of Engineers Army Geospatial Center (AGC)
  • US Federal Geographic Data Committee (FGDC)
  • US Geological Survey (USGS)
  • US National Geospatial-Intelligence Agency (NGA)

The candidate OGC Gazetteer Best Practices Document is available for public review and comment below:

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

 You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

The OGC seeks comment on City Geography Markup Language (CityGML) V1.1

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on Version 1.1 of the OGC City Geography Markup Language (CityGML) Encoding Standard (http://www.opengeospatial.org/standards/citygml).

CityGML is an open information model and XML-based encoding for the representation, storage, and exchange of virtual 3D city models. It provides a way to describe objects with respect to their geometry, topology, semantics and appearance, and it defines five different levels of detail. CityGML allows users to employ virtual 3D city models for sophisticated analysis and display tasks in different application domains such as pedestrian navigation, environmental simulations, urban data mining, facilities management, real estate appraisal, and location based marketing.

CityGML has been implemented in many software solutions and is in use in many projects around the world. Developed for Urban Information Modeling applications, CityGML plays an important role in bridging Urban Information Models with Building Information Models (BIM) to improve interoperability among the information systems used in the many areas of activity that involve design, construction, ownership and operation of buildings and capital projects.

CityGML is implemented as an application schema of the OGC Geography Markup Language 3 (GML3) Encoding Standard (http://www.opengeospatial.org/standards/gml), an international standard for spatial data exchange and encoding approved by the OGC and the International Organization for Standardization (ISO).

The current version 1.0 of CityGML was adopted as an official OGC Standard in August 2008 and has come to wide use since then. The OGC Technical Committee's CityGML Working Group has received input from the wider community in the form of change requests, proposed additions and suggestions. With this guidance, the Working Group developed the draft CityGML Version 1.1, a minor revision of the current CityGML version 1.0 that maintains backwards compatibility with version 1.0. Version 1.1 includes new thematic modules for tunnels and bridges, the ability to model footprint and roof edge representations for buildings in the coarsest level of detail, and generic attribute sets, as well as a number of additional properties and other enhancements.

 The candidate CityGML Version 1.1 standard documents are available for review and comment below. Comments are due by 14 September 2011.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

 You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks comment on candidate Earth Observation profile of coverage standard

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Closing Date: 
Tue, 11/01/2011
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate Earth Observation profile for the OGC Web Coverage Service (WCS) 2.0 standard. This profile will facilitate on-line data access to Earth Observation data products.

The OGC WCS 2.0 standard defines a general interface and operations that enable interoperable access to geospatial coverages, such as sensor data, satellite imagery, digital elevation models, and climate/ocean data. The candidate OGC Web Coverage Service Application Profile for Earth Observation products (EO-WCS) defines an interface for interoperable access to Earth Observation data.

The rapid increase of computer power and network accessibility, along with implementations of the OGC WCS standard, make it possible for applications to deliver user selected sensor, image, and statistics data, including human modifications of the Earth's surface and atmosphere. As use of the standard increases, an increasingly wide variety of data will conveniently be brought together in applications such as environment, natural resources, planning, disaster management and public security.

The candidate Earth Observation profile for the OGC Web Coverage Service (WCS) 2.0 standard documents are available for review and comment below.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

 You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC Seeks Comment on candidate GeoSPARQL standard

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC “GeoSPARQL: A Geographic Query Language for RDF Data” Standard. The candidate OGC GeoSPARQL standard defines spatial extensions to the W3C's SPARQL protocol and RDF query language. 

SPARQL is a protocol and query language for the Semantic Web. SPARQL is defined in terms of the W3C's RDF data model and will work for any data source that can be mapped into RDF, which potentially includes sources of geospatial data. The OGC GeoSPARQL standard supports representing and querying geospatial data on the Semantic Web. GeoSPARQL provides the foundational geospatial vocabulary for linked data involving location and defines extensions to SPARQL for processing geospatial data. This standard serves as a common target for vendors to implement and provides rich functionality for building geospatial applications.

GeoSPARQL follows a modular design. A core component defines top-level RDFS/OWL classes for spatial objects. A geometry component defines RDFS data types for serializing geometry data, RDFS/OWL classes for geometry object types, geometry-related RDF properties, and non-topological spatial query functions for geometry objects. A geometry topology component defines topological query functions. A topological vocabulary component defines RDF properties for asserting topological relations between spatial objects, and a query rewrite component defines rules for transforming a simple triple pattern that tests a topological relation between two features into an equivalent query involving concrete geometries and topological query functions.

The candidate OGC GeoSPARQL Standard documents are available for review and comment below.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC Seeks Comment on Geography Markup Language 3.3 Standard

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate version 3.3 of the OGC Geography Markup Language (GML). GML 3.3 builds on GML 3.2.1, published by ISO as ISO 19136:2007, and extends GML with additional schema components based on requirements requested by various domains of interest. For example, the 3d modeling community suggest the addition of triangular meshes (TINs) to GML. GML 3.3 is fully backwards compatible with GML 3.2.

GML defines an XML data encoding for geographic data and a grammar to express models of such data using XML Schema. GML has come into wide use since it was first adopted as an OGC standard in 2001 (http://www.ogcnetwork.net/gmlprofiles for examples). GML is the standard that enables information communities and other standards organizations such as the Internet Engineering Task Force (IETF) and OASIS to insert geospatial elements into their standards and be confident that their standards will be compatible with mainstream information infrastructure methods of conveying spatial/temporal information.

Some of the changes between the previous version 3.2.1 and 3.3 are:

  • Support for additional date representations based on ISO 8601 (Representation of dates and times)
  • Support for an additional, compact encoding of commonly used geometry types
  • Support for a new encoding of Triangulated Irregular Networks (TINs)
  • Support for Linear Referencing
  • Extensions to the XML encoding rule
  • Support for grids used by the meteorological and ocean observation communities

All extensions are made in separate XML namespaces to support a modular use of components from the GML schema.

Information on the change requests addressed in GML v3.3 can be found athttp://external.opengeospatial.org/twiki_public/GML/ChangeRequests. The candidate OGC GML v3.3 Standard documents are available for review and comment below.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

Request for Comments on Candidate PUCK Protocol Standard

Status: 
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.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC PUCK Protocol Encoding Standard.

Most sensor networks require careful manual installation and configuration by technicians to assure that software components are properly associated with the physical instruments that they represent. Instrument driver software, configuration files, and "metadata" describing the instrument and its capabilities must be manually installed and associated with a physical instrument port. Sometimes these manual procedures must be performed under physically challenging conditions, increasing the chances of human error. PUCK addresses these challenges by defining a standard instrument protocol to retrieve metadata and other information from the device itself. This information can include OGC SWE SensorML and IEEE 1451 Transducer Electronic Data Sheet (TEDS) documents, as well as actual instrument driver code. Computers on the network can use the PUCK protocol to retrieve this information from installed instruments and utilize it appropriately, e.g. to automatically identify, configure and operate the instruments. Thus PUCK enables automatic self-configuring "plug-and-work" sensor networks.

PUCK is relatively simple, and several manufacturers have implemented the protocol in their instruments' firmware. PUCK augments but doesn't replace existing instrument command sets, so can be implemented without abandoning existing firmware and software applications. PUCK was originally developed by the Monterey Bay Aquarium Research Institute (MBARI) for oceanographic applications, but is useful in any sensor network containing RS232 or Ethernet-connected instruments. PUCK-enabled instruments have been deployed on ocean observatories in the USA and Europe, and the protocol is being considered for adoption by other projects as well. The OGC Technical Committee’s PUCK Standards Working Group was chartered to process the existing MBARI PUCK protocol as a candidate OGC standard compatible with the OGC Sensor Web Enablement (SWE) standards baseline.

The candidate OGC PUCK Standard documents are available for review and comment below.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

Request for Comments on Earth Observation Metadata profile of the OGC Observations and Measurements Standard

Status: 
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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate standard “Earth Observation Metadata profile of the OGC Observations and Measurements Standard.” 

The Earth Observation (EO) profile of Observations and Measurements is intended to provide a standard schema for encoding Earth Observation metadata to support the description and cataloguing of products from sensors aboard EO satellites.

 

This second version of the Earth Observation metadata profile is based on Observations and Measurements, an OGC and ISO standard used in several communities. For example, O&M is used as a basis for the application schemas in several draft INSPIRE Annex II+III data specifications.

 

The metadata elements defined in this candidate standard are applicable for use in catalogues and applications, including various EO cataloguing applications based on OGC standards like the ebRIM Application Profile of the OGC Catalog Services – Web (CS-W) Interface Standard.

 

EO products are differentiated by parameters such as date of acquisition and location as well as characteristics pertaining to the type of sensor, such as cloud, haze, smoke or other phenomena obscuring optical imagery. Metadata used to distinguish EO product types are defined in this candidate standard for generic products and also for specific thematic EO products, such as optical, radar, atmospheric, altimetry, limb-looking and synthesized products. In addition, this document describes the mechanism used to extend these schemas to specific EO missions.

 

The candidate OGC Earth Observation Metadata profile of Observations & Measurements Standard documents are available for review and comment below.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

Pages