77
Steven Ramage Executive Director Open Geospatial Consortium

Spatial@gov conference 2011 steven ramage

Embed Size (px)

Citation preview

Page 1: Spatial@gov conference 2011 steven ramage

Steven Ramage

Executive Director

Open Geospatial Consortium

Page 2: Spatial@gov conference 2011 steven ramage

OGC and

Communities of Interest

Page 3: Spatial@gov conference 2011 steven ramage

Or:

OGC and OGC Web Services

Phase 8 (OWS-8) and

OGC’s role in the Global Earth

Observation System of Systems

(GEOSS)!

Page 4: Spatial@gov conference 2011 steven ramage

© 2011 Open Geospatial Consortium

4

Page 5: Spatial@gov conference 2011 steven ramage

OGC StandardsOGC Standards

Technical documents that detail interfaces or

encodings. Software developers use these

documents to build open interfaces and encodings

into their products and services.

http://www.opengeospatial.org/standards

These standards are the main "products" of the

OGC and have been developed by members to

address specific interoperability challenges.

© 2011 Open Geospatial Consortium

Page 6: Spatial@gov conference 2011 steven ramage

“We can't share maps on the Web.”

”We can't deliver data to different systems.”

"We don't have a common language to speak

about our geospatial data or our services.”

"We can't find and pull together data

from our automated sensors.”

“We have security issues relating to

geospatial data exchange.”

© 2011 Open Geospatial Consortium

Interoperability: information integrationInteroperability: information integration

Page 7: Spatial@gov conference 2011 steven ramage

Open

standards

Page 8: Spatial@gov conference 2011 steven ramage

Freely and publicly available

Non discriminatory

No license fees

Agreed through formal consensus

Vendor neutral

Data neutral.

Open standards does not mean open source.

Paper on Open Source and Open Standards:http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards

© 2011 Open Geospatial Consortium

OGC open standardsOGC open standards

Page 9: Spatial@gov conference 2011 steven ramage

White papers

Business intelligence

Cloud computing

Open source

Rights management

Page 10: Spatial@gov conference 2011 steven ramage

Across multiple domains

plume forecasting for

emergency responseplume forecasting for

emergency response riverine flood

forecastingriverine flood

forecastingwinter highways

maintenance

winter highways

maintenance

severe weather

warning servicesevere weather

warning service

landfallinghurricane

landfallinghurricane

wildfirewildfire

sustained polar

science campaign

sustained polar

science campaign

climate assessmentclimate assessment

future aviationfuture aviationcurrent aviationcurrent aviation

© 2011 Open Geospatial Consortium

Global challengesGlobal challenges

Page 11: Spatial@gov conference 2011 steven ramage

riverine flood

forecastingriverine flood

forecasting

• UC11: Riverine Flood Forecasting using Meteorological

Ensemble Forecasts

• Few people are interested in weather itself, it’s the impacts

of weather that are the concern

• How do we integrate weather and climate information into the

hydrology domain?

• Potential for cross-domain engagement with OGC Met Ocean

and Hydrology Domain Working Groups

© 2011 Open Geospatial Consortium

Slides courtesy of

Jeremy Tandy,

UK Met Office

Cross domain use caseCross domain use case

Page 12: Spatial@gov conference 2011 steven ramage

SYNTACTIC

SEMANTIC

Machine to Machine

Human to Human

Know Learn

Knowledge interoperabilityKnowledge interoperability

Kindly offered by Mark McInerneyAssistant Director, Defence Spatial Standards Office, DIGO, Australia

© 2011 Open Geospatial Consortium

Page 13: Spatial@gov conference 2011 steven ramage

An Observation PostA Vertical Obstruction

A Navigation Beacon

What is this?

Shared understanding Shared understanding

Kindly offered by Mark McInerneyAssistant Director, Defence Spatial Standards Office, DIGO, Australia

© 2011 Open Geospatial Consortium

Page 14: Spatial@gov conference 2011 steven ramage

33 Standards

(Web services through to

telecommunications)

Page 15: Spatial@gov conference 2011 steven ramage

54 Working Groups

(Domain Working Groups and

Standards Working Groups)

Page 16: Spatial@gov conference 2011 steven ramage

Making location count.

© 2011 Open Geospatial Consortium

Page 17: Spatial@gov conference 2011 steven ramage

172 Compliant Products

http://www.opengeospatial.org/res

ource/products/compliant

