1. Global Earth Observation System of Systems (GEOSS) Architecture Implementation Pilot (AIP) Air Quality and Health Working Group Stefan Falke, Rudy Husar, Frank Lindsay, David McCabe

2. AQ&H WG Participants Catalog/ Metadata Data Access Sensors/ Models WorkflowClientsScenario EPA ESIP AQ Cluster GIOVANNI GMU NOAA NGDC Northrop Grumman VIEWS WUStL

3. Air Quality & Health Scenario Scenario Overview The AQ Scenario envisions multiple types of AQ observations… satellite observations of AQ and meteorology in-situ, ambient observations models of meteorology and chemical transport other: emissions data, fire observations, LIDAR, etc. …being discovered and accessed via GEOSS and used to inform diverse decision-makers: Air Quality Managers, Policy-Makers, and the Public. Use Cases describe a Wildfire/Smoke event Scenario community-developed ; AIP participation diverse (next slide) Challenges Persistent, standardized AQ data network Interface to GCI: Community Catalog, Portal Selecting a scenario which can integrate the offerings using GCI- compatible Service Oriented Architecture

4. What few things must be the same so that everything else can be different? Data Access Services – OGC WCS/WMS Discovery Metadata – OGC CSW and ISO 19115/ISO 19119 Together this allows users to find and access data

5. Queryable Properties for Dataset Discovery: CSW and Current GEO Portals (1) Based on ISO 19115 Profile for Datasets (2) Compusult had additional queryable fields for shape file, harvest date, SBA and general keywords Dataset Fields Core CS-W Fields Desired CSW Query Fields 1 Current Geo Portal Queryable Fields GetCapabilities Doc Automatic metadata extraction from OGC Capabilities Docs.

6. Community Catalog: How Do We Get There? AQ Community Catalog AQ Community Portal CS-W WMSWCSWFSW*S Capability GEOSS App Server Community Data Server Community App CS-W, W*S

7. Clearinghouse and Common Infrastructure GEOSS Registries Services Components Standards Requirements

8. AIP Transverse Use Cases AIP is designed to test the GEOSS architecture through the Scenarios use of Use Cases

9. Community Portal

10. Scenario Overview The air quality scenario describes how the air quality community will use an interoperable, service-oriented system-of-systems which makes available and adds value to a wide variety of Earth observations, including –satellite observations of air quality and meteorological –in-situ observations of ambient conditions, primarily surface measurements of concentrations, visibility, etc. –models of meteorology and chemical transport models –emissions data, fire observations (i.e. from satellites), LIDAR, and other relevant observations. An important theme is that, in general, none of these data sources are adequate for decision support by themselves. The scenario envisions that service-oriented software and data components and services, found and accessed through GEOSS, will enable analysts to fuse models and disparate observations to arrive at improved estimates of current air quality conditions, forecasts, and historical trends. These value-added, synthesized Earth observations in turn improve decision support.

11. Wildfire and Smoke Scenario Scenario is available as a shared Google Docshared Google Doc Smoke from wildfires impacts air quality conditions both near fires and at locations hundreds of miles away, through smoke transport. Air quality managers, public health officials, and the public rely on information about wildfires, smoke, and air pollution concentrations in order to make decisions during the event to protect the safety and health of the public. After the event, AQ analysts use synthesized earth observations to improve the characterization of smoke events. Their analyses support decision making for air quality management, such as the analyses of exceptional events and long-range pollution transport mentioned above. The goal of this scenario is to improve the sharing and usability of Earth observation data relevant to wildfire smoke to support air quality management and public health decision making.

12. AQ Community Need to Update this Figure

13. DataSpaces and Catalog