OGC Requests

OGC Seeks Comments on Sensor Planning Service Standard 2.0

Status: 
Please note: This Request is scheduled to close on 14 April 2010.
Description: 
The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the draft OGC Sensor Planning Service (SPS) Interface Standard 2.0. This draft standard specifies interfaces for tasking a sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor tasking 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.

The proposed OGC SPS 2.0 standard and information on submitting comments on this document are available below.  The public comment period closes on 14 April, 2010.

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: 

OGC Seeks Comments on SWE Common Service Model Interface Standard

Status: 
Please note: This Request is scheduled to close on 25 April 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the candidate OGC Sensor Web Enablement (SWE) Common Service Model Interface Standard Version 2.0. The SWE Service Model provides a common set of data types and defines a common set of interface mechanisms that can be used with other SWE interface standards.

There are two "SWE Common" standards: The OGC SWE Common Service Model Interface Standard is applicable to all services that provide or require information from or about sensors. It is designed for uses cases in which sensors need to be accessed and managed through service interfaces. A related standard, the OGC SWE Common Encoding Standard, provides a standard model (and XML implementation of the model) for the representation, nature, structure and encoding of sensor related data. It is used for describing static data (files) as well as dynamically generated datasets (on-the-fly processing), real-time streaming data, and process and web service inputs and outputs.

Both of the SWE Common standards are designed to be used with other existing OGC® Sensor Web Enablement standards such as OGC Sensor Model Language (SensorML) Encoding Standard, Sensor Observation Service (SOS) Interface Standard and Sensor Planning Service (SPS) Interface Standard.

The proposed OGC SWE Service Model 2.0 Standard and information on submitting comments on this document are available below. The public comment period closes on 25 April 2010.

 

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: 

OGC Seeks Comments on “SWE Common” Data Model

Status: 
Please note: This Request is scheduled to close on 14 April 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the draft OGC Sensor Web Enablement (SWE) Common Encoding Standard Version 2.0.  The SWE Common standard provides a common data encoding that is used throughout the OGC Sensor Web Enablement (SWE) standards suite. More precisely, the SWE Common model is used to define the representation, nature, structure and encoding of sensor related data.

 

This model is used for describing static data (files) as well as dynamically generated datasets (on-the-fly processing), data subsets, process and web service inputs and outputs and real time streaming data. All categories of sensor observations are in scope ranging from simple in-situ temperature data to satellite imagery and full motion video streamed out of an aircraft.

 

The SWE Common language is an XML implementation of this model and is used by other existing OGC® Sensor Web Enablement standards such as Sensor Model Language (SensorML), Sensor Observation Service (SOS), Sensor Alert Service (SAS) and Sensor Planning Service (SPS).

 

The proposed OGC SWE Common 2.0 standard and information on submitting comments on this document are available below.  The public comment period closes on 14 April 2010.

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: 

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

Status: 
This Request is Closed.
Description: 
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.

In January of 2007, the OGC issued a call for sponsors for an OGC OWS-5 Interoperability initiative testbed activity to advance OGC's open framework for interoperability in the geospatial industry. Three meetings were conducted with potential OWS-5 sponsors to review the OGC technical baseline, to discuss OWS-4 results, and to identify OWS-5 requirements. Sponsors have expressed keen interest in advancing standards for geospatial workflow, sensor webs, geospatial digital rights management, GML information communities, and KML. After analyzing the sponsors input, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-5 initiative be organized around the following 6 threads:

  1. Sensor Web Enablement (SWE)
  2. Geo Processing Workflow (GPW)
  3. Information Communities and Semantics (ICS)
  4. Agile Geography
  5. Compliance Testing (CITE)
  6. CAD / GIS / BIM

Introductions to these 6 threads are below.


OWS-5 Sponsors

  • BAE Systems - Network Systems
  • Google
  • Lockheed Martin Integrated Systems & Solutions
  • Northrop Grumman
  • US National Aeronautic and Space Administration (NASA)
  • US National Geospatial-Intelligence Agency (NGA)

OWS-5 Threads

1) Sensor Web Enablement (SWE)

The Sensor Web subtask will continue to mature the existing set of SWE work items to enable the federation of sensors, platforms and management infrastructure into a single sensor enterprise. In OWS-5,interoperability engineering activities will focus on integration and demonstration of physical sensors and simulators within a realistic operating environment. In addition, progress is expected on enhancements to the SWE specifications as described in the "Future work" clauses of the respective baseline documents.

