2015-12-02 Tools Workgroup
Date: December 2, 2015
Time: 1-2:30pm MST
Call in: 1-800-768-2983 and access code 4918837
Webinar: https://join.me/IWDW-Online
IWDW Visualization Tools Workgroup
Links
Tools wiki Meeting minutes and agendasTools workgroup forum IWDW Forum topic on tool development
Current tools
IWDW Data Includes the tools:- Emissions Review
- Source Apportionment
- Model-to-Observation Comparison
- Model Performance Evaluation Plots
- Summary Reports
- IWDW GIS Server demo
Agenda
- Review minutes from October Tools workgroup call
- Status of current tools
- Alignment of IWDW tools with MPE recommendations doc.
- Development priorities
- Relevant GIS layers for geospatial tools
- prioritization of MPE products
- Other items
- Next call
Minutes
Attendees
Ken Rairigh, Chris Pennell, Rebecca Matichuck, Gail Tonnesen, Kevin Briggs, Zac Adelman, Shawn McClure, Dustin Schmidt, Rodger Ames, Tom MooreReview
The group reviewed minutes from the Oct. 20 Tools workgroup call. Most of the action items had been completed, however the model-to-obs data were still being processed for the 2011a/b platforms.
Rodger presented two documents to the group, one was a summary of the current IWDW tools, which documents their current status, including functionality, data sets or modeling platforms included, and plans for future development. The other document, referred to as 'MPE x IWDW', lists key MPE products identified in the EPA MPE recommendations document and aligns these with either current or prospective IWDW tools. The MPE IWDW document is essentially a large table that lists MPE products by modeling activity (such as emissions and PGM) and maps these to IWDW tools. Rodger led the group through the emissions section of the document. The Workgroup identified a need to develop an emissions GIS that will provide a number of MPE products not currently available on current IWDW Tools. A county level emissions GIS can also leverage the IWDW database currently in place for the Emissions Review Tool, thereby enabling rapid development by leveraging current backend infrastructure.
Action Items