Ws For Aqm


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Ws For Aqm

    1. 1. Web Services for Air Quality Management <ul><li>Air Quality management requires data from many distributed sources </li></ul><ul><li>For AQ management, data need to be filtered, aggregated and fused </li></ul><ul><li>Loosely coupled web services are a promising technology </li></ul><ul><li>The http://DataFed.Net tools follow such a Service Oriented Architecture to access, process and deliver AQ-relevant information </li></ul>R. Husar, S. Falke, K. Höijärvi Washington University, St. Louis, MO, ESIP Meeting, Washington DC, January 4-6, 2005
    2. 2. Application Scenario: Smoke Impact REASoN Project: Application of NASA ESE Data and Tools to Particulate Air Quality Management ( PPT/PDF ) <ul><li>Scenario: </li></ul><ul><li>Smoke form Mexico causes record PM over the Eastern US. </li></ul><ul><li>Goal: </li></ul><ul><li>Detect smoke emission and predict PM and ozone concentration </li></ul><ul><li>Support air quality management and transportation safety </li></ul><ul><li>Impacts: </li></ul><ul><li>PM and ozone air quality episodes, AQ standard exceedance </li></ul><ul><li>Transportation safety risks due to reduced visibility </li></ul><ul><li>Timeline: </li></ul><ul><li>Routine satellite monitoring of fire and smoke </li></ul><ul><li>The smoke event triggers intensified sensing and analysis </li></ul><ul><li>The event is documented for science and management use </li></ul><ul><li>Science/Air Quality Information Needs: </li></ul><ul><li>Quantitative real-time fire & smoke emission monitoring </li></ul><ul><li>PM, ozone forecast (3-5 days) based on smoke emissions data </li></ul><ul><li>Information Technology Needs: </li></ul><ul><li>Real-time access to routine and ad-hoc data and models </li></ul><ul><li>Analysis tools: browsing, fusion, data/model integration </li></ul><ul><li>Delivery of science-based event summary/forecast to air quality and aviation safety managers and to the public </li></ul>Record Smoke Impact on PM Concentrations [email_address] , stefan @me.wustl. edu Smoke Event
    3. 3. IT needs and Capabilities: Web Services Community interaction during events through virtual workgroup sites; quantitative now-casting and observation-augmented forecasting Smoke event summary and forecast suitably packaged and delivered for agency and public decision makers Uncoordinated event monitoring, serendipitous and limited analysis. Event summary by qualitative description and illustration Smoke event summary and forecast for managers (air quality, aviation safety) and the public Services linking tools Service chaining languages for building web applications; Data browsers, data processing chains; Tools for navigating spatio-temporal data; User-defined views of the smoke; Conceptual framework for merging satellite, surface and modeling data Most tools are personal, dataset specific and ‘hand made’ Analysis tools for data browsing, fusion and data/model integration Web services for data registration, geo-time-parameter referencing, non-intrusive addition of ad hoc data; communal tools for data finding, extracting Agents (services) to seamlessly access distributed data and provide uniformly presented views of the smoke. Human analysts access a fraction of a subset of qualitative satellite images and some surface monitoring data, Limited real-time data downloaded from providers, extracted, geo-time-param-coded, etc. by each analyst Real-time access to routine and ad-hoc fire, smoke, transport data/ and models How to get there New capabilities Current state IT need vision
    4. 4. Project Domain, New Technologies and Barriers <ul><li>REASoN Project Type: Application – Particulate Air Quality </li></ul><ul><li>Application Environment </li></ul><ul><ul><li>Participants: NASA as provider ; EPA, States, mediators’ as users of data & tech (slide 4) </li></ul></ul><ul><ul><li>Process Goal: Facilitate use of ESE data and technologies in AQ management </li></ul></ul><ul><ul><li>Specific application projects: FASTNET, Fires and Biomass Smoke, CATT </li></ul></ul><ul><li>Current barriers to ESE data use in PM management </li></ul><ul><ul><li>Technological: Resistances to seamless data flow; user-driven processing is tedious </li></ul></ul><ul><ul><li>Scientific: Quantitative usage of satellite data for AQ is not well understood </li></ul></ul><ul><ul><li>Organizational: Lack of tools, skills (and will??) within AQ agencies </li></ul></ul><ul><li>New Information Technologies Applied in the Project </li></ul><ul><ul><li>Web service wrappers for ESE data and associated tools (slide 5) </li></ul></ul><ul><ul><li>Reusable web services for data transformation, fusion and rendering (slide 6) </li></ul></ul><ul><ul><li>Web service chaining (orchestration) tools, ‘web applications’ (slide 7,8) </li></ul></ul><ul><ul><li>Virtual community support tools (e.g. virtual workgroup websites for 1998 Asian Dust Event ) </li></ul></ul><ul><li>Barriers to IT Infusion (not yet clear) </li></ul><ul><ul><li>New technologies are at low tech readiness level , TRL 4-5 </li></ul></ul>
    5. 5. Data Flow & Processing in AQ Management <ul><li>Resistances : Data Access Processing Delivery </li></ul>AQ DATA EPA Networks IMPROVE Visibility Satellite-PM Pattern METEOROLOGY Met. Data Satellite-Transport Forecast model EMISSIONS National Emissions Local Inventory Satellite Fire Locs Status and Trends AQ Compliance Exposure Assess. Network Assess. Tracking Progress AQ Management Reports ‘ Knowledge’ Derived from Data Primary Data Diverse Providers Data ‘Refining’ Processes Filtering, Aggregation, Fusion Driving Forces : Provider Push User Pull Information Engineering: Info driving forces, source-transformer-sink nodes, processes (services) in each node, flow & other impediments, overall systems ‘modeling’ and analysis
    6. 6. A Wrapper Service: TOMS Satellite Image Data <ul><li>Given the URL template and the image description, the wrapper service can access the image for any day, any spatial subset using a HTTP URL or SOAP protocol, ( see TOMS image data through a web services-based Viewer) </li></ul><ul><li>For web-accessible data, the wrapping is ‘non-intrusive’, i.e. the provider does not have to change, only expose the data in structured manner. Interoperability (value) can be added retrospectively and by 3 rd party </li></ul><ul><li>Check the DataFed.Net Catalog for the data ‘wrapped’ by data access web services (not yet fully functional) </li></ul>src_img_width src_img_height src_margin_right src_margin_left src_margin_top src_margin_bottom src_lon_min src_lat_max src_lat_min src_lon_max Image Description for Data Access: src_image_width=502 src_image_height=329 src_margin_bottom=105 src_margin_left=69 src_margin_right=69 src_margin_top=46 src_lat_min=-70 src_lat_max=70 src_lon_min=-180 src_lon_max=180 The daily TOMS images (virtually no metadata) reside on the FTP archive, e.g. ftp://toms. gsfc . nasa . gov /pub/ eptoms /images/aerosol/Y2000/IM_ aersl _ ept _20000820. png URL template:[yyyy]/IM_aersl_ept_[yyyy][mm][dd].png Transparent colors for overlays RGB(89,140,255) RGB(41,117,41) RGB(23,23,23) RGB(0,0,0) ttp ://capita.wustl. edu / dvoy _2.0.0/ dvoy _services/ cgi . wsfl ?view_state= TOMS_AI&lat_min=0&lat_max=70& lon _min=-180& lon _max=-60&datetime=2001-04-13&image_width=800&image_height=500 http://capita.wustl. edu / dvoy _2.0.0/ dvoy _services/ cgi . wsfl ?view_state= NAAPS_GLO_DUST_AOT&lat_min=0&lat_max=70& lon _min=-180& lon _max=-60&datetime=2001-04-13&image_width=800&image_height=500 http://capita.wustl. edu / dvoy _2.0.0/ dvoy _services/ cgi . wsfl ?view_state= VIEWS_Soil&lat_min=0&lat_max=70& lon _min=-180& lon _max=-60&datetime=2001-04-13&image_width=800&image_height=500
    7. 7. Generic Data Flow and Processing for Browsing DataView 1 Data Processed Data Portrayed Data Process Data Portrayal/ Render Abstract Data Access View Wrapper Physical Data Abstract Data Physical Data Resides in autonomous servers; accessed non-intrusively by data and view-specific wrappers Abstract Data Abstract data slices are requested by viewers; uniform data are delivered by wrapper services DataView 2 DataView 3 View Data Processed data are delivered to the user as multi-layer views by portrayal and overlay web services Processed Data Data passed through filtering, aggregation, fusion and other processing web services
    8. 8. Service Oriented Architecture: Data AND Services are Distributed <ul><li>Peer-to-peer network representation </li></ul>Data, as well as services and users (of data and services) are distributed Users compose data processing chains form reusable services Intermediate and resulting data are also exposed for possible further use Processing chains can be further linked into complex value-adding data ‘refineries’ Service chain representation User Tasks: Fi nd data and services Compose service chains Expose output User Carries less Burden In service-oriented peer-to peer architecture, the user is aided by software ‘agents’ Control Data Process Process Process Data Service Catalog Process Chain 2 Chain 1 Chain 3 Data Service
    9. 9. An Application Program: Voyager Data Browser <ul><li>The web-program consists of a stable core and adoptive input/output layers </li></ul><ul><li>The core maintains the state and executes the data selection, access and render services </li></ul><ul><li>The adoptive, abstract I/O layers connects the core to evolving web data, flexible displays and to the a configurable user interface: </li></ul><ul><ul><li>Wrappers encapsulate the heterogeneous external data sources and homogenize the access </li></ul></ul><ul><ul><li>Device Drivers translate generic, abstract graphic objects to specific devices and formats </li></ul></ul><ul><ul><li>Ports connect the internal parameters of the program to external controls </li></ul></ul><ul><ul><li>WDSL web service description documents </li></ul></ul>Data Sources Controls Displays I/O Layer Device Drivers Wrappers App State Data Flow Interpreter Core Web Services WSDL Ports