1 / 20

Air Quality Data Exchange

Air Quality Data Exchange. Exchange Network Users Meeting April 18th, 2006. Why we need the AQDE. AQS QA - 3 month time lag in the data that is available AirNowTech Most states only submit Ozone and PM2.5 data Request from another state directly

faraji
Télécharger la présentation

Air Quality Data Exchange

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Air Quality Data Exchange Exchange Network Users Meeting April 18th, 2006

  2. Why we need the AQDE • AQS • QA - 3 month time lag in the data that is available • AirNowTech • Most states only submit Ozone and PM2.5 data • Request from another state directly • Typically a substantial delay before receiving a response from the provider • Most transactions via postal mail • Time for a provider to prepare the data

  3. Project Objectives Drastically reduce the waiting time for states to obtain air quality data • Demonstrate state to EPA • AQS data exchange via CDX • AirNow data exchange on AirNow node • Demonstrate state to state XML data exchange utilizing the EN • hourly • minute (NJ) • Demonstrate the state to state flow of AQS data geospatially.

  4. Many Thanks • EPA • Funding • AQS (Nick Mangus) • AirNow (Phil Dickerson) • Partners • Delaware • New York • New Jersey

  5. enfoTech • XML data flow • Project management • Sonoma Technologies • AirNowTech • ESRI • GIS Technology

  6. AQDE Schema • AQDE = AQS version 2 • Upgraded the AQS schema to be ESAR compliant • Additional data elements for AirNow. • Allows states to • flow data to AQS • flow data to AirNowTech • support state to state data flow

  7. When EPA is ready to accept AirNow data over the Exchange Network, we will have 1 schema that works for everything. • Reduces work on states.

  8. Discoverable Web Services • Will register web services on Data Registry • Oregon DEQ • Users will be able to use the Data Discovery Tool or Service to find AQDE web services

  9. Leveraging Schema and Web Services • Reusing this flow for NJ Homeland Security data flow • Dept. of Health - PHIN (Public Health Information Network).

  10. Geospatial Analysis

  11. AirNow

  12. AirNow/AirNowTech • AirNow • General public • Hourly data – AQI for Ozone and PM2.5 • GIF images • AirNowTech • Government and academia • Hourly data - Absolute data values • Additional parameters and met data • Historical data • GIS

  13. AirNowTech Navigator

  14. Issues with Existing AirNow Data & Apps • Cannot submit data to AirNowTech with web services or XML • States need to maintain separate data exchange mechanisms to support the submission of data to AirNow. • In many cases AirNowTech does not contain updated or corrected data.

  15. AQDE Solution

  16. Enhanced Navigator • Create a web service interface to retrieve submitted files. • New AirNow node, separate from CDX • Create data transformation module were • XML file is parsed directly into the AirNow database. • XML file is converted into .obs files, which is processed into AirNow database.

  17. Create automated processing of data correction & updates. • States will submit data to the AIRNow Node using the AQDE XML Format. • Submission will include all updates since the last submission. • Submission can be scheduled through the state’s node client or other scheduling software.

  18. Challenges • Choosing a GIS Solution • New application • Modification of existing application • Balancing the implementation of the AQDE flow with the implementation of new air monitoring systems.

  19. Next Steps • Implement state to state flow • Begin enhancements to Navigator to accept XML flow • Face to face meeting to discuss flow and GIS development • TPA

  20. Results • Out of state air quality data on demand • Use with any analysis method • Reduced work for the states • 1 schema 2 flows • Enhanced AirNowTech • More updated and corrected data • Raising the profile of XML and web services in the air science community • Schema and web services that can be reused in future applications. • Better information for health and homeland security decision-making.

More Related