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:

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.

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 [dot] org (techdesk [at] opengeospatial [dot] org) until
15 December 2010.
After this date, no further questions or clarifications will be
posted. The
Clarifications Document is here:

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.

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 [dot] opengeospatial [dot] 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:

Please note: This Request is scheduled to close on 18 October 2010 at 9:00 PM EDT.

Description:

The Open Geospatial Consortium (OGC) has issued a Request for Quotations/Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the Special Activity Airspace (SAA) Dissemination Pilot, sponsored by the US Federal Aviation Administration (FAA).

The RFQ/CFP is below.
Responses are due by October 18, 2010. A bidders’ teleconference
will be held on October 4, 2010. The Point of Contact for the SAA
SWIM Pilot is Nadine Alameh nalameh [at] opengeospatial [dot] org.

The FAA SAA Dissemination Pilot will extend the SAA SWIM Services to enable the dissemination of SAA information (including updates and schedule changes) to National Airspace System (NAS) stakeholders and other external users via services that implement OGC Web Services (OWS) standards.

In support of the Next Generation Air Transportation System (NextGen), the FAA SWIM program seeks to achieve systems interoperability and information management for diverse Air Traffic Management (ATM) systems using Service-Oriented Architectures (SOA). The FAA SWIM capabilities include supporting the exchange of SAA information between operational ATM systems. SAAs include Special Use Airspaces (SUA) - regions of airspace designated for use by the military ensuring no other traffic uses that airspace during scheduled times.

The FAA SAA DisseminationPilot shall build on SAA SWIM Services leveraging the OGC Web Feature Service (WFS), the OGC Feature Portrayal Service (FPS), the (draft) Event Service and the Aeronautical Information Exchange Model (AIXM),
Support the filtering, access and portrayal of SAA information as well as the notification to subscribed users of SAA updates and schedule changes,and support the evolution towards end-to-end automated information flow from the US Department of Defense (DoD) - originators of SAA activation requests - to airlines and other NAS stakeholders.

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.

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 [dot] 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:

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.

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 [dot] 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:

The Open Geospatial
Consortium, Inc. (OGC®) is seeking public comment on a Geography Markup
Language (GML) XML encoding for describing the characteristics of a moving
object, such as a GPS enabled car. This
candidate standard provides a way of describing in simple terms the
motion of an object, such as a car driving through city streets or a person
walking in a park.

This candidate
standard fills a need for “lightweight” packets of tracking information, such
as direction and velocity, that can be communicated between diverse platforms
and applications supporting mobile location-aware devices. The GML encoding
used in this candidate standard is
compatible with a wide range of other standard encodings used in other
communities, such as emergency services.

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 [dot] 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:

The Open Geospatial
Consortium, Inc. (OGC®) Members are seeking comments on the “Observations and Measurements – XML
Implementation” candidate standard. This candidate standard specifies an
XML encoding for the Observations and Measurements conceptual model.

The Observations and
Measurements (O&M) conceptual model, a joint OGC and ISO standard, provides the theoretical basis for an abstract
model encoding for observations and provides support for common sampling
strategies. O&M also provides a general framework for systems that deal in
technical measurements in science and engineering.

The candidate OMXML
standard and other standards that have resulted from the OGC's Sensor Web
Enablement (SWE) effort (http://www.opengeospatial.org/ogc/markets-technologies/swe)
enable developers to make all types of sensors, transducers and sensor data
repositories discoverable, accessible and useable via the Web.

The candidate OGC Observations and Measurements – XML
Implementation Encoding Standard and information on submitting comments
on this document are available at http://www.opengeospatial.org/standards/requests/68. The public comment period closes on August 7th, 2010.

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 [dot] 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:

The Open Geospatial Consortium (OGC®) has issued a Request for Information (RFI) to solicit industry input into the second phase of a Fusion Standards Study. Phase 2 of the study focuses on Decision Fusion. Input from the RFI will influence planning for the OGC Web Services, Phase 8 (OWS-8) Testbed. OGC also seeks to establish alliances with other Standards Development Organizations (SDOs) having standards work relevant to fusion.

Decision Fusion, as described in the RFI, provides analysts an environment of interoperable services for situation assessment, impact assessment and decision support, based on information from multiple sensors and databases, e.g., multi-INT sources. The study includes recent advances such as social networking for decision fusion. Though the focus of the study is on military intelligence (“INT”), decision fusion is equally relevant to business intelligence, urban planning, and many other domains.

This RFI is based on requirements and contributions from OGC Member organizations – in particular the National Geospatial-intelligence Agency (NGA) – and industry recommendations from Phase 1 of the Fusion Standards Study.

The RFI contains a review of requirements and existing standards for decision fusion in several domains. Responses to the RFI will be reviewed during a workshop in July 2010.

Responses to the RFI are requested by June 11, 2010 [extended to 25 June]. The RFI includes instructions for how organizations can respond. Please contact George Percivall at gpercivall [at] opengeospatial [dot] org with any questions.

OGC testbeds, pilot projects and interoperability experiments are part of OGC's Interoperability Program, a global, hands-on 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.

The GeoAPI standard provides a set of Java language interfaces based on the ISO 19100 series of geospatial abstract models for metadata and feature geometry as well as two OGC Abstract Specifications for metadata and coordinate reference systems. In addition to producing this set of Java language interfaces, the OGC GeoAPI 3.0 Standards Working Group is producing a test suite through which developers implementing the Java interfaces can test their implementations.

The GeoAPI project emerges from the earlier OGC Geographic Objects effort and is the result of the collaboration of participants from various institutions and software communities. The GeoAPI project's goal is to provide a set of interfaces in the Java language to help software projects produce high quality geospatial software. This work is not expected to cover all OGC standards.

The candidate OGC GeoAPI 3.0 Interface Standard and information on submitting comments on this document are available below. The public comment period closes on 1 May 2010.

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 [dot] 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:

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.

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 [dot] 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: