BLM REA COP 2010 Blackbrush Mormon Tea Shrubland Distribution

Metadata Updated: November 12, 2020

The LANDFIRE vegetation layers describe the following elements of existing and potential vegetation for each LANDFIRE mapping zone: environmental site potentials, biophysical settings, existing vegetation types, canopy cover, and vegetation height. Vegetation is mapped using predictive landscape models based on extensive field reference data, satellite imagery, biophysical gradient layers, and classification and regression trees.DATA SUMMARYThe biophysical settings (BpS) data layer represents the vegetation that may have been dominant on the landscape prior to Euro-American settlement and is based on both the current biophysical environment and an approximation of the historical disturbance regime. It is a refinement of the environmental site potential map; in this refinement, we attempt to incorporate current scientific knowledge regarding the functioning of ecological processes - such as fire - in the centuries preceding non-indigenous human influence. Map units are based on NatureServe's Ecological Systems classification, which is a nationally consistent set of mid-scale ecological units (Comer and others 2003). LANDFIRES's use of these classification units to describe biophysical settings differs from their intended use as units of existing vegetation. As used in LANDFIRE, map unit names represent the natural plant communities that may have been present during the reference period. Each BpS map unit is matched with a model of vegetation succession, and both serve as key inputs to the LANDSUM landscape succession model (Keane and others 2002). The LANDFIRE BpS data layer is similar in concept to potential natural vegetation group layers produced in efforts related to fire regime condition class (Schmidt and others 2002; http://www.frcc.gov ).The first step in producing the LANDFIRE BpS data layer is the creation of an environmental site potential (ESP) layer. To create the ESP data layer, we first assign field plots to one of the ESP map unit classes (similar to BpS units in nomenclature but sometimes different in meaning). Go to http://www.landfire.gov/participate_acknowledgements.php for more information regarding contributors of field plot data. Assignments are based on presence and abundance of the indicator plant species recorded on the plots and on the ecological amplitude and competitive potential of these species. We then intersect plot locations with a series of 30-meter spatially-explicit gradient layers. Most of the gradient layers used in the predictive modeling of ESP are derived using the WX-BGC simulation model (Keane and Holsinger, in preparation; Keane and others 2002). WX-BGC simulations are based largely on spatially extrapolated weather data from DAYMET (Thornton and others 1997; Thornton and Running 1999; http://www.daymet.org) and on soils data in STATSGO (NRCS 1994). Additional indirect gradient layers, such as elevation, slope, and indices of topographic position, are also used. We use data from plot locations to develop predictive classification tree models, using See5 data mining software (Quinlan 1993; Rulequest Research 1997), for each LANDFIRE map zone. These decision trees are applied spatially to predict the ESP for every pixel across the landscape.Next, map units in the ESP layer are evaluated and, in some cases, split to reflect different fire regimes. These splits are made within each LANDFIRE map zone using a combination of plot data, gradient data, input from vegetation dynamics models, and additional See5 classification tree models. We then merge split map units back into the original ESP layer to create a BpS data layer. Finally, pixel values in the BpS layer are, in some cases, modified based on a comparison with the LANDFIRE existing vegetation type (EVT) layer created with the use of 30-meter Landsat ETM satellite imagery. We make such modifications only in non-vegetated areas (such as water, rock, snow, or ice) and where information in the EVT layer clearly enables a better depiction of the biophysical settings concept.The BpS data layer is used in LANDFIRE to depict reference conditions of vegetation across landscapes. The actual time period for this data set is a composite of both the historical context provided by the fire regime and vegetation dynamics models and the more recent field and geospatial data used to create it. The weather data used in DAYMET were compiled from 1980 to 1997. Refer to spatial metadata for date ranges of field plot data and satellite imagery for each LANDFIRE map zone.

Access & Use Information

License: No license information was provided. If this work was prepared by an officer or employee of the United States government as part of that person's official duties it is considered a U.S. Government Work.

Downloads & Resources

Dates

Metadata Date September 15, 2016
Metadata Created Date November 12, 2020
Metadata Updated Date November 12, 2020
Reference Date(s) January 1, 2006 (publication)
Frequency Of Update notPlanned

Metadata Source

Harvested from DOI Open Data

Additional Metadata

Resource Type Dataset
Metadata Date September 15, 2016
Metadata Created Date November 12, 2020
Metadata Updated Date November 12, 2020
Reference Date(s) January 1, 2006 (publication)
Responsible Party United States Forest Service, Rocky Mountain Research Station, Missoula Fire Sciences Laboratory, LANDFIRE Project (Point of Contact)
Contact Email
Guid
Access Constraints Use Constraints: These data are provided by Bureau of Land Management (BLM) "as is" and may contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived, and both scale and accuracy may vary across the data set. These data may not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office for which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This information may be updated without notification., Access Constraints: None, these data are considered public domain
Bbox East Long -106.221558
Bbox North Lat 41.747484
Bbox South Lat 35.429016
Bbox West Long -114.593675
Coupled Resource
Frequency Of Update notPlanned
Licence The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.
Metadata Language
Metadata Type geospatial
Progress completed
Spatial Data Service Type
Spatial Reference System
Spatial Harvester True

Didn't find what you're looking for? Suggest a dataset here.