GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot Products, Sensors, Models Access Services WG WG Points of Contact:

Slides:



Advertisements
Similar presentations
GEO Task AR AIP-2 Kickoff Workshop NCAR Mesa Laboratory September 2008.
Advertisements

GEOSS AIP2 Disaster Management Scenario Services and Components Stu Frye Didier Giacobbo Ron Lowther 25 September 2008.
GEOSS AIP-2 Development Interim Design Review Workflow & Alert WG Co-chairs: Satoshi Sekiguchi, AIST, Japan Dr. Liping Di, GMU, USA Dr. Genong (Eugene)
Air Quality and Health Scenario Stefan Falke, Rudy Husar, Frank Lindsay, David McCabe.
GEOSS AIP-2 Development Interim Design Review Disaster WG Stu Frye Didier Giacobbo Alexandre Robin (as alternate) Valencia 2 December 2008.
Northrop Grumman Participation GEOSS AIP Sensor Webs & Models
GEOSS AIP-2 Development Interim Design Review Portals & Application Clients Transverse WG Nadine Alameh
GEO AIP-2 Interim Design Review Test Facility Working Group Mauro Semerano (ElsagDatamat spa) ESA December 2008.
Page 1 CSISS LCenter for Spatial Information Science and Systems 03/19/2008 GeoBrain BPELPower Workflow Engine Liping Di, Genong Yu Center.
AIP-2 Kickoff Workshop Disaster Response Agenda and Primary Participants Stuart FryeCaribbean Flood Team Ron LowtherNorthrop Grumman Didier GiacobboSpot.
AIP-2 Kickoff Workshop Energy SBA Session Ellsworth LeDrew, University of Waterloo, Canada Thierry Ranchin, Mines ParisTech, France GEOSS AIP-2 Kickoff.
Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary.
OGC Sensor Web Enablement ESIP Federation Meeting, January 2009
GEO Task AR Architecture Implementation Pilot, Phase 2 (AIP-2) Kickoff Workshop NCAR Mesa Laboratory September 2008.
George Percivall, OGC and Ingo Simonis, OGC-E
GEO Task AR AIP-2 Kickoff Workshop Closing Plenary NCAR Mesa Laboratory September 2008.
Successful Implementations for SBAs using GEOSS Interoperability Arrangements George Percivall The Open Geospatial Consortium Jay Pearlman, IEEE Nadine.
GEOSS ADC Architecture Workshop: Sensor Web Ingo Simonis iGSI
GEOSS Task AR-09-01b Architecture Implementation Pilot Phase 4 (AIP-4) Nadine Alameh, George Percivall, Ingo Simonis Open Geospatial Consortium (OGC) GEOSS.
CEOS Project & Applications Subgroup Hanoi May EO Data Portal Task Team Status Wyn Cudlip BNSC/QinetiQ Presentation to Project.
Sensor Web Enablement and GEOSS Presented by: Terence van Zyl.
1 NASA CEOP Status & Demo CEOS WGISS-25 Sanya, China February 27, 2008 Yonsook Enloe.
1 GEOSS Architecture Implementation Pilot (AIP) Phase 2 Air Quality and Health Working Group Stefan Falke, Rudy Husar, Frank Lindsay, David McCabe, Erin.
SIF Status to ADC Co-Chairs
Core Task Status, AR Doug Nebert September 21, 2008.
Standards and Interoperability Forum: Status, Issues & Plans GEO Architecture and Data Committee Kyoto, Japan 9 February 2009 Siri-Jodha Singh Khalsa.
© GEO Secretariat Virtual Constellations..new planning process which takes account of international users and their requirements from the outset of satellite.
GEOSS Common Infrastructure (GCI): status and evolution EC Side Event - GEO Plenary IX Foz do Iguacu, November 2012 Mirko Albani Earth Observation.
The GEO Work Plan * 2010 Update (GEO-VI) * New Online Management System Alexia Massacand (Work Plan Coordinator) Rik Baeyens (IT Manager)
GEOSS Common Infrastructure (GCI)
NOAA Data Center Access Activities via the GEOSS Architecture Implementation Pilot (AIP-2) Task AR Glenn K. Rutledge NOAA / NCDC Co-Chair GEOSS AIP-2.
GEO Architecture and Data Committee Task AR Architecture Implementation Pilot George Percivall Open Geospatial Consortium Task AR Point of.
Pacific Island Countries GIS/RS User Conference 2010, Suva, November 2010 Sensor Web Enablement for the Pacific Vulnerability and adaptation of coastal.
OGC Liaison Report WGISS-20 Allan Doyle, EOGEO
A Global Agriculture Drought Monitoring and Forecasting System (GADMFS) Meixia Deng and Liping Di.
Global Earth Observation System of Systems (GEOSS) Architecture Implementation Pilot (AIP) Air Quality and Health Working Group Stefan Falke, Rudy Husar,
Actions on GCI way forward. The Way Forward – presented at ExCOM29 Launch new GEOSS Portal – End of Nov. For each SBA and special Initiative, GEO Secretariat.
GEO Architecture Implementation Pilot ESIP Federation Meeting January 2009.
CEOS WGISS May 2006 NASA Support for WTF-CEOP Sept 11, 2006 Ken McDonald, NASA Yonsook Enloe, SGT Inc.
Jürgen Walther Office of the Interministerial Committee for Geo Information (IMAGI) Coordination Office GDI-DE Federal Agency for Cartography and Geodesy.
Task IN-05 GEO Work Plan Symposium 2014 IIB AIP-7 (May 1 st ) Reporting: Bart De Lathouwer (OGC)
Slide # 1 GEO Task AR Architecture Implementation Pilot George Percivall GEO ADC Meeting, 14 & 15 May 2007.
DA Sensor Web Enablement for In-Situ Observing Network Facilitation.
1 NOAA IOOS Program Data Integration Framework (DIF) Project Overview Adapted from a brief to the NOAA Data Management Committee August 6, 2008 by Jeff.
GEOSS AIP-5 Architecture Implementation Pilot, Phase 5 - Disasters Management Session- Hervé Caumont - Session Lead - OGC IP Team AIP-5 Kick-off Meeting,
GEO Architecture and Data Committee Task AR Architecture Implementation Pilot George Percivall September 2008.
Task DA Sensor Webs Enablement for In-Situ Observing Network Facilitation Dr. Jay Pearlman Presentation to ADC May 14, 2007.
WGISS Technology Subgroup Report WGISS-29 Bonn, 2010 Nataliia Kussul WGISS.
NSAU Flood Model Use in Sensor Web: Lessons Learned Sergii Skakun Space Research Institute NASU-NSAU, Ukraine CEOS WGISS-27 May 11-15, 2009 Toulouse, France.
Architecture Implementation Pilot-5 Disasters Management WG Encourage mature systems to interoperate with the GEOSS Common Infrastructure Leader Hervé.
1 Implementing QA/QC Standards for In Situ Ocean Sensors Using OGC-Sensor Web Enablement a.k.a. QARTOD to OGC a.k.a. Q2O Project Status Brief to NOAA IOOS.
Slide # 1 GEO Task AR Architecture Implementation Pilot George Percivall GEO ADC Meeting, 28 February & 1 March 2007.
Core Task Status, AR Doug Nebert September 22, 2008.
Implementing GEOSS architecture with-and-for Users George Percivall Open Geospatial Consortium Task lead AR-09-01B.
NOAA IOOS SOS Implementations in 2008 Jeff de La Beaujardière, PhD NOAA IOOS Program DIF Sr Systems Architect.
Ideas on Opening Up GEOSS Architecture and Extending AIP-5 Wim Hugo SAEON.
GEOSS Architecture Implementation Pilot, Phase 2 (AIP-2) George Percivall, Open Geospatial Consortium GEO Task AR-09-01b Task POC 2 February 2009.
GEO ADC Co-Chair meeting USGS, Reston, Dec Slide # 1 AR Interface implementations for GEOSS George Percivall
GEOSS Architecture Implementation Pilot AIP-3 Engineering Use Cases Nadine Alameh & Josh Lieberman AIP-3 kickoff Frascati, Italy March
Federation of Earth Science Information Partners EGIDA Workshop May 9-11, 2011, Bonn, Germany.
GEO Architecture and Data Committee Task AR Architecture Implementation Pilot Access Services: Products, Sensors, Models WG Access Services Co-Chairs:
Global Earth Observation System of Systems (GEOSS) Architecture Implementation Pilot (AIP) Air Quality and Health Working Group Stefan Falke, Rudy Husar,
George Percivall, Open Geospatial Consortium
GEO Architecture Implementation Pilot
GEOSS Architecture Implementation Pilot, Phase 2 (AIP-2)
George Percivall September 2008
Core Task Status, AR Doug Nebert September 22, 2008.
AIP-5 Kick-off Workshop Summary 3-4 May 2012, UNEP, Geneva
GEOSS Architecture Implementation Pilot, Phase 3 AIP-3 Initial Plans – Drought Scenario - presentation to ESIP - George Percivall, Open Geospatial Consortium.
Air Quality Data Systems and the GEOSS Architecture
Presentation transcript:

