Data Outputs
HAQAST: 2017 Northern California Wildfires Tiger Team
Lead Contacts: Susan O'Neill, US Forest Service & Minghui Diao, San Jose State University
Short url: http://bit.ly/haqasttiger
CMAQ Air Quality Modeling Results (BAAQMD) - Four Planned Runs
Figure: Modeling Domain
1. No Fires (Anthropogenic and Biogenic Emissions)
2. Baseline ("Business as usual"): BlueSky Fire Emissions, CMAQ Time Profile and Plume Rise (Briggs-based)
3. Sensitivity 1 (hourly ground-based, remotely-sensed time profile): BlueSky Fire Emissions & Plume Rise (Briggs-based), GOES-16 Time Profile (re-run posted 6/10/2019)
4. Sensitivity 2 (100% remotely-sensed): Fire Emissions (GOES-16 FRP, NASA FEER algorithm), Time Profile (GOES-16 Fire Detections), Plume Rise (GOES-16 FRP, Sofiev algorithm)
Inventory of Fire Emissions (USFS, UCD)
Figure: GOES-16 Derived Acres Burned per Hour
Sensitivity 1: BlueSky Fire Emissions & Plume Rise (Briggs-based), GOES-16 Time Profile (new files 6/3/2019)
Sensitivity 2: GOES-16 Fire Emissions (NASA FEER), GOES-16 Time Profile, GOES-16 Plume Rise (Sofiev)
Other Fires Dataset: All fires, excluding the 5 Major Northern California Fires
PM2.5 and Wind Observations Analysis (SJSU, UCR)
Python code, observational data (PM2.5, winds, fire perimeters), and hourly png figures at: https://haze.airfire.org/webaccess/susan/HAQAST/Wildfires_TT/PM25_and_Wind_Obs/
Northern California Health Studies (Draft Summary Table)
MISR October 12, 2017 (NASA)
https://haze.airfire.org/webaccess/susan/HAQAST/Wildfires_TT/MISR/
Data Fusion PM2.5 Surfaces (MODIS, Surface Monitors) (NASA MSFC)
https://haze.airfire.org/webaccess/susan/HAQAST/Wildfires_TT/DataFusionPM2.5/
Monitoring Data Output
Unhealthy for Sensitive Groups (USG)
Monitoring Data Tool - Historical Data
https://tools.airfire.org/historical/
PWFSLSmoke R Package (for working with Monitoring Data)
MAIAC AOD and Plume Injection Height (NASA)
Plume Injection Height
June - November 2018: Monitors within 400km of Sonoma, CA
*For more information about a particular monitor, click the dot on the map and note the “siteName” of the monitor (example: ARB 1037(Spalding)). Next, click on “All Monitors” link under “Monitoring Data Output” section and find the corresponding PNG filename for that monitor (example: ARB1037(Spalding)_lon_.120.787_lat_40.669_arb2.1037_2018_24hrPM2-5.png)
June - November 2017: Monitors within 400km of Sonoma, CA
*For more information about a particular monitor, click the dot on the map and note the “siteName” of the monitor (example: ARB 1037(Spalding)). Next, click on “All Monitors” link under “Monitoring Data Output” section and find the corresponding PNG filename for that monitor (example: ARB1037(Spalding)_lon_.120.787_lat_40.669_arb2.1037_2018_24hrPM2-5.png)
June - November 2016: Monitors within 400km of Sonoma, CA
*For more information about a particular monitor, click the dot on the map and note the “siteName” of the monitor (example: ARB 1037(Spalding)). Next, click on “All Monitors” link under “Monitoring Data Output” section and find the corresponding PNG filename for that monitor (example: ARB1037(Spalding)_lon_.120.787_lat_40.669_arb2.1037_2018_24hrPM2-5.png)
June - November 2015: Monitors within 400km of Sonoma, CA
*For more information about a particular monitor, click the dot on the map and note the “siteName” of the monitor (example: ARB 1037(Spalding)). Next, click on “All Monitors” link under “Monitoring Data Output” section and find the corresponding PNG filename for that monitor (example: ARB1037(Spalding)_lon_.120.787_lat_40.669_arb2.1037_2018_24hrPM2-5.png)