Air Quality Data Systems and the GEOSS Architecture Rudolf B. Husar, Washington University Given at the OGC Technical Committee Meeting St. Louis, MO, March 24, 2006 Expanding on Presentations by Doug Nebert, March 2008, ESIP Web Services. George Percivall, February 2008, ADC-6-Report

GEOSS GEOSS Architecture By 2015, GEOSS will be a distributed system of systems, building step-by-step on current cooperation efforts among existing observing and processing systems within their mandates, while encouraging and accommodating new components. GEOSS Architecture Describes how components fit together for providing data and information that will be better …than the individual components or systems of which it is composed. Links together strategies and systems to facilitate Earth observations in a comprehensive, coordinated, and sustained manner.

Core GEOSS Architecture From Percivall, Feb 2008 accesses GEO Web Portal and other Clients searches User searches invokes GEOSS Clearinghouse list of catalogues GEOSS Component, Service registry references accesses This explains the relationship of registries and Clearinghouse. From George Percivall’s slides, Feb. 2008 Catalogues Services contribute to register Standards, Special Arrangements Registries Offerors reference

GEOSS Architecture for the Air Quality Community (March 2008) Service Offerors, Users find, select GEOSS Clearinghouse extracts Catalog User Community AQ Portal bind, invoke Catalog list Searches, harvests Services GEOSS Comp. Registry Community AQ Catalog GEOSS Architecture for Air Quality data system. Value-adding chain in Decision-Support System. registers publish provides references links to Standards; SIF Registry Service Offeror Adopted from Percivall, Feb 2008 by R. Husar, March 2008

GEOSS Architecture for the Air Quality Community (March 2008) Service Offerors, Users GEOSS Clearinghouse extracts find Catalog User composes Service Workflow visualizes Data Analyst Community AQ Portal Reports to invokes Catalog list Searches, harvests Policy Analyst GEOSS Comp. Registry Community AQ Catalog Services GEOSS Architecture for Air Quality data system. Value-adding chain in Decision-Support System. registers Informs provides references publishes Decision Maker Standards; SIF Registry Service Offeror Adopted from Percivall, Feb 2008 by R. Husar, March 2008

GEOSS Architecture for the Air Quality Community (March 2008) Service Offerors, Users, Community of Practice GEOSS Community GEOSS Clearinghouse extracts find Catalog User composes Service Workflow visualizes Data Analyst Community AQ Portal Reports to invokes Catalog list Searches, harvests Policy Analyst Community AQ Catalog Services GEOSS Comp. Registry Community Of Practice GEOSS Architecture for Air Quality data system. Value-adding chain in Decision-Support System. registers Informs links to references provides publishes Decision Maker Standards; SIF Registry Service Offeror Adopted from Percivall, Feb 2008 by R. Husar, March 2008

Standards, Requirements IOC Architecture – Engineering Viewpoint (Feb 2008) Adopted from Percivall, Feb 2008 by R. Husar Client Tier GEO Web Site GEO Web Portal GEOSS Community Portals Client Apps Information Services Tier GEOSS Registries GEOSS Clearinghouse GEOSS Community Catalogues Data Services Components, Services Process, Portray Standards, Requirements Other, Workflow GEO Core Services Communal Services Access Tier Model Access Services Data Access Services Sensor Access Services Other Access Services

AI Pilot Development Approach From Percivall, Feb 2008 Participation AR-07-02 Architecture Implementation Pilot Evolutionary Development Process Concept Development Participation Call for Participation Participation Kick-off Workshop Architecture Documentation Updates for each step Baseline Participation Development Activities Participation Persistent Operations (AR-07-01) Operational Baseline for next evolutionary spiral

AIP Process improvement ideas Adopted from Percivall, Feb 2008 by R. Husar AIP Process improvement ideas Comments on AIP Process Process Improvement Air Quality CoP Approach Functionality defined by developers not users UIC/ADC collab., Workshops; Operational SBA functionality Contact with UIC; Toronto, Workshop; Open Invitations, ESIP, CoP wiki AIP Process is closed Make development iterative; Anyone can join at anytime Process focused on demonstrations More operational persistence; Deliver AR-07-01 Operations Expand AQ Data Netw; Seek link to AR-07-01 Too structured: milestones, deliverables Retain structure within phase; More iterative, open approach One phase at a time; Feedback, feedback