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 Seeks Comments on "NIL Extension" to Geography Markup Language (GML)

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

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate "GML-NIL profile" of the OGC Geography Markup Language (GML) Encoding standard. GML is a widely used XML grammar for encoding information about geographical features. The GML-NIL profile provides a way to allow data providers to make a best effort to supply data according to an application schema, even if they do not have values for all feature properties. This is achieved by marking the application schema as a whole as ‘nillable=true’ and using OGC ‘nil’ URIs in links for missing data. This reverses the usual pattern which has a default value of nillable=false.   

 

The GML-NIL pattern of use has been used informally for several years in Earth and environmental science applications, and this candidate standard merely aims to formalize and document the practice. It is expected to be useful in many applications where a heterogeneous community wishes to enable participation by a wide variety of members with different capabilities and data sources. The submission team is composed of members of the GeoSciML project.

 

The candidate OGC GML-NIL standard documents are available for review and comment below.

Downloads: 


 Nillable GML (12-110)   

 



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: 

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: 

Request for Comments (RFC) on the GeoLinking Service Standard

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

The membership of the Open Geospatial Consortium, Inc. (OGC) is requesting comments on the candidate standard OpenGIS(R) GeoLinking Service (GLS) Interface.

The candidate GLS standard defines an interface for services that provide the ability to "link" data that contain information about geographic objects, such as census tract population statistics, with data in another repository that contains the actual geometry (points, lines, polygons). For example, a table of populations of cities on one server may not contain the geometry information that describes the cities' locations and boundaries, while a second server may house the cities' geometry. The candidate GLS standard describes a set of interfaces for both servers that lets the city name be used as a "common geographic identifier" to join the population data to its geometry, so the user can create a map or perform geospatial analysis on the linked data.

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: 

The OGC seeks comment on GeoSynchronization Best Practices

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

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

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

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

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

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

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

Comment: 

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

Subscribe: 

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


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

OGC Requests: 

Request for Comment on KML 2.2

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 the KML 2.2 candidate standard. The OGC invites public comment on this candidate standard. All comments will be collated and used in the evaluation of KML 2.2 as an OGC standard. In late first quarter 2008, the OGC committee working on the KML 2.2 candidate standard will seek approval by OGC members for KML 2.2 an OpenGIS(R) Encoding Standard.

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

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for KML 2.2. Documentation of this draft standard can be downloaded below:

Candidate Submission: Thur, 2007-08-30
TC and PC vote to issue request: Fri, 2007-09-21
Begin request period: Tue, 2007-12-4
Close request period: Thu, 2008-01-03

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?SUBJECT=KML%202.2%20Comment&BODY=Part%20A%20to%20be%20completed%20once.%20%20Iterate%20Part%20B%20as%20needed.%0D%0DPART%20A%0D%0D1.%20Evaluator:%20%5BCONTACT%20INFORMATION%5D%0D%0D2.%20Submission:%20%5BOpenGIS%20Project%20Document%20Number,%20Name%5D%0D%0DPART%20B%0D%0D1.%20Requirement:%20%5BGeneral,%20#%5D%0D%0D2.%20Implementation%20Specification%20Section%20number:%20%5BGeneral,%20#%5D%0D%0D3.%20Criticality:%20%5BMajor,%20Minor,%20Editorial,%20etc.%5D%0D%0D4.%20Comments/justifications%20for%20changes:%20%5BComments%5D%0D%0D">Click here to submit comments The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

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

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

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

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

 

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

 

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

 

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

 

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

Comment: 

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

Subscribe: 

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


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

OGC Requests: 

AAtS Standards Harmonization Guidance Initiative

Status: 
Please note:  This call is now closed.

The community workshop has been re-scheduled to December 17-18 in Washington DC. Contact nalameh [at] opengeospatial.org (Nadine Alameh) if you're interested in participating.

Closing Date: 
Tue, 10/22/2013 - 04:00
Description: 