GEO Architecture and Data Committee Task AR Architecture Implementation Pilot Products, Sensors, Models Access Services WG WG Points of Contact: Terence Van Zyl, MERAKA Institute Hervé Caumont, OGC IP Team / ERDAS December 3rd, 2008

Access WG Charter The Access WG provides coordination and guidance to achieve interoperable Access Services to products, sensors and models. This relies on the AIP-2 participant's offerings (their proposed contributions to the pilot). By doing so, the Access WG contributes with other WG to enable a Global EO System of Systems, through scenarios and use cases definition.

AIP-2 Participants with a focus on Access Services

Data Product Access 23 Primary responses: CIESIN, CNES, EPA, ESA, GEO-Ukraine, ICAN, ICT4EO, IP3, ISPRA, JAXA, Mines Paris Tech, NASA World Wind, NOAA IOOS, NOAA NCDC GOSIC, NOAA NCDC NEXRAD, NOAA NCDC NIDIS, NOAA NCDC NOMADS, NOAA/NASA GOES-R and GMU CSISS, Northrop Grumman, SURA/NIMSAT/GoMOOS, Spot Image, USGS, Washington Univ St. Louis 15 Contributing responses: ACRF, Caribbean Flood Team, ERDAS, ESIP AQ Cluster, ESRI, ESRI Canada, NOAA SNAAP

