OGC Requests

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

Status: 
Please note: As of 1 December 2009 this Request will be CLOSED to further proposals.
Description: 

RFQ Issuance Date: 28 October 2009
OWS-7 Bidder's Conference: 10 November 2009, 11:00-13:00 US Eastern
Proposal Due Date: 1 December 2009, 5:00 p.m. EST.

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

OGC members who wish to observe OWS-7 may do so upon submission of the OGC Observer Agreement: http://bit.ly/8DvwvK

Overview

OWS testbeds are part of OGC's Interoperability Program, 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, international teams of technology providers work together to solve specific geoprocessing 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 OGC standards.

The OWS-7 sponsors are organizations seeking open standards for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-7 initiative be organized around the following threads:

OWS-7 is organized in three activity "threads":

  • Sensor Fusion Enablement (SFE)
  • Feature and Decision Fusion (FDF)
  • Aviation

 

OWS-7 Sponsors

U.S. National Geospatial-Intelligence Agency (NGA)
U.S. Federal Aviation Administration (FAA)
EUROCONTROL
EADS Defence Communications Systems (DCS)
U.S. Geological Survey (USGS)
U.S. Army Geospatial Center (AGC)
U.S. Joint Program Executive Office (JPEO)
BAE Systems
PCI Geomatics
Lockheed Martin

 

OWS-7 Threads

In June of 2009, the OGC issued a call for sponsors for the OWS-7 interoperability initiative to advance OGC's open framework for interoperability in the geospatial industry.  Three meetings were conducted with potential OWS-7 sponsors to review the OGC technical baseline, discuss OWS-7 results, and identify OWS-7 requirements.  During the OWS-7 Concept Development phase, a Fusion Standards Study was also conducted, to better inform the requirements for OWS-7 development. 

The definition of fusion resulting from the study was:

 "Fusion is the act or process of combining or associating data or information regarding one or more entities considered in an explicit or implicit knowledge framework to improve one's capability (or provide a new capability) for detection, identification, or characterization of that entity".

There exist many fusion processes deployed in closed architectures with existing single provider software and hardware solutions. The problem in the study was to move those capabilities into a distributed architecture based upon open standards including standards for security, authorization, and rights management.

In the study, fusion was discussed in terms of the three categories shown in the central column in Figure 1‑1:

Figure 1-1

Figure 11. Categories of Fusion

The sponsors selected elements of the Fusion Study results to include in the two OWS-7 threads described below.  Sensor Fusion is addressed in the Sensor Fusion Enablement (SFE) thread. Object/Feature Fusion and Decision Fusion are addressed in the Feature and Decision Fusion (FDF) thread. 

The threads of OWS-7 build upon the threads of previous OWS test beds, as shown in Figure 1-2. 

Figure 1-2

 

Figure 12. Evolution of OWS Testbed Threads

The Sensor Fusion Enablement (SFE) thread builds on the Sensor Web Enablement (SWE) and Geospatial Processing Workflow (GPW) thread by including Sensor Fusion topics and applying workflow to sensor fusion.  The Feature and Decision Fusion (FDF) thread also builds on the OWS-6 Geospatial Processing Workflow (GPW) thread, as well as the OWS-6 Decision Support Services (DSS) thread, by including feature definition and workflow of GPW along with decision support topics.

The third activity thread in OWS-7, the Aviation Thread, began as the Aeronautical Information Management (AIM) Thread in OWS-6, which addressed the use of web services, event notifications, and AIXM 5.0 for Electronic Flight Bag (EFB) applications in the aviation industry.  The Aviation Thread in OWS-7 represents an expansion of scope, to include flight planning and aviation operations more broadly.

Sensor Fusion Enablement (SFE)

The SFE Thread builds on the OGC Sensor Web Enablement (SWE) framework of standards that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. SFE will focus on integrating the SWE interfaces and encodings with workflow and web processing services to perform sensor fusion.  SFE will continue the development of Secure SWE architecture, as well as the interoperability of SWE and Common CBRN Sensor Interface (CCSI).