The Open Geospatial Consortium (OGC) has issued a Request for Information (RFI) to engage the aviation community in identifying standards efforts relevant to the provision of aircraft connectivity to the FAA’s System Wide Information Management (SWIM) infrastructure.

RFI Information:

  • Responses are due by 5 pm EST on 22 October 2013. 
  • A public Q&A webinar was held 1 October 2013 to provide the community with more information on the context and objectives behind this RFI. Documentation below. 

The FAA’s Aircraft Access to SWIM (AAtS) initiative is in a preliminary stage of requirements development and standards identification. Its goal is to establish a common operating environment between the flight deck, air traffic management and Airline Operational Control/Flight Operational Control (AOC/FOC) for collaborative strategic decision-making. Distribution of the operational information needed to support the safe movement of aircraft during all phases of flight in the National Airspace System (NAS) will increase capacity and efficiency and result in more timely departures and arrivals.  

There are a number of aviation standards in development, concurrently and independently, by a variety of industry groups that are also pursuing the development of requirements and standards to leverage ground-based aviation related information and data networking technology to support aircraft operations. The need to understand the scope, applicability and relationship between these efforts is both critical and timely.

Staff and members of all such industry groups are encouraged to respond to this RFI and to participate and contribute information on:

  • Technologies, standards and general trends relevant to AAtS
  • Practical recommendations on harmonization opportunities and challenges
  • Insights on how to best craft an interim path for the community and to develop a technical architecture that is forward thinking and can accommodate this emerging and evolving environment.
  • Global harmonization considerations 

Responses provided will guide the discussion at a community workshop, scheduled for 17-18 December 2013 in Washington DC, and will be considered in the development of a report that will form the basis for harmonization guidance and recommendations. 

Downloads: 

References:

