Download Mosaic Data Products

Comments

LF 2020 Update - Reflects important changes to ancillary data and classes, such as a complete recalculation of topography, corrections to aspect that are crucial to fire behavior modeling, a new separate product layer for roads designed for operational use, removal of the developed ruderal classes, designation of new burnable developed classes, replacing recently disturbed classes with modeled vegetation, and transitioning federal agricultural lands to burnable fuels in non-irrigated areas.

LF 2019 Limited - Includes only 2017, 2018, and 2019 disturbances submitted by December 31, 2019. Vegetation and Fuels pixels not mapped as disturbed by LF from 2017–2019 are identical to LF 2016 Remap. Fuels pixels mapped as disturbed by LF from 2012–2019 are transitioned to estimate conditions to a 2021 capable fuel product.

LF 2016 Remap - Uses the latest reference datasets to map disturbance and field reference plots for vegetation mapping; Landsat archives to improve identification of surface water, barren and sparse and reduce the impact of seamlines; and lidar information to create continuous structure products and create a circa 2016 base map for fuels mapping. Fuels products will leverage continuous vegetation structure into fuels production.

LF 2014 - Incorporates disturbance & succession through 2014.

LF 2012 - Incorporates disturbance & succession through 2012.

LF 2010 - Refined urban, agriculture, and wetlands and incorporated disturbance & succession through 2010. Created a suite of data layers for U.S. insular areas.

LF 2008 - Started with LF 1.0.5 and incorporated disturbances (fire, vegetation management, weather, etc.) & succession through 2008.

LF 2001 - Refined Existing Vegetation Type (EVT) based on local feedback. Remapped Existing Vegetation Cover (EVC) and Height (EVH) in forested areas. BPS layer refined in western rangelands using Soil Survey Geographic Database (SSURGO)

* The algorithm required a time series of imagery to identify disturbance, imagery from 1984 - 2008 was used; some areas used imagery through 2009 or 2010, if available.

Checksums are used to verify (check) the integrity of files and identify data transmission errors, typically after copying or moving them. An MD5 checksum is a 32-character hexadecimal number that is computed on a file. If two files have the same MD5 checksum value, then there is a high probability that the two files are the same.

After the user downloads a file to their computer, they can generate an MD5 value on the same file and compare the values. There are a variety of MD5 checksum programs available on the Internet. If the checksum values differ, then there is something wrong with the downloaded file and it should be downloaded and checked again. If problems persist, contact the LANDFIRE Help Desk.

For example: an MD5 value can be generated in MS DOS using the command "CertUtil -hashfile <path><file> MD5", or in linux by using the "md5sum <path><file>" command.