Page 18: Spatial@gov conference 2011 steven ramage

440 OGC Members

(Government [$200-500 option],

industry, academia and

research)

http://www.opengeospatial.org/og

c/join/levels

Page 19: Spatial@gov conference 2011 steven ramage

667 Compliant and

Implementing Products

http://www.opengeospatial.org/res

ource/products/complete

Page 20: Spatial@gov conference 2011 steven ramage

Spatial Law

and Policy Committee

Business Value Committeehttp://www.opengeospatial.org/pro

jects/groups/businessvalue

Page 21: Spatial@gov conference 2011 steven ramage

OGC at a glanceOGC at a glance

© 2011 Open Geospatial Consortium

Page 22: Spatial@gov conference 2011 steven ramage

Global perspectiveGlobal perspective

© 2011 Open Geospatial Consortium

Page 23: Spatial@gov conference 2011 steven ramage

OGC program structureOGC program structure

Interoperability Program – prototyping and testing program with proven ROI. Designed to accelerate interface development and validation, and bring interoperability to the market.

Standards Program – manage consensus

processes similar to other industry consortia

(W3C, IETF, OMG and others). Revise and

maintain open geospatial and location standards.

Marketing and Communications

Program – raise awareness of standards

availability, adoption and business value. Work

with OGC members and alliance partners.

Rapid Interface

Development

Standards

Setting

Market

Adoption

© 2011 Open Geospatial Consortium

Page 24: Spatial@gov conference 2011 steven ramage

OGC Iterative DevelopmentOGC Iterative DevelopmentHowHow it worksit works

Interoperability Program

Standards Program

Marketing Program

Draft

Specifications

Adopted

Specifications

Gaps and

Enhancements

SCOTS*

Implementations

Prototype

Implementations

Requirements

*Standards-based Commercial Off The Shelf

Requirements

© 2011 Open Geospatial Consortium

Page 25: Spatial@gov conference 2011 steven ramage

OGC OGC TestbedTestbed ApproachApproach

*RFQ/CFP = Request for Quotation / Call for Participation ExecutionExecution

Task DTask D

KickKick--offoff

PreparationPreparation

Task CTask C

RFQ/CFP*RFQ/CFP*

DevelopmentDevelopment

Task BTask B

ConceptConcept

DevelopmentDevelopment

Task ATask A OGC staff manages process

with policies and procedures

proven to produce results.

Over 30 initiatives successfully completed. OGC standards advanced through this process.

© 2011 Open Geospatial Consortium

Page 26: Spatial@gov conference 2011 steven ramage

OWSOWS--8 Sponsors8 Sponsors

• US National Geospatial Intelligence Agency (NGA)

• US Geological Survey (USGS)

• US Army Geospatial Center (AGC)

• US Federal Aviation Administration (FAA)

• Eurocontrol

• US National Aeronautics & Space Administration (NASA)

• European Space Agency (ESA)

• UK Defence Science & Technology Laboratory (DSTL)

• Lockheed Martin Corporation (also providing thread architect)

© 2011 Open Geospatial Consortium

Page 27: Spatial@gov conference 2011 steven ramage

OWSOWS--8 Participants 8 Participants

• 52North

• Atmosphere

• Atos Origin

• Carbon Project

• Carmenta

• Cassidian

• Compusult

• comsoft

• con terra

• CubeWerx

• Envitia

• Esri

• Frequentis

• Galdos

• GIS.FCU

• GMU

• IDS

• iGSI

• interactive instruments

• Jacobs Univ-

EOX-rasdaman

• La Trobe Univ

• LISAsoft

• Luciad

• NGIS (in-kind)

• OpenGeo

• PYXIS

• Snowflake

• TU-München

• Uni Münster-IfGI

• Uni Bundeswehr

• Wuhan Univ (in-kind)

© 2011 Open Geospatial Consortium

Page 28: Spatial@gov conference 2011 steven ramage

OWSOWS--8 threads & 8 threads & subthreadssubthreads

Thread Architects:

Observation Fusion – Raj Singh

Geosync – Michy Maynard

CCI – Luis Bermudez

Aviation – Nadine Alameh

© 2011 Open Geospatial Consortium

Page 29: Spatial@gov conference 2011 steven ramage

OGC Interoperability Team recommended to sponsors that content of

OWS-8 initiative be organized around the following threads:

• Observation Fusion