Emphasis for SFE during this phase of the OWS testbed will be the following:

  • Motion Video Fusion. Geo-location of motion video for display and processing. Change detection of motion video using Web Processing Service with rules.
  • Dynamic Sensor Tracking and Notification. Track sensors and notify users based on a geographic Area of Interest (AOI). The sensor and the user may be moving in space and time.
  • Trusted SWE in an untrusted environment. Build on OWS-6 Secure Sensor Web development, to investigate secure SOS, SPS in more depth.
  • CCSI-SWE Best Practice. Building on OWS-6, develop an ER to be considered by the OGC Technical Committee as a Best Practice.

Feature / Decision Fusion (FDF)

The FDF Thread builds on OWS-6 GPW and DSS work, in particular to advance the state of information cataloguing, Web Processing Services (WPS) profiles, and the Integrated Client. The following task areas have been identified for Feature and Decision Fusion:

  • Schema Automation. Transformation from UML to profiles of GML and KML, including generation of constraints.
  • Data Discovery and Organization. Use of thematic categories in multi-media data discovery, including augmented metadata for quality of source, fitness for use, and uncertainty of the data values, propagated through usage and workflow.
  • Feature and Statistical Analysis. Workflow profiles for feature fusion, including statistical analysis, vector and topological processing. WFS, WMS and WMTS will be used to support statistical mapping.
  • Geosynchronization. Web services and client components to support synchronization of geospatial data and updates across a hierarchical Spatial Data Infrastructure (SDI).
  • Data and Analysis Sharing. The use of OWS Context for collecting links to web services and analysis results.
  • Integrated Client. A field-ready client application to support and display sensor information, cataloguing metadata, notification alerts, feature and statistical analysis, and OWS Context. This client will include an embedded WFS server for geosynchronization support.

Aviation Thread

This thread seeks to further 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.

The US Federal Aviation Administration (FAA) and EUROCONTROL have developed AIXM as a global standard for the representation and exchange of aeronautical information. AIXM uses the OGC Geography Markup Language (GML) tailored to the specific requirements for the representation of aeronautical objects, including the temporality feature that allows for time dependent changes affecting AIXM features. FAA and EUROCONTROL are using AIXM as an integral part of their efforts to modernize their aeronautical information procedures and to transition to a net-centric, global aeronautical management capability. More specifically, AIXM is being used in the net-centric System Wide Information Management (SWIM)-related components of the US NextGen and European Union (EU)'s SESAR programs. Indeed, it is expected that the results of the Aviation Thread of OWS-7 will be contributed to both programs with a focus on recommended OGC specifications that can be applied in the definition and implementation of both SWIM environments. 

WXXM is also jointly developed by FAA and EUROCONTROL, as a proposed standard for the exchange of aeronautical weather information in the context of a net-centric and global interoperable Air Transport System (ATS). WXXM also uses GML tailored to the specific requirements of aeronautical meteorology and is based on the OGC Observation and Measurement Model. WXXM development is harmonized and coordinated with the World Meteorological Organization (WMO), the organization traditionally responsible for standards in meteorology.

The OWS-7 Aviation Thread will investigate and demonstrate the applicability of AIXM and WXXM along with relevant OGC specifications and web services to applications and tools that support Airline Operations Centers and Flight Dispatch applications. Such applications provide information for representing a Common Operating Picture; supporting flight planning (including General Aviation) and preparation (MET and AIM); calculating weight and balance; estimating fuel requirements; in-flight emergency response; etc. The primary focus in OWS-7 is on ground usage of the information, although provision of information packages to the crew, on the ground and in the air, is also of interest.