Data Product Access Topics Services: WMS, WCS and WFS Encodings Formats : NetCDF/CF, KML, GML, JPEG2000, PNGs, GeoTIFF, MrSID, Geolocated JPEGs, CADRG, CIB, Shapefile EO Data: Radar, Optical, Weather, Precipitation, TRMM flash flood potential ALOS Imagery: Panchromatic, Near IR, SAR High-frequency radar in situ oceanographic data Coastal Web Atlas holdings Multistandard platform (MapServer, ArcIms Server, SDE, etc) SPIDR web services IP3 ENM Species Distribution Analysis service SoDa W*S is already a Special Argmt Broker Service to access OGC Web services, THREDDS/OpenDAP, GBIF

Sensors and Models Access 7 Primary responses: GEO-Ukraine, ICT4EO, IP3, NOAA IOOS, Northrop Grumman, Spot Image, SURA/NIMSAT/GoMOOS 5 Contributing responses: Caribbean Flood Team, Compusult, NASA World Wind, NOAA NCDC NEXRAD, Noblis

Sensors and Models Access Topics Sensor Web Enablement: SOS, SPS, SAS, SensorML, O&M EO-1, TRMM, Envisat, SRTM, MODIS, RADAR, RT weather, fire Weather, fire, flood areas and index Flood model outputs Bluesky Smoke model Model Web CALPUFF and WRF model outputs

Goal, audience, and usage of the 'Use cases' Use Cases are provided to model the interactions of a (sub)system under study with its environment (actors, being some kind of user interface or other systems) –Co-authored by systems analysts and end users –A starting point for tests design Use Cases are developed by the AIP Transverse Technology WG Scenarios are developed by the AIP Community WG Both support AI Pilot storyboards, to test & demonstrate interoperability amongst online persistent systems and services –Running a scenario over several systems –Activating systems functions as described in the use cases

Basic set of use cases / capture persistent access Accessing a product Accessing a model Accessing a sensor for observations Accessing a rendered output from a product or model Ordering a product Invoking the disaster charter for access to products Subscribing to a sensor alert Commanding a sensor

Accessing a Product Description: –Access to various web resident services including WFS, WCS, OpenDAP; encodings; CRSs Lead: –Hervé Caumont Status: –Started was agreed during WG Telecon will be posted on WG Website (this week)

Accessing a Model Description: –Access to a web resident services that fronts a model Lead –Glenn Rutledge Status –Started

Accessing rendered output from a product or model Description: –Access to a map portrayal service for products or models visualization Lead: –No lead Status –Not started

Accessing a Sensor for Observations Description: –Access to a web resident sensor fronted by a web service supporting OGC-SOS Lead –Luis Bermudez Status –Started

Subscribing to a Sensor Alert Description: –Access to a web resident sensor fronted by a web service supporting OGC-SAS for the purpose of receiving alerts Lead: –No Lead Status: –Not started

Commanding a Sensor Description: –Access to a web resident sensor fronted by a web service supporting OGC-SPS for the purpose influencing future observations Lead –Terence van Zyl Status –Started

Ordering a Product Description: –Access a product through the tasking of a specific sensor/platform Lead –No Lead Status –Proposed as additional use case

Invoking the Disaster Charter Description: –Use case to describe how in the case of a disaster to speed up the process of access to the charter Lead –No lead Status –Proposed as additional use case

Template for writing Access Use Cases

How to populate the initial Use Cases When writing, keep focus on the subsystem under study (the Web Coverage Service, the Sensor Alert subscription service…) –Give awaited inputs and provided outputs –Document for modularity Use verbs / action (server receives request for a single band geoTIFF…, server sends…) Consider the cumulated / consolidated Use Cases view, and document the right modularity and uniqueness of each Use Case

Simple example

Status General WG Tasks being completed –Arrive at a set of generic principles that underpin all persistent access –Provide through a Google form a way for outsiders to capture experience, issues, etc… relating to use cases –Arrive at a set of measures that will describe our success and the effectiveness of use cases –Do a self evaluation –Cycle through and refine Use Cases definitions

Invitation to Contribute The Process Being Followed per Use Case –Identify a use case that captures persistent access –Invite people to contribute and comment on use cases –Refine/Populate the use cases to support interoperability testing of components and services within the AI Pilot –Capture comments –Continue cycling through this process refining each iteration

Invitation to contribute

Contact Information Getting to the Access WG Web page: – –Menu entry access-services-working-groupaccess-services-working-group Subscribing to the Access WG Mailing List: – Access WG weekly telecons to discuss issues arising and new use cases that need to be addressed –Announcements through Access WG mailing list

Thank you