– WCS 2.0 Earth Observation Application Profile, WCPS, Compliance Test Scripts

– Detection, tracking, and bookmarking of moving objects in video, implemented using

SWE and other OGC encodings and interfaces.

• Geosynchronization (Gsync)

– 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).

OWSOWS--8 threads & 8 threads & subthreadssubthreads

© 2011 Open Geospatial Consortium

Page 30: Spatial@gov conference 2011 steven ramage

• Cross-Community Interoperability (CCI)

– Advancement of semantic mediation approaches to query and use data based on different

heterogeneous data models, which are available via OGC WFS.

– Advancement of the use of style registries and styling services.

– Advancement of the use of KML.

– Advancement of the use of UML/OCL for Schema Automation on Domain Models.

• Aviation AIXM:

– Maturing the delivery, filtering and update of AIXM 5.1 using WFS-T/FE 2.0; continuing the

development of reusable tools, benchmarking of compression techniques for enhanced

performance, advancing styling and portrayal support, and validating the emerging metadata

and GML profiles.

– Event Notification Architecture: including Digital NOTAM Events.

– WXXM and weather information: using coverages for encoding representative weather forecast

and radar datasets, supporting on-demand Coordinate Reference System (CRS)

specifications/transformations, exploring alternative distributed architectures for managing Units of

Measure (UoM), demonstrating the applications of probabilistic Terminal Aerodrome Forecasts

(TAF) decision making applications, and reviewing/validating the WXXM schemas.

OWSOWS--8 threads & 8 threads & subthreadssubthreads

© 2011 Open Geospatial Consortium

Page 31: Spatial@gov conference 2011 steven ramage

OWSOWS--8 Aviation scenarios8 Aviation scenarios

• Dispatch and Planning (Continued from OWS-7)

– Testing new weather concepts

– Using real-time weather to increase situational awareness

• Validation of AIXM Authoritative Data Source Architecture

– Update of AIXM features via WFS-T

– Basic user authentication (identity and role);

– Basic access control

– Validation of data according to business rules

• Digital NOTAM Event Spec Scenarios

– Activation/deactivation of published ATS space

– Creation of ad-hoc SAA, ATS airspace, etc

– Route portion closure or opening

– Aerodrome/Runway/Taxiway closure

• Probabilistic Weather in Decision Making

– Demonstrate potential of using probabilistic information

in weather data in decision-support applications.

© 2011 Open Geospatial Consortium

Page 32: Spatial@gov conference 2011 steven ramage

DocumentDocument deliverables: Aviationdeliverables: Aviation

Document Lead

Aviation ER (including Event Arch

& Auth Data Source Arch)

iGSI, IfGI (Event Architecture),

TUM (Auth Architecture)

AIXM 5.1 metadata & GML Profiles Galdos & Snowflake

WFS guidance for AIXM Snowflake

AIXM Performance Assessment Atos Origin

ICAO guidance for SLD Carmenta

Digital NOTAM Event Spec Report iGSI & IfGI

WXXM/Weather Findings La Trobe University & EOX-RAS

WXXM Audit Findings Galdos

AIXM 5.1 datasets for Digital

NOTAM EventsSnowflake

© 2011 Open Geospatial Consortium

Page 33: Spatial@gov conference 2011 steven ramage

Observation Fusion: Observation Fusion: CoveragesCoverages

• WCS 2.0 Earth Observation Application Profile (EO-AP) Definition and

Implementation. Build on WCS 1.0 EO-AP developed in ESA’s HMA project.

• WCS 2.0 EO-AP to include data models for:

– 2-D Coverage with latitude and longitude axes, which can represent, for example, a hyperspectral

satellite scene.

– the subset of a 2-D satellite scene (either radar or multispectral)

– a time series of co-registered 2-D satellite scenes

– Stitched Mosaic as a 2-D horizontal coverage which can refer to several co-referenced non-

overlapping Datasets;

– Dataset Series as a collection of coverages; A Dataset Series can refer to any number of co-

referenced Datasets and Stitched Mosaics.

• and supporting these data products:

– MODIS (specific products to be identified.)