Emphasis for SWE during this phase of the OWS project will be on:

  • Leveraging results of OWS-4 to extend and integrate those specifications and implementations.
  • Demonstrating SWE's ability to meet the geospatial needs of large enterprise system by integrating SWE into realistic enterprise workflow scenarios supported by Use Cases.
  • Continuing previous test-bed efforts to integrate IEEE 1451 sensor into SWE
  • Establishing cross thread collaboration with CGB by integrating sensors into 3D models.
  • Harmonizing SWE concepts and specifications with other OGC specifications and initiatives.
  • Developing compliance test for SWE specification to accelerate adoption

2) Geo Processing Workflow (GPW)

No geo-process is an island, or more exactly no geo-process should be an island. By interconnecting geo-processes through service chaining and orchestration to meet workflow requirements, creation of valued-added enterprise systems is possible that demonstrate the power of interoperability and service oriented architectures. The OWS-2 Image Handling for Decision Support (IH4DS) thread extended the baseline of OWS service types with image processing services. OWS-3 Common Architecture activities built on that work by applying the services developed in OWS-2 to the SWE and GeoDSS environments. OWS-4 furthered workflow service development by investigating the patterns for building general purpose geo-processing services and prototyping a feature editing scenario.

OWS-5 will further mature geoprocessing workflows by bringing together more services in real-world image processing scenarios, developing a SOAP/WSDL framework for all OGC services, and incorporating rights-based access to resources. The GPW thread in this testbed is organized into the following inter-related work areas:

  • Enterprise integration and refinement of OGC Web Service architecture
  • Enterprise integration of OGC Web Services using service chaining and workflow to implement the full service life cycle for the Publish-Find-Bind pattern
  • Integrate GeoRM services and components in the workflow with focus on Identity, Authorization, Authentication and Trust model

3) Information Communities and Semantics (ICS)

The ICS thread seeks to advance the understanding and use of complex geographic information types within an interoperability architecture. A variety of geospatial data types will be modeled in UML and converted into GML using the UGAS ShapeChange tool. Information about these data and the services provisioning them will be registered in a number of catalogs and utilized in workflows developed in the GPW thread.

This activity will test the ability of OGC standards to facilitate one of the core scenarios in any spatial data infrastructure-information publication.

4) Agile Geography

This testbed focuses on process integration and ‘right-sizing' of services to demonstrate the power of interoperability and service-oriented architectures using OGC Web Services. The Agile Geography thread explores this goal through two distinct activities.

The first explores the future of KML, OWS Context, and lightweight payloads of geospatial information on the Web in general, applying the concepts of links, bookmarks and Web pages to digital cartography and geospatial information management. Participants will explore the harmonization of KML and OWS Context XML encodings and prototype client and server software that exploits these document types.

The second activity-GeoSynchronization and Sharing-extends the WFS-Transactional architecture to target a federated environment comprised of loosely affiliated parties who desire to collaborate, in full or in part, on the maintenance of a shared geospatial data set.

5) Compliance Testing (CITE)

The OGC Interoperability Program and the OGC Specification Program have achieved a great deal of momentum as a result of the multiple OGC Web service specifications that have recently been published. Key consumers in the geospatial industry are modernizing their enterprises and realizing spatial data infrastructures (SDIs) based on the applicability and interoperability of OGC web services.

The major geospatial industry consumers require verifiable proof of compliance with OGC specifications in order to reach the desirable outcome of interoperability. In OWS-5 the CITE thread advances testing for Web Coverage Service and Catalog Service for the Web to versions 1.1 and 2.0.2 respectively. OWS-5 also initiates Sensor Web compliance testing, with the first Sensor Observation Service and Sensor Planning Service tests.

Also included in the requirements are reference implementations of these specifications. A reference implementation is an open source, fully functional implementation of a specification in reference to which other implementations can be evaluated. The OGC provides open source reference implementations to ensure maximum transparency of its specifications for both vendors and customers.

6) CAD / GIS / BIM (CGB)

NOTE: Work items within the CAD/GIS/BIM thread are provided for comment -- with the anticipation that CGB will be conducted in Phase 2. Comments on CGB are solicited now to support a future RFQ/CFP for Phase 5.2 as defined in Master Schedule.

The CGB activities in the OWS program are directed toward bridging the information models and workflows of the various communities involved with the representation of the built environment in three dimensions. Standards for interoperable exchange of information about buildings and standards for representing and exchanging information about cities at broad-scale are beginning to enable owners, administrators and toolmakers to make investments in developing assets based on these standards. Applications of integrated city models are emerging in the mass-market sphere, witness Google Earth and Microsoft Local Live. One can imagine the extension of these tools into the domains of location-based services to emergency preparedness and response. These applications will require the integration of semantically rich authoritative information that is likely to be created in a highly distributed fashion. This thread of OWS-5 focuses on developing a services-based architecture that will bring the necessary information together, and to make it accessible in a secure way.