To support the above goal, the OWS-7 Aviation Thread will cover the following tasks:

  • Evaluation and advancement of AIXM, in the areas of using and testing new AIXM 5.1 features, developing components/tools for generating, validating, converting, and parsing AIXM, addressing feature metadata requirements and performance constraints, and supporting the portrayal of AIXM information.
  • Evaluation and advancement of WXXM, focusing on the incorporation and demonstration new weather concepts such as the 4-D Weather Data Cube, including the impact of such concepts on the Event Notification Architecture, the support for probabilistic events, and the definition and usage of the time model in WXXM.
  • Advancement of the Event Notification Architecture developed and exercised in OWS-6 to support multiple sources of events and multiple types of events and data changes (AIXM, WXXM), and to investigate different delivery protocols (push/pull), registration and subscription lifecycle management approaches, and domain/schema-specific matching between events and subscriptions.
  • Integration of AIXM/WXXM in the FAA SWIM environment, focusing on investigating approaches for leveraging SWIM Interface Management, Messaging and Security capabilities, as well as enabling Aviation clients to access SWIM services in addition to OGC services.
Downloads: 
Proposals for cost reimbursement are due by 1 December 2009, 5:00 p.m. EST.
 
For those who have done this before: Please do not reuse old templates, but use our new ones. Thanks!

Click a link to download the .zip archive:

DOWNLOAD COMPLETE PACKAGE


Complete OGC Web Services, Phase 7 (OWS-7) RFQ (pdf  zip format)

Complete OGC Web Services, Phase 7 (OWS-7) RFQ (doc  zip format)

OR INDIVIDUAL FILES

