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.

ADDs will be added in 2026 as seasonal data becomes available

Metadata will be added in 2026 as seasonal data becomes available

MoD-FIS Comprehensive Plan 
GB-SW MoD-FIS White Paper 
LANDFIRE Modeling Dynamic Fuels with an Index System Innovations 
MoD-FIS Brings Seasonal Fine Fuels Information to Wildland Fire Mangement 
Scott and Burgan 2005: Standard Fire Behavior Fuel Models: A Comprehensive Set for Use with Rothermel's Surface Fire Spread Model 
 

OLD CONVENTION Extent shorthand - excluding the Insular Areas

LC    L = LANDFIRE    C = CONUS

LH   L = LANDFIRE    H = Hawaii

LA   L = LANDFIRE    A = Alaska

The history of the "capable" naming convention applicable to LF 2020 and earlier versions

Beginning with LF 2016 Remap, an improvement for fuels products in disturbed areas was implemented. Fuels were adjusted to expected current year vegetation conditions for disturbances that had occurred between certain select years that vary by the version. Making the fuels products "capable to X year fuels" or "capable fuels". Beginning with the LF 2020 Update, Existing Vegetation Cover (EVC) and Height (EVH) were also "capable to X year".

This capability was conveyed by including the capable year in the naming convention. A “capable fuels” download example from LF 2020 (CONUS) would look like: 

In the LF 2022 Update, and onward, capability is no longer incorporated into the naming convention. This change was implemented to ensure that the products always match the version year and name. Special attention must be paid to the version number (LF 2022 is version number 230) to distinguish it from earlier versions.

A "capable fuels" download example from LF 2022 (CONUS) would look like: 
 

Then, beginning with the LF 2022 Update, and onward, capability was no longer incorporated into the naming convention. This change was implemented to ensure that the products always math the version year and name.

Previous LANFIRE Naming Convention for LF 2001 - LF 2004

Disturbance (Dist, FDist, VDist, VTM products)

{AK/US/HI}_{ Official Name, all uppercase }{YYYY} – Product Folder

{Product Folder}\Tif\ {ak/us/hi}_{Official Name, all lowercase}{YYYY}.tif

{Product Folder}\General_Metadata\ {ak/us/hi}_{Official Name, all lowercase}{YYYY}.{xml/htm}