MTBS Announcements

Data Quality Review (April 1, 2016)

At the beginning of the MTBS project (2006), Landsat imagery was not freely available and the project could not purchase more than two Landsat scenes per year for any path/row. Consequently, ideal imagery was not always used to map each fire. Image selection was often a compromise between optimum phenology and the number of fires that could be mapped.

Data Release (April 1, 2015)

MTBS released an additional 731 fires to MTBS.gov bringing the total number of fires mapped by the project to 19,227. This data release contains the remaining 2013 fires and a portion of the fires from the 2014 fire season. With this release the MTBS data record now covers the years 1984 through 2013 (the remaining 2014 fires will be published in December 2015).

Data Release (October 1, 2014)

MTBS released an additional 563 fires to MTBS.gov bringing the total number of fires mapped by the project to 18,497. This data release contains a portion of the fires from the 2013 fire season and Texas historical fires from 1984-2012. With this release the MTBS data record now covers the years 1984 through a portion of 2013 (the remaining 2013 fires will be published next spring).

New File Naming Convention Applied to All Fires (October 1, 2014)

The new file naming convention, originally announced on July 31, 2013, has now been applied to all fires in the MTBS archive. We are re-releasing all 1984-2010 fires with their new file names. Please note the originally released data has not changed.  The fire IDs and file naming convention have only been adapted to adhere to the new convention.  Please reference MTBSNamesXwalk (pdf or txt) for a crosswalk of the old naming conventions to the corresponding new names.

New Fire Type Added to MTBS Data Record (April 16, 2014)

The MTBS project has mapped over 2,722 discovered fires covering over 11.8 million acres. Historically, all fire types were assumed to be wildfire (WF) unless they were specifically reported as a prescribed fire (RX) or wildland fire use (WFU) in the original source data. Since discovered fires had no original source data these fires fell into the default WF fire type category resulting in skewed reporting for the WF fire type. Over time, the cumulative impact of including discovered fires in the WF acreage has reached a point where it needed to be addressed.