OGC Web Services, Phase 7 (OWS-7) RFQ Main Body (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Main Body (doc)

OGC Web Services, Phase 7 (OWS-7) RFQ Annex A (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex A (doc)

OGC Web Services, Phase 7 (OWS-7) RFQ Annex B (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex B (doc)

OGC Web Services, Phase 7 (OWS-7) RFQ Annex C (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex C (doc)

OGC Web Services, Phase 7 (OWS-7) RFQ Annex D (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex D (doc)

 OGC Web Services, Phase 7 (OWS-7) RFQ Template - Funding (xls)
OGC Web Services, Phase 7 (OWS-7) RFQ Template - Proposal (doc)
 

Clarifications

Download the final clarifications from the bidder's conference.

We will accept further questions through Thursday, 19-November, which I will post by Friday, 20-November. Then proposals are due by 1-December at 5pm US Eastern.

 

Bidder's Conference Information

The Bidder's Conference was held on 10 November 2009.  Further questions may be directed by email to techdesk [at] opengeospatial.org until Nov 19.

The above Clarification document has been updated to reflect the questions presented during the Bidder's Conference.

OGC Requests: 

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

Status: 
Please note: This Request closed on 14 January 2011.

 

Description: 

 

RFQ Issuance Date: 22 November 2010

OWS-8 Bidder's Conference: 6 December 2010, 10:00-11:30am US EST
Proposal Due Date:
14 January 2011, 5:00 p.m. EST.

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

OGC members who wish to observe OWS-8 may do so upon submission of the OGC Observer Agreement: 
http://bit.ly/aTGi8T

Overview

OWS testbeds are part of OGC's Interoperability Program, 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, international teams of technology providers work together to solve specific geoprocessing 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 OGC standards.

 

The OWS-8 sponsors are organizations seeking open standards for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommend to the sponsors that the content of the OWS-8 initiative be organized around the following threads:

  • Observation Fusion
  • Geosynchronization (Gsync)
  • Cross-Community Interoperability (CCI)
  • Aviation

OWS-8 Sponsors

  • U.S. National Geospatial-Intelligence Agency (NGA)
  • U.S. Geological Survey (USGS)
  • U.S. Army Geospatial Center (AGC)
  • U.S. Federal Aviation Administration (FAA)
  • EUROCONTROL
  • U.S. National Oceanic and Atmospheric Administration (NOAA)
  • U.S. National Aeronautics and Space Administration (NASA)
  • European Space Agency (ESA)
  • U.K. Defence, Science and Technology Laboratary (DSTL)
  • Lockheed Martin Corporation

OWS-8 Threads

In July 2010, the OGC issued a call for sponsors for the OWS-8 interoperability initiative to advance OGC's open framework for interoperability in the geospatial industry.  Two meetings were conducted with potential OWS-8 sponsors to review the OGC technical baseline, discuss OWS-7 results, and identify new requirements to be addressed in OWS-8.  The following organization and scope of activity threads resulted from consolidation of all sponsors’ requirements:

  • Observation Fusion
    • WCS 2.0 Earth Observation Application Profile, WCPS, Compliance Test Scripts
    • Detection, tracking, and bookmarking of moving objects in video, implemented using SWE and other OGC encodings and interfaces.
  • Geosynchronization
    • Geodata Bulk Transfer: The ability to distribute individual data sets and/or collections of data sets in a consistent manner offline and over networks.
    • Geosynchronization: Web services and client components to support synchronization and updates of geospatial data across a hierarchical Spatial Data Infrastructure (SDI).
  • Cross-Community Interoperability (CCI)
    • Advancement of semantic mediation approaches to query and use data based on different heterogeneous data models, which are available via OGC WFS.
    • Advancement of the use of style registries and styling services.
    • Advancement of the use of KML.
    • Advancement of the use of UML/OCL for Schema Automation on Domain Models.
  • Aviation
    • AIXM: Maturing the delivery, filtering and update of AIXM 5.1 using WFS-T/FE 2.0; continuing the development of reusable tools, benchmarking of compression techniques for enhanced performance, advancing styling and portrayal support, and validating the emerging metadata and GML profiles.
    • Event Notification Architecture: including Digital NOTAM Events.
    • WXXM and weather information: using coverages for encoding representative weather forecast and radar datasets, supporting on-demand Coordinate Reference System (CRS) specifications/transformations, exploring alternative distributed architectures for managing Units of Measure (UoM), demonstrating the applications of probabilistic Terminal Aerodrome Forecasts (TAF) decision making applications, and reviewing/validating the WXXM schemas.

Schedule of Events and Milestones

  • Request for Quotation / Call for Participation (RFQ/CFP): 22 November 2010
  • Bidders Conference (Q&A with WebEx): 6 December 2010. Go to the WebEx calendar here: http://opengeospatial.webex.com/ and look for the OWS8 Bidders event.
  • Last date for submitting questions or changes to the RFQ: 15 December 2010
  • Proposals due: 14 January 2011
  • Participant selections completed: 28 January 2011
  • OWS-8 Kickoff (3-day workshop in DC area, attendance required): 9-11 March 2011
  • OWS-8 Completion (final reports due): 30 September 2011

Live demonstrations of OWS-8 results will be conducted at the September 2011 OGC Technical Committee meeting in Boulder, Colorado USA 

Demonstration videos of the testbed results will be posted for public viewing within 30 days of testbed completion. 

Downloads: 
Proposals for cost reimbursement are due by 14 January 2011, 17:00 p.m. EST.
 
For those who have done this before: Please do not reuse old templates, but use our new ones. Thanks!

Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE


Complete OGC Web Services, Phase 8 (OWS-8) RFQ (pdf  zip format)
Complete OGC Web Services, Phase 8 (OWS-8) RFQ (doc  zip format)

OR INDIVIDUAL FILES

OGC Web Services, Phase 8 (OWS-8) RFQ Main Body (pdf)
OGC Web Services, Phase 8 (OWS-8) RFQ Main Body (doc)

OGC Web Services, Phase 8 (OWS-8) RFQ Annex A (pdf)
OGC Web Services, Phase 8 (OWS-8) RFQ Annex A (doc)

OGC Web Services, Phase 8 (OWS-8) RFQ Annex B (pdf)
OGC Web Services, Phase 8 (OWS-8) RFQ Annex B (doc)

OGC Web Services, Phase 8 (OWS-8) RFQ Annex C (pdf)
OGC Web Services, Phase 8 (OWS-8) RFQ Annex C (doc)

OGC Web Services, Phase 8 (OWS-8) RFQ Annex D (pdf)
OGC Web Services, Phase 8 (OWS-8) RFQ Annex D (doc)

 OGC Web Services, Phase 8 (OWS-8) RFQ Template - Funding (xls)
OGC Web Services, Phase 8 (OWS-8) RFQ Template - Proposal (doc)
 

Questions: Bidder's Conference

 A Bidder's Conference (webinar) was held Monday 6 December 201010:00-11:30am US EST to discuss all communications received since the RFQ release. You can download and view the “OWS8 Bidders Conference” video.

 

 

 

Clarifications Document

All Q&A, updates, and other information about OWS-8 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 until 15 December 2010. After this date, no further questions or clarifications will be posted. The Clarifications Document is here:

Clarifications - pdf
Clarifications - doc

OGC Requests: 

OpenGIS® Catalogue Services - ebRIM profile of CSW (ebRIM): Request for Public Comments

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) is contemplating adoption of a technology called OpenGIS® Catalogue Services - ebRIM profile of CSW (ebRIM). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Application Profile. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for OpenGIS® Catalogue Services - ebRIM profile of CSW (ebRIM). Documentation of this draft specification can be downloaded here:

Candidate Submission: Mon, 2005-10-17 09:00
Close request period: Fri, 2005-11-11 09:00
TC and PC vote to issue request: Fri, 2006-01-20 09:00
Begin request period: Sun, 2006-02-19 09:00
 

Downloads: 


This document defines an application profile of an OGC Catalogue service; it is primarily based on the HTTP binding (the CSW part) described in Clause 11 of the OGC Catalogue Services Specification, version 2.0 (OGC 04-021r3). The profile constrains the usage of several base specifications and introduces some additional search, retrieval, and transaction capabilities.
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] 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: 

OpenGIS® Catalogue Services Specification 2.0.1 (with Corrigendum) - ISO Metadata Application Profile (CSW2 AP ISO): RFP

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) is contemplating adoption of a technology called OpenGIS® Catalogue Services Specification 2.0.1 (with Corrigendum) - ISO Metadata Application Profile (CSW2 AP ISO). 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 purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed Application Profile required for OpenGIS® Catalogue Services Specification 2.0.1 (with Corrigendum) - ISO Metadata Application Profile (CSW2 AP ISO). Documentation of this draft specification can be downloaded here:

Candidate Submission: Fri, 2006-01-20 15:00
Close request period: Fri, 2006-03-10 15:00
TC and PC vote to issue request: Thu, 2006-04-20 15:00
Begin request period: Sat, 2006-05-20 15:00
 

Downloads: 

This application profile document specifies the interfaces, bindings, and encodings required to publish and access digital catalogues of metadata for geospatial data, services, and applications that comply with the given profile. Metadata act as generalised properties that can be queried and returned through catalogue services for resource evaluation and, in many cases, invocation or retrieval of the referenced resources.
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] 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: 

OpenGIS® Sensor Model Language (SensorML): Request for Public Comments

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) is contemplating adoption of a technology called OpenGIS® Sensor Model Language (SensorML). 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 purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed encodings required for OpenGIS® Sensor Model Language (SensorML). Documentation of this draft specification can be downloaded here:

