Reference Data
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data. LF collects data through user submitted data contributions and by searching for data on websites and agency databases/Systems of Record (SOR).
To facilitate annual updates, LF needs as much time as possible to process data. LF is asking for data to be submitted or available in database systems by October 31st. Please make every effort to have your FY 2025 data accessible to LF by October 31, 2025. This may include entering data into online databases/Systems of Record (SOR) so it can be obtained by LF. Data submitted after the deadline will be used if schedules allow in LF2024 production work. All data contributions must meet LF requirements.
The primary focus of this data call is to collect FY 2025 disturbance and treatment activities. To make annual updates possible we will be asking for data from the fiscal year which runs from 10/01/2024 – 09/30/2025. LF now requires disturbance/treatment date or fiscal year to be included with your data submission, this will ensure your data are processed correctly. The secondary focus is to collect vegetation/fuel plot data. LF also welcomes feedback on current products.
LF would like your help to fill in data holes and gaps that exist for disturbance and treatment perimeters from state agencies. State agency data is critical in creating the best products possible. Please visit the State Agency Data webpage to see which state agencies have or have not provided disturbance and treatment data to LF. Your involvement is important to support improved accuracy of the data.
Disturbance/Treatment polygons: Disturbance and treatment polygons are first priority data for updates (LF 2022, LF 2023, etc.) and are processed and maintained in the LF Events Geodatabase.
|
|
Vegetation and Fuel Plot data: Vegetation and fuel plot data are processed and maintained in the LF Reference Database (LFRDB). New plot data with species cover information are being used for annual updates and data submissions will be processed as time allows.
| Plot Theme | format |
| geo-referenced vegetation and fuel conditions | tabular - text files, spreadsheets, relational databases |
| spatial- shapefiles, geodatabases, coverages |
Lidar Data: Lidar data is used to develop vegetation structure models.
- LF uses airborne lidar data collections to develop vegetation structure models. Please provide links and contact information to obtain data that are available to the public.
- If data are not publicly accessible, please contact the LF Reference Data Administrator to determine the best method for transfer.
Feedback on LF products: Feedback is secondary priority data for updates and remaps. Submit feedback through the LF Help Desk.
Disturbance/Treatment polygons: Disturbance and treatment polygons are first priority data for updates (LF 2022, LF 2023, etc.) and are processed and maintained in the LF Events Geodatabase.
|
|
Vegetation and Fuel Plot data: Vegetation and fuel plot data are processed and maintained in the LF Reference Database (LFRDB). New plot data with species cover information are being used for annual updates and data submissions will be processed as time allows.
| Plot Theme | format |
| geo-referenced vegetation and fuel conditions | tabular - text files, spreadsheets, relational databases |
| spatial- shapefiles, geodatabases, coverages |
Lidar Data: Lidar data is used to develop vegetation structure models.
- LF uses airborne lidar data collections to develop vegetation structure models. Please provide links and contact information to obtain data that are available to the public.
- If data are not publicly accessible, please contact the LF Reference Data Administrator to determine the best method for transfer.
Feedback on LF products: Feedback is secondary priority data for updates and remaps. Submit feedback through the LF Help Desk.
Brenda Lundberg
LANDFIRE Reference Data Administrator
blundberg@contractor.usgs.gov
Brenda Lundberg
LANDFIRE Reference Data Administrator
blundberg@contractor.usgs.gov
Data Contributions
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data.
Disturbance and treatment polygons are processed and maintained in an events geodatabase. The LF Events Geodatabase is used to inform updates to existing vegetation and fuel layers.
LF primary focus for this data call is to collect disturbance and treatment polygons from FY 2025 (10/01/2024-09/30/2025). If you submit more recent or older data, LF will archive the data for evaluation and potential use in future mapping updates or comprehensive remaps. Refer to Disturbance Data Processing to learn how LF evaluates and processes polygon data.
Types of Disturbance and Treatment Data
• Wildfires
• Development
• Insect and Disease
• Weather Damage
• Chemical
• Harvest/Thinning
• Mechanical
• Prescribed Fires
• Seeding/Planting
Attributes Requested
• Disturbance/Treatment type
• Disturbance/Treatment fiscal year or date
• Disturbance/Treatment name
• Start date and/or End date
• Severity
• Reporting entity/agency
• Notes (e.g., effects on veg. or fuel)
Data Format
We will accept data in various formats, including ESRI shapefiles, geodatabases, and ArcInfo coverages. Supporting information, including definitions of the fields and any codes in the data tables, should accompany the data to ensure correct interpretation.
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data.
Disturbance and treatment polygons are processed and maintained in an events geodatabase. The LF Events Geodatabase is used to inform updates to existing vegetation and fuel layers.
LF primary focus for this data call is to collect disturbance and treatment polygons from FY 2025 (10/01/2024-09/30/2025). If you submit more recent or older data, LF will archive the data for evaluation and potential use in future mapping updates or comprehensive remaps. Refer to Disturbance Data Processing to learn how LF evaluates and processes polygon data.
Types of Disturbance and Treatment Data
• Wildfires
• Development
• Insect and Disease
• Weather Damage
• Chemical
• Harvest/Thinning
• Mechanical
• Prescribed Fires
• Seeding/Planting
Attributes Requested
• Disturbance/Treatment type
• Disturbance/Treatment fiscal year or date
• Disturbance/Treatment name
• Start date and/or End date
• Severity
• Reporting entity/agency
• Notes (e.g., effects on veg. or fuel)
Data Format
We will accept data in various formats, including ESRI shapefiles, geodatabases, and ArcInfo coverages. Supporting information, including definitions of the fields and any codes in the data tables, should accompany the data to ensure correct interpretation.
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data.
LF relies on user contributed plot data for training sites in mapping processes. All acceptable plot data will be converted and archived in the LF Reference Database (LFRDB) for evaluation and potential use in future mapping needs.
New plot data with species cover information are being used for annual updates. Repeat measurements of plots are also welcome. LF will incorporate additional data as time and production schedules allow or archive data for future evaluation. Refer to Plot Data Processing and Value of Georeferenced Vegetation Plots to LANDFIRE to learn how LF evaluates and processes plot data.
Types of Vegetation of Fuel Plot Data
- describes existing vegetation and/or fuel conditions
- come from government and non-government sources
- was originally compiled for inventory, monitoring, mapping, and research
Attributes Requested
- must be geo referenced
- can be any subset of the data from the vegetation and/or fuel categories in LF Plot Data Attributes table.
| LF Plot Data Attributes | |
| Category | Possible Plot Attributes |
| Sampling Unit | XY coordinates |
| Sampling date | |
| Vegetation | Cover type and/or potential vegetation type |
| Full or partial list of plant taxa with estimates of canopy cover and height | |
| Measurements of individual trees can include diameter, height, crown base height, crown ratio, crown class, or density | |
| Fuel | Counts or biomass measures of fine and coarse woody material |
| Depth or biomass measures of litter and duff layers | |
| Biomass measures of live and dead shrub or herbaceous material | |
Data Format:
We will accept data in various formats
- tabular - text files, spreadsheets, relational databases
- spatial - shapefiles, geodatabases, coverages
Supporting information, including definitions of the fields and any codes in the data tables, should accompany the data to ensure correct interpretation. Project descriptions, final reports, data dictionaries, or plot photos are helpful where available.
The LFRDB Data Dictionary shows the attributes that LF archives from vegetation and fuel plot contributions. Not all attributes are needed for the data to be useful for LF.
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data.
LF relies on user contributed plot data for training sites in mapping processes. All acceptable plot data will be converted and archived in the LF Reference Database (LFRDB) for evaluation and potential use in future mapping needs.
New plot data with species cover information are being used for annual updates. Repeat measurements of plots are also welcome. LF will incorporate additional data as time and production schedules allow or archive data for future evaluation. Refer to Plot Data Processing and Value of Georeferenced Vegetation Plots to LANDFIRE to learn how LF evaluates and processes plot data.
Types of Vegetation of Fuel Plot Data
- describes existing vegetation and/or fuel conditions
- come from government and non-government sources
- was originally compiled for inventory, monitoring, mapping, and research
Attributes Requested
- must be geo referenced
- can be any subset of the data from the vegetation and/or fuel categories in LF Plot Data Attributes table.
| LF Plot Data Attributes | |
| Category | Possible Plot Attributes |
| Sampling Unit | XY coordinates |
| Sampling date | |
| Vegetation | Cover type and/or potential vegetation type |
| Full or partial list of plant taxa with estimates of canopy cover and height | |
| Measurements of individual trees can include diameter, height, crown base height, crown ratio, crown class, or density | |
| Fuel | Counts or biomass measures of fine and coarse woody material |
| Depth or biomass measures of litter and duff layers | |
| Biomass measures of live and dead shrub or herbaceous material | |
Data Format:
We will accept data in various formats
- tabular - text files, spreadsheets, relational databases
- spatial - shapefiles, geodatabases, coverages
Supporting information, including definitions of the fields and any codes in the data tables, should accompany the data to ensure correct interpretation. Project descriptions, final reports, data dictionaries, or plot photos are helpful where available.
The LFRDB Data Dictionary shows the attributes that LF archives from vegetation and fuel plot contributions. Not all attributes are needed for the data to be useful for LF.
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data. LF collects data through user submitted data contributions and by actively searching for data on websites and agency data base systems.
LF has acquired three types of data:
- Disturbance/Treatment Polygon data - disturbance and vegetation/fuel treatment activities — Public LF Events Geodatabase (available for download)
- Vegetation/Fuel plot data - vegetation and fuel information — Public LF Reference Database (LFRDB) (available for download)
- Feedback data — which informed all previous LF versions
Compiled Data — For a list of data contributions, refer to the Compiled Data Table. The priority for this data contribution period is polygon disturbance and vegetation/fuel treatment perimeters from FY 2025. Refer to the Time Span field to determine if the most recent data for your area was collected.
Website and Agency Data — The Website Agency DB Table provides a list of websites or agency databases/Systems of Records (SOR) from which LF acquires data. If your data is stored on one of these websites or agency databases/SOR, verify your updated data are posted to ensure it will be evaluated for potential use in the next LF update.
LANDFIRE (LF) would like to acknowledge and thank everyone who has contributed data. LF collects data through user submitted data contributions and by actively searching for data on websites and agency data base systems.
LF has acquired three types of data:
- Disturbance/Treatment Polygon data - disturbance and vegetation/fuel treatment activities — Public LF Events Geodatabase (available for download)
- Vegetation/Fuel plot data - vegetation and fuel information — Public LF Reference Database (LFRDB) (available for download)
- Feedback data — which informed all previous LF versions
Compiled Data — For a list of data contributions, refer to the Compiled Data Table. The priority for this data contribution period is polygon disturbance and vegetation/fuel treatment perimeters from FY 2025. Refer to the Time Span field to determine if the most recent data for your area was collected.
Website and Agency Data — The Website Agency DB Table provides a list of websites or agency databases/Systems of Records (SOR) from which LF acquires data. If your data is stored on one of these websites or agency databases/SOR, verify your updated data are posted to ensure it will be evaluated for potential use in the next LF update.
LANDFIRE (LF) forms partnerships with many groups and organizations to enhance the richness of the LF Reference Database (LFRDB) and incorporates those contributions into the LF data production process. Three examples of this type of sharing include:
Bureau of Land Management, Assessment Inventory and Monitoring (BLM-AIM): LF and BLM entered into an agreement with the LANDFIRE Program to provide their extensive plot data base to develop or assess LANDFIRE spatial data layers. The data helps the program improve the usability of program products in rangeland areas. BLM AIM is a Major Partner of LF.
Forest Inventory Analysis (FIA): LF and FIA entered into an agreement in 2005 to include FIA data in the LF production process while maintaining the confidentiality of the FIA locations. FIA is a Major Partner of LF and for NRCS.
Natural Resource Conservation Service (NRCS) - National Resource Inventory (NRI): LF and NRI LF and NRI established a formal working relationship in 2015, then renewed a data sharing relationship again in 2020. In 2009, the United States Department of Agriculture (USDA), NRCS and the LF Program collaborated in a pilot project to assess the usefulness of NRCS NRI Program rangeland plot data. The assessment involved a remap of the LF Existing Vegetation Type (EVT) layer in a region of Montana. NRCS is a Supporting Partner of LF.
LANDFIRE (LF) forms partnerships with many groups and organizations to enhance the richness of the LF Reference Database (LFRDB) and incorporates those contributions into the LF data production process. Three examples of this type of sharing include:
Bureau of Land Management, Assessment Inventory and Monitoring (BLM-AIM): LF and BLM entered into an agreement with the LANDFIRE Program to provide their extensive plot data base to develop or assess LANDFIRE spatial data layers. The data helps the program improve the usability of program products in rangeland areas. BLM AIM is a Major Partner of LF.
Forest Inventory Analysis (FIA): LF and FIA entered into an agreement in 2005 to include FIA data in the LF production process while maintaining the confidentiality of the FIA locations. FIA is a Major Partner of LF and for NRCS.
Natural Resource Conservation Service (NRCS) - National Resource Inventory (NRI): LF and NRI LF and NRI established a formal working relationship in 2015, then renewed a data sharing relationship again in 2020. In 2009, the United States Department of Agriculture (USDA), NRCS and the LF Program collaborated in a pilot project to assess the usefulness of NRCS NRI Program rangeland plot data. The assessment involved a remap of the LF Existing Vegetation Type (EVT) layer in a region of Montana. NRCS is a Supporting Partner of LF.
Contribute Feedback
LANDFIRE (LF) welcomes feedback on its current data products. Feedback information addresses potential discrepancies between existing products and known field conditions. Submit feedback to LF's Helpdesk.
Feedback on data helps LF:
- understand the issue(s)
- develop systematic approaches for potential updates
- evaluate efforts for improvement (if within the scope of updates)
Understand that LF does not simply substitute or "stamp in" the data you provide into the LF layers. Rather, LF uses this data to help determine areas of improvement in LF production processes in order to provide a consistent product across all lands.
LF Program Letters
LF Departmental/Agency Direction Letters
LF Program Letters
LF Departmental/Agency Direction Letters
Additional Information
LF Reference Data Requirements minimum information needed for each data type and additional attributes that are highly beneficial to improve data products and provides disturbance and treatment polygon data needs
LF Data Draw Frequently Asked Questions related to contributing data
LF Events Geodatabase Data Dictionary shows the attributes that LF archives from disturbance and treatment data contributions.
Developing Auto-Keys for LF Vegetation Mapping: 2014-2015 CONUS Project Report
LF Reference Data Requirements minimum information needed for each data type and additional attributes that are highly beneficial to improve data products and provides disturbance and treatment polygon data needs
LF Data Draw Frequently Asked Questions related to contributing data
LF Events Geodatabase Data Dictionary shows the attributes that LF archives from disturbance and treatment data contributions.
Developing Auto-Keys for LF Vegetation Mapping: 2014-2015 CONUS Project Report
Does LANDFIRE accept Events from previous years?
No. The production schedule does not allow time for the LANDFIRE team to go back and add Events from previous years.
Does LANDFIRE accept Events from previous years?
No. The production schedule does not allow time for the LANDFIRE team to go back and add Events from previous years.