OGC Requests

OGC Seeks Comments on NetCDF Climate and Forecast Data Encoding Standards

Status: 
Please note: This Request is scheduled to close on 7 October, 2010.
Description: 

The Open Geospatial Consortium (OGC®) members are seeking comments on three candidate standards – the OGC CF-netCDF Primer, OGC Network Common Data Form (NetCDF) Core Encoding Standard, and the OGC NetCDF Binary Encoding Extension Standard - NetCDF Classic and 64-bit Offset Format.


NetCDF (network Common Data Form) is comprised of a data model for array-oriented scientific data, related access libraries, and a machine-independent data format. Together, the interfaces, libraries, and format support the creation, access, and sharing of georeferenced scientific data.


NetCDF and CF-NetCDF were developed by the weather and climate communities and have been maintained by the University Corporation for Atmospheric Research (UCAR) (www.ucar.edu).  These standards has been formally recognized by US Government standards bodies. UCAR introduced NetCDF into the OGC as a candidate OGC standard to encourage broader international use and greater interoperability among clients and servers interchanging data in binary form. Establishing CF-netCDF as an OGC standard for binary encoding will enable standard delivery of data in binary form via several OGC service interface standards, including the OGC Web Coverage Service (WCS), Web Feature Service (WFS), and Sensor Observation Service (SOS) Interface Standards.


The following organizations submitted these candidate standards to the Open Geospatial Consortium:

IMAA-CNR Italy

METEO-FRANCE

Natural Environment Research Council (NERC)

Northrop Grumman Corporation

University Corporation for Atmospheric Research (UCAR)

US National Oceanic and Atmospheric Administration (NOAA)


The candidate OGC OGC standards and information about submitting comments on this document are available below. The public comment period closes on 7 October , 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 NetCDF Enhanced Data Model Extension Standard

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

The Open Geospatial Consortium (OGC®) membership seeks comments on an OGC candidate standard, the Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Encoding Standard. This document specifies an extension to the existing OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0.

The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. NetCDF (network Common Data Form) is widely used internationally to communicate and store many kinds of multidimensional data, although it was originally developed for the Earth science community. The netCDF data model is particularly well suited to providing data in forms familiar to atmospheric and oceanic scientists: namely, as sets of related arrays. NetCDF was developed and is maintained and actively supported by the Unidata Program Center (http://www.unidata.ucar.edu) of the University Corporation for Atmospheric Research (UCAR).
 
The netCDF classic data model has previously been established as the core OGC CF-netCDF standard. With this extension to the core standard for the enhanced data model, complex data structures can be represented very easily, allowing for more efficient programming. In performance-critical applications, the enhanced model provides significant benefits. Moreover, if existing HDF5 (Hierarchical Data Format, release 5) applications that depend on groups, user-defined types, unsigned types, or strings produce or use these data, the netCDF enhanced data model is required. The recently introduced candidate NetCDF Enhanced Data Model Extension Encoding Standard is the latest step in a longer-term plan for establishing CF-netCDF as an OGC standard for binary encoding, which will enable standard delivery of data in binary form via several OGC service interface standards, including the OGC Web Coverage Service (WCS), Web Feature Service (WFS), and Sensor Observation Service (SOS) Interface Standards.
 
The candidate OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Encoding Standard and information about submitting comments on this document are available below. The public comment period closes on July 1, 2012.
Comment: 

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

Subscribe: 

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


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

OGC Requests: 

OGC Seeks Comments on Open GeoSMS Standard - Core

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

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC Open GeoSMS Standard - Core.

The candidate OGC Open GeoSMS Standard allows applications to location enable Short Message Service (SMS). SMS is the text communication service component of phone, web and mobile communication systems. SMS uses standardized communications protocols that allow the exchange of short text messages between fixed line or mobile phone devices.

Open GeoSMS enables developers to use extended Short Message Service (SMS) to facilitate communication of location content between different LBS (Location-Based Service) devices or applications. The encoding is extremely light weight and the standards document is quite short.
 
The Taiwan Industrial Technology Research Institute (ITRI) contributed this candidate standard to the OGC. Open GeoSMS is already in use in a number of deployed commercial applications in Taiwan as well as in a number of disaster response applications such as those provided by Sahana.

The candidate OGC Open GeoSMS Standard can be found below.  The period for issuing comments expires on 24 April 2011.

Comment: 

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

Subscribe: 

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


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

OGC Requests: 

OGC Seeks Comments on Ordering Service Candidate Standard

Status: 
Please note: This Request is scheduled to close on 23 February 2011.
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC Ordering Services for Earth Observation Products Interface Standard. This candidate interface standard defines interfaces for ordering products derived from Earth observation satellites. In particular it provides interfaces for:

Getting the processing and delivery options available for specific Earth observation products

Getting the price quotation for an order to be submitted

Submitting the order

Monitoring the status of the submitted orders and optionally cancelling them

Retrieving the products (on-line, if supported by the server)

 

 

This candidate standard has been prepared by the OGC Technical Committee Ordering Standards Working Group and it is based on an existing specification prepared and implemented in several ESA (European Space Agency) projects. Currently, implementations are available from at least the following space agencies:

• ESA

• Eumetsat

• DLR

Other implementations are being developed, including those being developed in GMES-related activities.

 

This candidate standard is designed to work with the OGC Sensor Web Enablement (SWE) suite of standards: For the modelling of ordering options the SWE Common specification has been selected and some elements are shared with the OGC Sensor Planning Service Interface Standard (SPS).

 

The candidate OGC Ordering Services for Earth Observation Products Interface Standard can be found below. The period for issuing comments expires on 23 February 2011.

Comment: 

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

Subscribe: 

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


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

OGC Requests: 

OGC Seeks Comments on Sensor Observation Service Candidate Standard

Status: 
Please note: This Request is scheduled to close on 1 December, 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the candidate OGC Sensor Observation Service (SOS) Standard Version 2.0. The SOS candidate interface standard is designed to provide access to sensor observations, sensor descriptions, and digital representations of observed features in an interoperable and standardized way. Further, the SOS 2.0 candidate standard provides means to insert new sensor descriptions or observations.

 

The OGC Sensor Observation Service revision incorporates several enhancements. These include a modular restructuring of the document, new KVP and SOAP bindings, redesign of the observation offering concept, and reliance on the OGC Sensor Web Enablement Service Model. SOS 2.0 is highly modular and follows the OGC core/extension design pattern. The main SOS 2.0 document incorporates the core as well as the transactional extension, result handling extension, enhanced operations extension, binding extension, and a profile for spatial filtering of observations. An additional document specifies the extension for the operation to retrieve metadata about the observations stored by a service.

 

The proposed OGC SOS 2.0 standard and information on submitting comments on this document are available below.  The public comment period closes on 1 December 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] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

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


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

OGC Requests: 

OGC Seeks 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: 

Pages