Candidate Submission: Wed, 2006-02-01 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-05 16:00
Begin request period: Fri, 2006-05-05 16:00
 

Downloads: 

This document specifies models and XML encoding for the core SensorML. SensorML provides a common framework for any process and process chain. Within SensorML, sensors and transducer components (detectors, transmitters, actuators, and filters) are all modelled as processes that can be connected and participate equally within a process chain, and which utilize the same process model frame as any other process.
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] 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: 

OpenGIS® Sensor Observation Service (SOS): Request for Public Comments

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) is contemplating adoption of a technology called OpenGIS® Sensor Observation Service (SOS). 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 purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for OpenGIS® Sensor Observation Service (SOS). Documentation of this draft specification can be downloaded here:

Candidate Submission: Thu, 2006-02-02 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-05 16:00
Begin request period: Fri, 2006-05-05 16:00
 

Downloads: 

This document specifies Sensor Observation Service. A Sensor Observation Service 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
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] 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: 

OpenGIS® Sensor Planning Service (SPS): Request for Public Comments

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) is contemplating adoption of a technology called OpenGIS® Sensor Planning Service (SPS). 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 purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for OpenGIS® Sensor Planning Service (SPS). Documentation of this draft specification can be downloaded here:

Candidate Submission: Tue, 2006-02-21 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-12 16:00
Begin request period: Fri, 2006-05-12 16:00

 