Downloads: 

Proposals for cost reimbursement are due by June 8, 2007.

Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE
Complete OGC Web Services, Phase 5 (OWS-5) RFQ (zip format)

OGC Web Services, Phase 5 (OWS-5) Bidder's Conference Information


A Bidder's Conference is currently scheduled for May 22.
Time: 15:00 UTC, 5:00 PM CEST, 11:00 AM EDT, 8:00 AM PDT
Phone line: +1 512-225-3050 passcode:36429#.

Clarifications to OWS-5 RFQ/CFP

The following clarifications apply to the Request for Quotation/Call for Participation in OGC Web Services, Phase 5 (OWS-5) as issued on 11 May 2007. This list will be updated as additional clarifications are needed. The most current list will always be posted here:

Download OWS-5 RFQ/CFP Clarifications

 


OGC Requests: 

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

Status: 
Please note:  As of October 31, this Request is CLOSED to further proposals.
Description: 
RFQ Issuance Date: 21 July 2008
OWS-6 Bidder's Conference: 8 August 2008
Proposal Due Date: 5 September 2008

 


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-6 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-6 initiative be organized around the following threads:

  1. Sensor Web Enablement (SWE)
  2. Geo Processing Workflow (GPW)
  3. Aeronautical Information Management (AIM)
  4. Decision Support Services (DSS)
  5. Compliance Testing (CITE)

OWS-6 Sponsors

  • U.S. National Geospatial-Intelligence Agency (NGA)
  • Joint Program Executive Office for Chemical and Biological Defense (JPEO-CBD)
  • GeoConnections - Natural Resources Canada
  • U.S. Federal Aviation Agency (FAA)
  • EUROCONTROL
  • EADS Defence and Communications Systems
  • US Geological Survey
  • Lockheed Martin
  • BAE Systems
  • ERDAS, Inc.

OWS-6 Threads

1) Sensor Web Enablement (SWE)

The OGC Sensor Web Enablement framework has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. OWS-6 will focus on integrating the SWE interfaces and encodings into cross-thread scenarios and workflows to demonstrate the ability of SWE specifications to support operational needs. Emphasis for SWE during this phase of the OWS test-bed will be on:

  • CCSI-Enabled CBRN Sensors into the SWE Environment
  • Build on Georeferenceable imagery accomplishments of OWS-5
  • Harmonize SWE-related information models: SensorML, GML, UncertML, MathML
  • Apply GeoRM, Trusted Services, and security models in SWE environment
  • Events-based architecture including WNS

2) Geo Processing Workflow (GPW)

This GPW thread aims to build on the progress of previous testbeds with a focus on maturing the interoperability and capabilities of OGC web services in a service-oriented architecture with particular emphasis to address OGC web service security issues. To satisfy mission-critical goals, the architecture must not only provide for integration of a wide variety of service capabilities and resources, it must do so and ensure authenticity, integrity, quality and confidentiality of services and information. To meet these goals, the following task areas have been identified:

  • Asynchronous Workflow and Web Services Security
  • Data Security for OGC web services
  • Data Accessibility
  • WPS Profiles - Conflation; and Grid processing
  • GML Application Schema Development & ShapeChange Enhancements

3) Aeronautical Information Management (AIM)

The Aviation Information Management (AIM) subtask is a new thread within OWS to develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) in an OGC Web Services environment. The AIM subtask shall focus on evaluating and advancing various AIXM features in a realistic trans-Atlantic aviation scenario setting by devising and prototyping a Web Services Architecture for providing valuable aeronautical information directly to flight decks, Electronic Flight Bags (EFB) and hand-held devices (such as PDAs and Blackberries) while the airplane is at the gate or en-route to its destination (for the purposes of OWS-6, the aeronautical information in the latter case does not depend on the knowledge of the airplane's location).

AIXM was developed by the Federal Aviation Administration (FAA) and Eurocontrol as a global standard for the representation and exchange of aeronautical information. It was designed as a basis for digital aeronautical information exchange and for enabling the transition to a net-centric, global aeronautical management capability. AIXM has been developed using the ISO 19100 modeling framework and has two major components: a conceptual model presented in the form of an UML class model and a data encoding specification which was developed using the OGC Geography Markup Language (GML). Both have been tailored to the specific requirements for the representation of aeronautical objects, especially the temporality feature that allows for time-dependent changes affecting AIXM features. More information about AIXM is available on www.aixm.aero. In support of the above objectives, the OWS-6 AIM thread shall perform tasks in the following areas while ensuring that the integrity of data is preserved throughout all data exchange operations:

  • Use and enhancement of Web Feature Service and Filter Encoding specifications in support of AIXM features and 4-dimensional flight trajectory queries,
  • Prototype of Aviation client for retrieval and seamless visualization of AIXM, Weather and other aviation-related data, emphasizing time and spatial filtering in order to present just the right information into a given user context anytime, anywhere,
  • Architecture of standards-based mechanism to notify users of changes to user-selected aeronautical information.

4) Decision Support Services (DSS)