Community Workshop: 

    • The community workshop, originally scheduled for Nov 5-6, has been rescheduled to Dec 17-18, 2013. Email nalameh [at] opengeospatial.org if you're interested in attending. 
    • All organization representatives interested in participating in the workshop are strongly encouraged to submit a concise response to the RFI, in order to help us organize the workshop efficiently and incorporate everybody's interests.

     

    Further Information:

    Please send an email to techdesk [at] opengeospatial.org if you have questions or need further information.

    Webinar:

    Links to the webinar material:

    Clarifications: 

      Download the Clarifications.

        OGC Requests: 

        Canadian Geospatial Data Infrastructure Interoperability Pilot (CGDI IP): Request For Quotation And Call For Participation

        Status: 
        Please note: The submission period for this request is closed. Clarifications have been issued.
        Description: 

        The Open Geospatial Consortium (OGC) is releasing a Request For Quotation and Call for Participation (hereafter referred to as RFQ/CFP) to solicit your proposal in response to a refined set of requirements for the CGDI Interoperability Pilot. This request is issued as an RFQ/CFP for two reasons. The first reason is that GeoConnections as sponsor is providing cost-sharing funds to offset expenses uniquely associated with the initiative. The second reason is that GeoConnections and OGC intend to involve as many participants in the initiative as possible and thus are soliciting contributory proposals that will enhance and/or make use of the initiative outcomes.

        Candidate Submission: Tue, 2007-04-10 12:00
        Close request period: Wed, 2007-05-02 23:59

        CGDI Interoperability Pilot Overview

         

        Clarifications have been issued. updated: 2007-04-27 10:25:24

         

        Background

        One of the tenets of the CGDI is the widespread dissemination of data which is at the same time managed at or near its source. Late in 2005, GeoConnections commissioned AMEC of Oakville, Ontario to investigate the use of technology based on the Open Geospatial Consortium's Web Feature Service (WFS) standard to better meet this objective. Recommendations made in the ensuing AMEC 2006 report, "Web Feature Services, Considerations for CGDI Government Partners" included taking primary steps to properly adopt and effectively use WFS within the CGDI.

        In spring of 2006 some CCOG members approached GeoConnections about enhancing their current services in order to provide framework data to GeoBase within a distributed computing environment. As a follow-up to the AMEC report and CCOG requests, GeoConnections then invited CCOG and IACG members to participate in a pilot project to assess the opportunities afforded by WFS technology to improve the management and dissemination of CGDI data.

        Objectives and Benefits

        The renewed GeoConnections program is primarily focused on both enhancing and applying the CGDI. This opportunity for working in collaboration with the provincial partners will test better mechanisms for the distribution and updating of framework data, providing users with access to the most current and authoritative data, avoiding version disparities, and minimizing duplication.

        Provincial partners have communicated interest in establishing WFS as a standard for providing wide access to data from distributed locations closest to their source. As source data providers for GeoBase framework data, provincial stakeholders will receive assistance with the implementation of onsite WFS components both in a technical and business sense. Assistance will be made available in the form of financial contributions for labour, software, and data publishing. This will allow providers to maintain control over the data they own while contributing at the same time to a national view of that data. Project results will aid CCOG members in planning the future production implementation of a distributed architecture for GeoBase data management and distribution.

        Data users require authoritative geospatial information, accessible directly from as close as possible to its source, in order to make timely and effective decisions. Evolving the GeoBase portal to operate in a more distributed fashion and making maintenance transactions more efficient will help to meet those user requirements. Such GeoBase improvements will be realized through the development of partnerships, data standards and encouragement of sharing. Working with data providers to improve the maintenance of GeoBase framework data is a particular priority for GeoConnections.

        Private sector technology providers will be brought into the project through a competitive process. They will assist the project partners in the deployment of the WFS technology.

        Scope

        This project proposed by GeoConnections in conjunction with CCOG members will focus on three vector-based data themes:

        • Geographic Name;
        • National Road Network;
        • Administrative Boundaries;

        The functional scope of this project includes investigations in the following areas:

        • Access by users to closest-to-source data
        • Transactional updates exchanged between data suppliers and GeoBase
        • Use of a distributed services architecture to support performant end-user online applications

        The project will include participants from provincial and federal agencies and from the private sector. Agencies will participate at different levels, some will work with private sector partners while others will use their existing infrastructures to provide access to manage and disseminate data. The information gained during the execution of this project will benefit all project participants as well as the broader CGDI community.

        Schedule

        Discussions with potential project partners for this project were initiated in the second half of 2006. A contract with Open Geospatial Consortium, Herndon, Va., to provide technical management and architecture support was initiated in January 2007. Refinement of the requirements and the Project Concept document is completed in March 2007 and the competition to select industrial partners will be completed by May 2006. The technology deployments will be complete by October 2007 and this will be followed by a 6 month pre-operational phase.

         

        Clarifications have been issued.

         

        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.
        OGC Requests: 

        Request for Comments on Earth Observation Satellite Tasking Extension for OGC® Sensor Planning Service (SPS)

        Status: 
        Please note: This Request is scheduled to close on 16 September, 2010.
        Description: 

        The Open Geospatial Consortium, Inc. (OGC®) members are seeking comments on the "Earth Observation Satellite Tasking Extension for OGC® Sensor Planning Service (SPS)." The SPS configuration proposed in this profile supports the programming of Earth Observation (EO) sensor systems. The candidate standard describes a single SPS configuration that can be supported by many satellite data providers who have existing facilities for managing sensor system programming requests.

        This SPS standard defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor, where the sensor may be any type of sensor with a digital interface. The SPS and EO-SPS standards are part of the OGC Sensor Web Enablement (SWE) (http://www.opengeospatial.org/ogc/markets-technologies/swe) suite of standards. SWE standards enable developers to describe, discover, task, and access any Internet or Web accessible sensor, transducer and sensor data repository.

        The candidate OGC® Sensor Planning Service Application Profile for Earth Observation Sensors and information on submitting comments on this document are available below.

        The public comment period closes on September 16, 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: 

        Pages