– ENVISAT MERIS L3 demonstration products (http://earth.eo.esa.int/level3/)

– ENVISAT ASAR Wide Swath

– Limb-scanning instruments (e.g. Microwave Limb Sounder) typically produce vertical profiles,

– Narrow-swath instruments (e.g., CALIPSO) produce vertical cross-sections.

• and these encodings:

– GeoTIFF, netCDF / CF-netCDF, JPEG2000, HDF-EOS

Copyright © 2011 Open Geospatial Consortium

Page 34: Spatial@gov conference 2011 steven ramage

Observation Fusion: Observation Fusion: CoveragesCoverages -- 22

• Develop WCS 2.0 Extensions for band subsetting, scaling & interpolation,

EPSG CRS

• Deploy a WCPS that provides multi-coverage fusion capabilities with different,

heterogeneous raster types, for example 1-D sensor time series, 2-D

hyperspectral remote sensing data and bathymetry/elevation data, 3-D EO time

series, 4-D climate data.

• Design WCS 2.0 EO-AP to scale to large number of coverages as is typical in

the data archives of ESA and NASA.

• Develop sufficiently complex WCPS queries, taken from real-life examples, to

make them convincing to domain experts.

• WCS 2.0 EO-AP Compliance Testing. Develop Compliance Test suite for the

WCS 2.0 AP including completing the ATS and developing the ETS and

Reference Implementation.

• Processing of EO Coverages: WCPS and WPS. Develop WCPS for advanced

access to Earth Observation Coverages. Develop WPS for Earth Observation

data analysis of multiple coverages and other data.

Copyright © 2011 Open Geospatial Consortium

Page 35: Spatial@gov conference 2011 steven ramage

WCS Earth Observation AP data flowsWCS Earth Observation AP data flows

Copyright © 2011 Open Geospatial Consortium

Page 36: Spatial@gov conference 2011 steven ramage

WPS WPS –– WCPS Use CasesWCPS Use Cases

Copyright © 2011 Open Geospatial Consortium

EO Client Data (ref or value)

Data

WPS

EO Client Coverage Processing

Language (CPL) script

Data

WCS

WCPS

EO Client Coverage Processing

Language (CPL) script

Data WPS

WCPS

Page 37: Spatial@gov conference 2011 steven ramage

Feature Fusion / Portrayal Feature Fusion / Portrayal

User wants to retrieve all the dams from several data stores and portray the

dams using USGS Symbology.

– The client can invoke several OGC services, such as WMS, WFS and WCS,

to discover services, get data, convert CRS as needed, and get appropriate

Symbology for the data presented

Copyright © 2011 Open Geospatial Consortium

Cross Community Cross Community

Interoperability Interoperability

ThreadThread

Page 38: Spatial@gov conference 2011 steven ramage

Semantic Mediation at OWSSemantic Mediation at OWS--88

®© 2011 Open Geospatial Consortium

Cross Community Cross Community

Interoperability Interoperability

ThreadThread

Copyright © 2011 Open Geospatial Consortium

Page 39: Spatial@gov conference 2011 steven ramage

OGC®© 2011 Open Geospatial Consortium

Copyright © 2011 Open Geospatial Consortium

Page 40: Spatial@gov conference 2011 steven ramage

OGC®© 2011 Open Geospatial Consortium

Copyright © 2011 Open Geospatial Consortium

Page 41: Spatial@gov conference 2011 steven ramage

Semantic mediation participantsSemantic mediation participants

Engineering Report

Deliverable

Lead

1. Semantic Mediation

ER

Envitia

2. SLD Portrayal with

Registries ER

Galdos and

Compusult

3. Schema Automation

ER

interactive

instruments

4. CR’s for semantics:

WFS

Compusult.

Int-Instr

Carmenta

5. CR’s for portrayal

services, encodings

Compusult.

Int-Instr

Carmenta

Component

Deliverables

Participants

OGC Mediation Service

(OMS)

Luciad

WFS for datasets from

NGA

interactive

instr.

WFS for datasets from

USGS

CubeWerx

Clients for mediation &

portrayal: SLD, SE, KML

Compusult

CSW ebRIM for Portrayal

Registry

Carmenta

CSW ebRIM for semantic

mediation

Compusult

FPS for SE, KML Carmenta

ShapeChange

enhancements

interactive

instr.

Page 42: Spatial@gov conference 2011 steven ramage

GeoSyncGeoSync ServicesServices

Refined in OWSRefined in OWS--7: 7:

Publisher Submits

Change Request

5566

22

Geosync Service (GSS)Geosync Service (GSS)

44

11

33

OGC WFS-T OGC WFS-T OGC WFS-T

GSS notifies Publisher

whether proposed

changes were Approved

or Rejected

GSS notifies

Followers of

changes to

features (i.e.

Transactions)

GSS notifies

Reviewer

of pending

Change

proposals

Reviewer Approves

or Rejects the

proposed changes

Approved changes are

applied to features via

OGC WFS-T

Geographic

features accessible

via WFS

Publisher reads features from

a WFS managed by the GSS

and proposes changes to

those features. This may

include proposing creation of

new features.

Page 43: Spatial@gov conference 2011 steven ramage

Data / ScenarioData / Scenario

• TDS (GRLS) Data Set (NGA)

– Over Monterey California

• 4 WFS

– WFS 2.0 CubeWerx

– GIS.FCU WFS

– OpenStreetMap WFS (OpenGeo)

– CarbonProject ArcGIS WFS

• Scenario

– Earthquake in Monterey, causes an oil spill off the bay

– Units are dispatched to help the situation

– Including mobile apps

Copyright © 2011 Open Geospatial Consortium

Page 44: Spatial@gov conference 2011 steven ramage

GeosyncGeosync: Demo Scenario: Demo Scenario

Copyright © 2011 Open Geospatial Consortium

Page 45: Spatial@gov conference 2011 steven ramage

Bulk Transfer CapabilitiesBulk Transfer Capabilities

• The proposed Geodata Bulk Transfer capability consists of a

conceptual 'container' where the 'parts' (defined below) function

independently of the whole container thus allowing potential producers

and consumers to leverage only part of the interoperability standard.

The 'container' should support the ability to:

1. Define the relationships between feature types

2. Maintain integrity (container check sums)

3. Provide a compression methodology optimized for transmission and

consumption on disadvantaged clients

4. Describe the parts or feature types within the container

5. Define the metadata for the whole container as well as the parts of the

container

6. Provide for direct random access (desirable but not mandatory)

Copyright © 2011 Open Geospatial Consortium

Page 46: Spatial@gov conference 2011 steven ramage

GeosyncGeosync in OWSin OWS--8: additional considerations8: additional considerations

• Schema Initialization

– Enable creation of a new feature type in the data server through GSS

• Data Initialization: Ability to add and initialize features on server, prior to

geosynchronization

– Full Copy Data Initialization

– Partial Copy Initialization: similar to full copy data initialization except that a subset

of the source features is identified for geosynchronization (filtered on temporal, spatial

and scalar property constraints)

– No Copy Data Initialization (Point in Time Forward): geosynchronization can begin

at any point-in-time without the need to seed the target feature type with data from

the source feature type. The only requirement is that the target feature type exists or

is created using Schema Initialization. All future changes are integrated from the start

of no copy data initialization.

• Geosynchronization for Time Stamped, Time Sliced Data (WFS 2.0)

– Test spatio-temporal editing, filtering with GSS

Copyright © 2011 Open Geospatial Consortium

Page 47: Spatial@gov conference 2011 steven ramage

Observation Fusion: Motion TrackingObservation Fusion: Motion Tracking

• Implementing and reconciling NATO STANAG and NGA MISB

standards for tracking moving objects in motion imagery, using OGC

Standards. Investigate, evaluate and recommend areas of

harmonization between OGC Sensor Web Enablement, OGC GML-

based standards, and OGC Tracking and Notification Service, to

support STANAG 4607 Ground Moving Target Indication Format

(GMTIF), Edition 3; STANAG 4609, Edition 3, EG0903.0 Video Moving

Target Indicator (VMTI); and NATO Study 4676 NATO ISR Tracking

Standard (NITS).

• Document a set of architecture viewpoints showing the use of SWE and

other OGC standards to implement the TCPED-based GMTI, VMTI,

and ISR Tracking concept of operations. Document any gaps and

shortfalls found in the architecturally relevant OGC suite of standards

where implementations supporting GMTI, VMTI, and/or ISR Tracking

would fall short of defined requirements. The OWS-8 ER on this topic

could become the basis for an OGC Best Practice.

Copyright © 2011 Open Geospatial Consortium

Page 48: Spatial@gov conference 2011 steven ramage

Mobile Objects data flowsMobile Objects data flows

Copyright © 2011 Open Geospatial Consortium

Page 49: Spatial@gov conference 2011 steven ramage

Mobile Objects ArchitectureMobile Objects Architecture

Copyright © 2011 Open Geospatial Consortium

Page 50: Spatial@gov conference 2011 steven ramage

Now for something

completely different

Page 51: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

The Global Earth Observation

System of Systems (GEOSS)

Page 52: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

Our planet is a System of Systems

Page 53: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

U.S. Department of State, Washington DC

July 31, 2003

The Group on Earth Observations (GEO)

An Intergovernmental Organization with

77 Members and 56 Participating Organizations

Page 54: Spatial@gov conference 2011 steven ramage

© GEO Secretariat© GEO Secretariat slide 54

• Some 30% of our economy is directly tied to the environment

• Scientific understanding and ongoing knowledge of the Earth system

is fundamental for well-informed economic decision-making

• Sustained Earth observations are critical

• Systems interoperability and open access to data are fundamental

• A global approach to Earth observations is required

The GEOSS Imperative

Page 55: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

Any single problem

requires many data sets

Any single data set

serves many applications

Q Observation systems should be

shared across disciplines

Page 56: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

Existing observation systems

show important duplications

User requirements point

to significant observation gaps

Q Observation systems should be

coordinated and shared internationally

Page 57: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

� Coordinate and sustain observation systems

� Provide easier & more open data access

� Foster use through science, applications

and capacity building

2 to answer society’s need for information

decision making

Governments and organizations are

collaborating through GEO to –

Page 58: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

Page 59: Spatial@gov conference 2011 steven ramage

© GEO Secretariat

� Data and products at minimum time delay and minimum cost

� Free of charge or cost of reproduction for research and education

GEO Data Sharing Principles

� Full and open exchange of data Q recognizing relevant international instruments and national policies and legislation

Page 60: Spatial@gov conference 2011 steven ramage

OGC role in GEOSS

• OGC is a Participating Organization in GEO

• OGC leads the Architecture Implementation Pilot

(GEO Task AR-07-02)

• OGC is a member of GIGAS Consortium

• OGC is an lead in organization in a series of

GEOSS Workshops

• OGC is a co-lead of the GEO Standards and

Interoperability Forum (SIF)

Page 61: Spatial@gov conference 2011 steven ramage

What are the Architecture

Implementation Pilots (AIP)?

“fostering interoperability arrangements

and common practices for GEOSS”

Page 62: Spatial@gov conference 2011 steven ramage

Operational

Capability

Operational

Capability

User

Needs,

Scenarios

User

Needs,

Scenarios

Design,

Develop,

Deploy

Design,

Develop,

Deploy

ADC activities

including:

Architecture

Implementation

Pilot (AIP)Task AR-09-01b

GEOSS

Common

Infrastructure (GCI)Task AR-09-01a

support

persistent

implementation

requirements

SBA Tasks,

UIC, CBC,

STC

A process, elaboration of GEOSS Architecture

URR, Data Sharing Task Force

GCI-Coordination Team

DSP

QA4EO

LTDP

Transfer to

operations

2011-2015

SIF outreach

Page 63: Spatial@gov conference 2011 steven ramage

AIP Reusable Process for SBA Integrators

• Scenarios: end user view of the value of GEOSS

– Focused on topics of interest to a community

– Occur in a geographic Area of Interest (AOI)

– Steps in a scenario are mapped to Use Cases

Page 64: Spatial@gov conference 2011 steven ramage

GEOSS AIP Phase 4 (AIP-4)

Activity #1: Access to Priority EO Data Sources1a. Thesaurus for EO Observation Parameters

1b. "EO Priority Data Sources” list

1c. Getting EO Data Online

1d. Tutorials on data access

Activity #2: Clients and Mediated Access Enablers2a. Coordination with GCI

2b. Coordination of Enabler Components

2c. Integration and Usability Testing of Enablers Components

Page 65: Spatial@gov conference 2011 steven ramage

AIP-3 Summary and Recommendations

• Improved access to variety of observations

– Remote sensing, in-situ sensing, & models

• Increased capabilities through web services

– Access, Processing, Data, Semantics

• Repeatable results through engineering process

– Scenarios, Services, Interoperability Arrangements

• Improved decision-making

– Coordinated SBA and technical developments

Page 66: Spatial@gov conference 2011 steven ramage

AIP-4 Activity #1:

Access to Priority EO Data Sources

• Access to Priority EO Data Sources as either:

– Long Term Archive or

– Data Broker

• Data access assistance:

– Tutorials, server toolkits, expert guidance

– Coordination with SIF

• Services to test priority access services and enabler

components

– Data access through services

• WCS, WFS, WMS, SOS, OPenDAP, WPS

Page 67: Spatial@gov conference 2011 steven ramage

Enabler Components

• Semantic-enabled mediation Components

– EuroGEOSS Data Access Broker

– GENESI-DEC Search Service

– PML NETMAR

• Web Processing Services Components

– Population estimation service – CIESIN

– Ecological forecasting – EuroGEOSS – UncertWeb

– Spatio-temporal processing services – Graphitech

– Coverage Processing – Rasdaman and Vightel

– Solar radiation parameters extraction – Mines Paris Tech

– Satellite, in-situ and model data processing – PML

– Heterogeneous data for common grids – EuroGEOSS Access

Broker

Page 68: Spatial@gov conference 2011 steven ramage

For more information

• GEO

– earthobservations.org

• GEO Architecture Implementation Pilot

– www.ogcnetwork.net/AIpilot

• GEOSS registries and SIF

– geossregistries.info

Page 69: Spatial@gov conference 2011 steven ramage

Planning for AIP-5

• Scenario based development based on requests

– Energy, Health, Water

• Develop Information Schemas for GEOSS

• Draft Schedule

– Develop CFP: January to March 2012

– Kickoff Workshop: May or June 2012

– Development: 4 months

– Complete in 2012

• Deliverables

– Components, ERs, Deployed scenarios.

Page 70: Spatial@gov conference 2011 steven ramage

Finally

Page 71: Spatial@gov conference 2011 steven ramage

OASIS/IETF/

W3C

Infrastructure:

WSDL, UDDI,

SOAP, XML, REST

ISO

Domains: object/

abstract models,

content,

vocabulary

OGC

Software Interfaces:

instantiate domain and

de jure standards into

Infrastructure

De F

acto

De J

ure

Domain Infrastructure

OGC and global standardsOGC and global standards

© 2011 Open Geospatial Consortium

Page 72: Spatial@gov conference 2011 steven ramage

– Primary alliances for standards coordination

• Commission Europeen des Normes (CEN)

• Digital Geospatial Information Working Group (DGIWG)

• Internet Engineering Task Force (IETF)

• Organization for the Advancement of Structured Information

Standards (OASIS)

• International Organization for Standards (ISO)

• Open Mobile Alliance (OMA)

• National Institute of Building Sciences (NIBS)

• National Emergency Number Association (NENA)

• Network Centric Operations Industry Consortium (NCOIC)

• IEEE Technical Committee 9 (Sensor Web)

– Secondary alliances

• Global Spatial Data Infrastructure Association (GSDI)

• Web3D

• World Wide Web Consortium (W3C)

• Integrated Justice Information Systems (IJIS) Institute

• International Alliance for Interoperability (IAI)

• IEEE GRSS and ICEO

• Taxonomic Data Working Group (TDWG)

OGC and Alliance PartnersOGC and Alliance Partners

© 2011 Open Geospatial Consortium

Page 73: Spatial@gov conference 2011 steven ramage

Organize OGC standards requirements, priorities and

outreach activities consistent with language, culture,

policy, and political environment.

– Regional

• Asia Forum

• Europe Forum

• Iberian and Latin American Forum

– National

• France Forum

• India Forum

• Korea Forum

OGC Forum activitiesOGC Forum activities

© 2011 Open Geospatial Consortium

Page 74: Spatial@gov conference 2011 steven ramage

Requests for Information

Requests for Comment

Call For Participation

Change Requests

OGC Public Forum

OGC Network

Public inputPublic input

© 2011 Open Geospatial Consortium

Page 75: Spatial@gov conference 2011 steven ramage

To take the survey, if you are a technology user, visit

http://uncc.surveyshare.com/s/AQAIJDC.

To take the survey, if you are a technology provider, visit

http://uncc.surveyshare.com/s/AQAIZBC.

The survey ends 18th December 2011. Prizes will be

awarded at random to three individuals who complete the

survey. Each survey takes about 15 minutes to complete.

© 2011 Open Geospatial Consortium

OGC survey on business valueOGC survey on business value

Page 76: Spatial@gov conference 2011 steven ramage

®

®

Mary McRae, OASIS

Standards are

like parachutes:

they work best

when they're

open.

Page 77: Spatial@gov conference 2011 steven ramage

QUESTIONS

[email protected]