Decision Support Services having an emphasis on applications of geospatial and temporal information has been a recurring thread in previous OWS testbeds. This thread focuses on presenting and interacting with data obtained from the sensor web and geoprocessing workflows in the most effective ways to support analysis and decision making. The focus for DSS in OWS-6 builds on portrayal, WMS Tiling, and integrated client work from OWS-4, with additional work on 3D visualization and integration of the built environment and landscape. This thread will encompass these capabilities and task areas:

  • ISO 19117 and OGC SLD Portrayal
  • 3D Portrayal of GML with Fly-through
  • Hosting CityGML data with WFS
  • Outdoor and indoor 3D route and tracking services
  • WMS performance (tiling)
  • Integrated Client for multiple OWS services

5) Compliance Testing (CITE)

Validating compliance with an OGC specification means verifying that a software product has implemented the specification correctly by testing the software interface for response and behavior that is outlined in the specification. Verifying compliance to the standard is necessary in order to achieve interoperability. As a result, geospatial application vendors desire to provide their potential costumers a means to verify adherence to OGC standards as a measurable discriminator for the interoperability of software products. Similarly, users desire assurance that acquired software components will interoperate with their existing investments in OGC-compliant technology. The Conformance and Interoperability Test and Evaluation (CITE) thread is intended to provide the geospatial industry (consumers and vendors) a methodology and tools that will test compliance with OGC web services.

The OGC Interoperability Program and the OGC Specification Program have achieved a great deal of momentum as a result of the multiple OGC web service specifications that have recently been published. Key consumers in the geospatial industry are modernizing their enterprises based on the applicability and interoperability of OGC web services. The major geospatial industry consumers require verifiable proof of compliance with OGC specifications in order to reach the desirable outcome of interoperability. Furthermore, as the OGC technology stack has matured, a group of interfaces has emerged that represents a baseline of technology needed to implement a fully interoperable, end-to-end spatial data infrastructure. The CITE threads in previous OWS projects have made significant progress towards having a complete suite of compliance tests for this baseline of interfaces.

A major focus of OWS-5 was on achieving consensus on the format and content of an Abstract Test Suite (ATS). The OWS-5 CITE participants agreed to follow the ISO guidance for writing Abstract Test Suites. The ATS are used to develop Executable Test Suites which are the scripts that the TEAM Engine runs to conduct an automated compliance test. A major focus of OWS-6 CITE will be in clearly documenting the approach to defining Abstract Test Suites. This will be a great benefit to the OGC community as the OGC Architecture Board (OAB) requires that new specifications be published with an accompanying ATS. In addition, a focus of OWS-6 CITE will be to expand the usability of the existing OGC compliance tests by "tailoring" these tests for specific schema profiles and/or data.

Downloads: 

Proposals for cost reimbursement are due by September 5, 2008.

Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE
Complete OGC Web Services, Phase 6 (OWS-6) RFQ (zip format)

OGC Web Services, Phase 6 (OWS-6) Bidder's Conference Information


A Bidder's Conference is currently scheduled for 8 Aug 2008, 10am-noon US Eastern time.
Time: 14:00 UTC, 4:00 PM CEST, 10:00 AM EDT, 9:00AM CDT, 7:00 AM PDT
Phone line: +1 512-225-3050 passcode:36429#.
WebEx will also be used; connection instructions to be sent out before the meeting.

Clarifications to OWS-6 RFQ/CFP

The following clarifications apply to the Request for Quotation/Call for Participation in OGC Web Services, Phase 6 (OWS-6) as issued on 21 July 2008. This list will be updated as additional clarifications are needed. The most current list will always be posted here:

Clarifications have been posted .

 


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 (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: 

Pages