18
06/15/22 06/15/22 1 FETS: State of the System FETS: State of the System Providers, Features, Lessons Learned Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

Embed Size (px)

Citation preview

Page 1: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 11

FETS: State of the SystemFETS: State of the SystemProviders, Features, Lessons LearnedProviders, Features, Lessons Learned

August 31, 2009FETS Project Meeting

Boise, ID

Page 2: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 22

OutlineOutline

• Review Status Report– FETS functions and features

– Data acquisition status

– Recent user case studies

– Solicit feedback from the group

• Present results of generating a Level 1 emissions inventory for 2008

Page 3: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 33

Page 4: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 44

Page 5: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 55

User Case StudiesUser Case Studies• ICS-209 data errors

– BACKGROUND: Maricopa Co downloaded daily wildfire activity for 2008. Acreage values in some cases were more than twice what ICS-209 reported.

– PROBLEM: FETS was double-counting acres for fires that had a lapse in daily reporting.

– SOLUTION: Queries for loading ICS-209 data into the system were modified. All wildfire data was re-loaded into the FETS.

• Washington Agricultural Burns in Alaska!?– BACKGROUND: Alaska DEC alerted us to fires appearing in

Alaska that never occurred, or that occurred the year before.

– PROBLEM: Washington agricultural data shared the same identification schema with Alaska data. Washington fires were erroneously being assigned to Alaskan event.

– SOLUTION: Queries that matched new data with existing records were improved to avoid cross-contamination. Washington ag data and Alaska data were re-loaded.

Page 6: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 66

User Case StudiesUser Case StudiesNew Mexico WFU reporting

– BACKGROUND: New Mexico reports their own WFU activity. In some cases, the map shows co-located wildfires reported by ICS-209 with the same name as a WFU reported by NM.

– PROBLEM: Data are being reported in New Mexico to two different sources as unique fire types (but with the same name).

– SOLUTION: UNRESOLVED. Unclear whether the two sources of data are double-counting or complementary (i.e. the same fire is being managed two ways). Fires at right were still active at the time of download and may be incomplete. No examples exist from 2008.

Page 7: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 77

Level 1 Emissions Inventories

include:

– Daily activity and calculated emissions

– ERTs used and % reduction, if reported

– Natural/Anthropogenic classification

Level 1 Emissions Inventories

do not include:

– Explicit smoldering calculations*

– Plume Characteristics

– Emissions of PAHs, PABs, Mercury, or other toxics

*CONSUME calculates smoldering and flaming stages together

Page 8: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 88

Status: Data AcquisitionStatus: Data Acquisition

ProviderFederal

State

Private

Agricultural

Rangeland

Alaska X X X X

Arizona X X X

California X X X X

Colorado X X X

Idaho X X X X

Montana X X X

Oregon X X X X X

Nevada X X X

New Mexico X X X X

Nez Perce Tribe X X X

Utah X X X

Washington X X X X

Wyoming X X X

Active Pending Known, not initiated

Page 9: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 99

FETS 2008 Level 1FETS 2008 Level 1Emissions InventoryEmissions Inventory

• So…you’re up-to-date on the status of the FETS. You may be wondering, “Does it work?”

• We wondered the same thing…so we tested it.

• Had a person with little/no experience with FETS query and download data:

– 2008 - WRAP Region - All fire types

– WRAP & CONSUME-based emissions

Page 10: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1010

FETS 2008 Level 1FETS 2008 Level 1Emissions InventoryEmissions Inventory

Basic Approach

• Downloaded all data for 2008 from Web site

• Performed diagnostic checks to assess confidence level in data

• Set up EXCEL Pivot Tables to review data

• Compared to other published sources (WF only)

• Summarized findings

Page 11: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1111

FETS 2008 Level 1FETS 2008 Level 1Emissions InventoryEmissions Inventory

Summary of Findings

• IT WORKS!!...with room for fixes/improvements

– Decent agreement with other available fire data

– CONSUME tends to estimate lower emissions (PM2.5) than WRAP-method (probably due to adjustments in fuel consumption)

• Some coding fixes for the CONSUME suite are necessary

– Data acquisition (for Rx, Ag, NFR) is the key

– Pretty modest effort to download, QA/QC, and summarize fire activity and emissions data.

Page 12: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1212

2008 Level 1 EI For the WRAP 2008 Level 1 EI For the WRAP RegionRegion

Basic Approach

• Download all data for 2008 from Web site

• Perform simple diagnostic checks

• Compare to other published sources (WF only)

• Summarize results

Page 13: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1313

Page 14: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1414

Page 15: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1515

Page 16: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1616

Page 17: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1717

Planned vs. Accomplished Acres 2008Planned vs. Accomplished Acres 2008Pre-Approval Records Only | Rx, Ag, NFR Pre-Approval Records Only | Rx, Ag, NFR

FiresFires

By MonthBy Month

By StateBy State

Page 18: 1/13/20161 FETS: State of the System Providers, Features, Lessons Learned August 31, 2009 FETS Project Meeting Boise, ID

04/21/2304/21/23 1818

Planned vs. Accomplished Acres 2008Planned vs. Accomplished Acres 2008All Records | Rx, Ag, NFR FiresAll Records | Rx, Ag, NFR Fires

By MonthBy Month

By StateBy State