Downloads: 

This OpenGIS® document specifies interfaces for requesting information describing the capabilities of a Sensor Planning Service, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task.
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] 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: 

OpenGIS® Transducer Markup Language (TML): Request for Public Comments

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) is contemplating adoption of a technology called OpenGIS® Transducer Markup Language (TML). 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 purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed encodings required for OpenGIS® Transducer Markup Language (TML). Documentation of this draft specification can be downloaded here:

Candidate Submission: Fri, 2006-02-03 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-05 16:00
Begin request period: Fri, 2006-05-05 16:00
 

Downloads: 

This document describes TML and how it captures necessary information to both understand and process transducer data. Descriptions of how TML captures the actual data and also descriptions of necessary information such as system calibration, transducer behavior, conditions of operation and data collection parameters critical to logical data structure model are all captured within TML. This document specifically describes the TML transducer behavior models and TML data models. It does not describe a service for delivering TML-structured data, but there is a brief discussion of SOA and streaming platform considerations.
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] 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: 

OWS-5 Testbed Addendum Released

Status: 
Please note: This Request is closed.
Description: 
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:

  1. GeoSynchronization
  2. OWS Core and Extension Experiment

1) GeoSynchronization

GeoSynchronization targets a federated environment comprised of loosely affiliated parties who desire to collaborate on the development and maintenance of a shared geospatial data set. Additionally, technology is enabling new online markets for information sharing and processing to emerge. These too can achieve cost and time benefits from leveraging loosely coupled, industry standards for sharing and synchronization. Solving this interoperability issue is of critical importance to ongoing Spatial Data Infrastructure (SDI) initiatives across the globe, as parties with differing software infrastructures, organizational goals, and legal mandates seek to increase the availability of geospatial information across society without incurring prohibitive costs. While existing OGC technologies have made it easier to publish information in an interoperable manner, creating the potential for effective sharing and collaboration, another level of interoperability technology is required to manage the intricacies of cross-organizational data sharing, which may include acceptance, validation, rejection, and description of operations on information streams.

In this testbed participants will be funded to experiment with solutions that leverage GML-based information models, such as the GML profiles being developed for US framework data sets and the Canadian Geospatial Data Infrastructure. Mass market information models, such as Atom+GeoRSS GML and KML may be considered as well. It is expected that investigations in this area will likely extend the WFS Transactional architecture to accommodate a more loosely coupled approach. However, alternative architectures will be considered as well.

 

2) OWS Core and Extension Experiment

The OGC in general, and the OGC Architecture Board (OAB) in particular, is considering a more formal, modular approach to standards that is described in "OGC Abstract Specification - The Model Specification - Structuring an OGC specification to encourage implementation, version 07-056r2". In support of this effort, this OWS-5 task uses the guidance from this document and applies it to the "OpenGIS® Web Feature Service (WFS) Implementation Specification", "Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification", and the Web Processing Service.


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: 

Pages