The complete dataset for the nationwide 2018 fires is anticipated to be released by the end of August 2020. MTBS is currently developing and will publish a tentative schedule for future data releases. Please check back here for additional updates.
MTBS released 1,296 new fires to MTBS.gov bringing the total number of fires mapped by the project to 22,969. This data release contains all 2017 fires. With this release the MTBS data record now spans the years 1984 through 2017.
Prior to the MTBS.gov website update in Summer 2017, this dataset had multipart features displaying a separate record for each polygon (i.e., multipart features exploded). In the current version of the website, multipart features in the attribute table have been modified to reflect a one-to-one relationship to the number of published fires (i.e., multipart features unexploded). Therefore, the number of records in the attribute table is reduced and accounts for the discrepancy in the number of records between the two versions.
The MTBS project has released a new version of the QGIS Fire Mapping Tool (FMT). The FMT is now compatible with QGIS 2.x and 3.x with this release.
The MTBS project has released the NDVI Profile Tool. This interactive web application gives users the ability to display a multi-temporal NDVI profile that is spatially averaged by a user-defined Landsat Path/Row and categorized by land cover type.
MTBS released 1,337 new fires to MTBS.gov bringing the total number of fires mapped by the
project to 21,673. This data release contains all 2016 fires. With this release the MTBS data
record now spans the years 1984 through 2016.
MTBS has removed several attribute fields from the National Fire Occurrence Dataset. The
removed fields are Fire Year, Fire Month, Fire Day, WRS Path, WRS Row, P Acres, R Acres, State,
Admin, MTBS Zone, GACC, HUC4 Code, HUC4 Name, Version, Revision Code, and Release Date.
The complete dataset for 2016 fires is anticipated to be released Summer 2018. Please check back here for additional updates.
MTBS has discovered an issue in the rendering of our KMZ data when viewed in Google Earth. Caution should be exercised when viewing these data. We are working with Google to rectify this issue and will provide another announcement when it is resolved.