GIS Metadata

BLM OR Fire History Polygon

Frequently-asked questions:

What does this data set describe?

BLM OR Fire History Polygon

FIRE_POLY: Fire History polygons represent the final mapped wildfire perimeter of all BLM fires 10 acres or larger across Oregon and Washington. In addition, wildfires smaller than 10 acres may be included along with many other non-BLM Federal and State agencies wildfires.

Supplemental information:
BLM (Bureau of Land Management) A published revision of the Department Manual's Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm),BLM (Bureau of Land Management) Data Standard is posted here: http://www.blm.gov/or/gis/data.php There is no lower size limit for fires to be included, although BLM does require capture of a final perimeter on fires 10 acres or larger in Type 1 (BLM land protected by BLM) and Type 2 (BLM land protected by another Federal agency under a cooperative agreement or contract; including mutual aid agreements) scenarios. Single tree ignitions and extremely small fires are generally omitted from FIRE_POLY and found only on FIRE_POINT. In addition, while FIRE_POINT contains fire origin points for most of the fires whose perimeters are included on FIRE_POLY, there are perimeters without a corresponding point; particularly for historic fires. It should be noted in the standard that the national standards (both BLM and Interagency) are being considered for revision and this standard should be considered interim until those updates occur.,BLM (Bureau of Land Management)

  1. How should this data set be cited?

    U.S. Department of Interior, Bureau of Land Management (BLM), 20180111, BLM OR Fire History Polygon.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.509074
    East: -116.346536
    North: 49.109000
    South: 41.632276

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar date: 20180111
    Currentness reference:
    publication date

  5. What is the general form of this data set?

    Geospatial data presentation form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (6437)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 8.98315284119521e-009. Longitudes are given to the nearest 8.98315284119521e-009. Latitude and longitude values are specified in Decimal Degrees.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    Points of origin for wildfires (Source: BLM)

    Internal feature number. (Source: Esri)

    Sequential unique whole numbers that are automatically generated.

    The unit identifier for the agency that has primary protection responsibility at the point of origin at the time of the incident.  The administrative unit at the fire's point of origin. Domain values to lengthy to list. See Data Standard for complete list. (Source: NWCG)

    Feature geometry. (Source: Esri)

    Coordinates defining the features.

    Official fire incident number assigned at dispatching office.  Obtained from Wildcad application. A four to six digit number assigned to a fire by the reporting unit that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.   (Source: NWCG)

    Cost accounting tracking number assigned by the FireCode application.  For the BLM, pre-Fiscal Year 2004 (prior to the FireCode system), this is the fire number assigned to the incident by the reporting office. (Source: NWCG)

    The name assigned to an incident; assigned by responsible land management unit. (Source: NWCG)

    Name of complex.  Applicable only if fire was incorporated into a complex at any point before declared contained.  A complex is two or more incidents located in the same general area which are assigned to a single incident commander or unified command.  Incidents are an occurrence, either human-caused or natural phenomenon, that requires action or support by emergency service personnel to prevent or minimize loss of life or damage to property and/or natural resources. (Source: NWCG)

    The year in which the fire occurred.  In YYYY format. (Source: NWCG)

    A unique identifier generated for each wildland fire. Concatenation of fire year, FIRE_UNIT_ID, and FIRE_NUM yyyy-SSUUUU-xxxxxx yyyy = calendar year SSUUUU = FIRE_UNIT_ID xxxxxx = local incident identifier (FIRE_NUM)  (Source: NWCG)

    The Unique Identifier (FireID) assigned to each fire in the Wildland Fire Management Information system (DOI fires only). (Source: WFMI (Wildland Fire Management Information))

    The date the fire was confirmed to exist or was reported as discovered.  In YYYYMMDD format.  UNKNOWN is an allowable entry. (Source: NWCG)

    A combination of the BLM administrative state and field office which has administrative responsibility for the spatial entity.  This includes which office covers the entity for planning purposes and which office is the lead for GIS edits.  Another agency or individual may have the physical management responsibility for the on-the-ground entity.  This field applies particularly when a spatial entity crosses resource area or district boundaries and the administrative responsibility is assigned to one or the other rather than splitting the spatial unit.  Similarly, OR/WA BLM may have administrative responsibility over some area that is physically located in Nevada, Idaho, and California and vice versa.  When appropriate, the office can be identified only to the district or even the state level rather than to the resource area level. (Source: BLM)

    Oregon/Washington BLM
    Burns District Office
    Three Rivers Field Office
    Andrews Field Office
    Coos Bay District Office
    Umpqua Field Office
    Myrtlewood Field Office
    Eugene District Office
    Siuslaw Field Office
    Upper Willamette Field Office
    Lakeview District Office
    Klamath Falls Field Office
    Lakeview Field Office
    Medford District Office
    Butte Falls Field Office
    Ashland Field Office
    Grants Pass Field Office
    Glendale Field Office
    Prineville District Office
    Central Oregon Field Office
    Deschutes Field Office
    Roseburg District Office
    Swiftwater Field Office
    South River Field Office
    Salem District Office
    Cascades Field Office
    Marys Peak Field Office
    Tillamook Field Office
    Vale District Office
    Malheur Field Office
    Baker Field Office
    Jordan Field Office
    Spokane District Office
    Wenatchee Field Office
    Border Field Office

    The general circumstance which caused a fire or set the stage for its occurrence (Human vs Natural). (Source: BLM)

    Cause of the fire is not known
    Fire was caused by humans
    Fire was naturally caused (e.g., lightning)

    More detailed description of the cause of a fire than what is provided in CAUSE_CAT. (Source: BLM)

    Name (mixed case, first and last) of the person or agency who provided the fire perimeter or point coordinates.  For FIRE_POINT, this may be the name of the national database point coordinates were downloaded from. (Source: BLM)

    The actual source of the GIS coordinates for the points.  If the line is copied from another theme, and already has COORD_SRC, it should be reviewed and may need to be changed for use in this dataset. (Source: BLM)

    Lines from or snapped to the CADNSDI dataset
    Lines duplicated or buffered from Cartographic Feature Files
    Digital Elevation Model (30m or better accuracy) used for creation of contours
    Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs Typical Accuracies (40 feet)
    Lines generated to connect discontinuous features
    Screen digitized linework over Digital Orthoquad backdrop
    Screen digitized linework over Digital Raster Graphic (USGS) backdrop
    Lines snapped to Geographic Coordinate Database Points
    Lines obtained from a Global Positioning System device
    Linework derived from interpretation of non-photographic imagery
    Digitized line work from hardcopy map
    Lines duplicated from Digital Master Title Plat
    Source layer from BLM GIS
    Survey methods were used to create the linework
    Tiger data
    Coordinates only given as a legal description (township, range,section)
    Unknown coordinate source
    WODDB (Western Oregon Digital Database) Photogrammetric

    Date the coordinates, whose source is listed in COORD_SRC, were collected. In YYYYMMDD format. (Source: BLM)

    How close, in feet, the spatial GIS depiction is to the actual location on the ground.  There are several factors to consider in GIS error:  scale and accuracy of map-based sources, accuracy of GPS equipment, and the skill level of the data manipulators.  A value of "0" indicates no entry was made.  This is the correct value when the COORD_SRC is another GIS theme (Digital Line Graph, Cadastral National Spatial Data Infrastructure and Digital Elevation Model) because the accuracy is determined by that theme.  However, if COORD_SRC is MAP (digitized from a paper map) or GPS, a value of "0" indicates a missing value that should be filled in either with a non-zero number or "-1."  A value of "-1" indicates that the accuracy is unknown and no reliable estimate can be made. (Source: BLM)

    Official final reported burned acres.  May differ from GIS_ACRES total. (Source: NWCG)

    Acres measured in GIS (Source: BLM)

    Free text for comments about the fire point (Source: BLM)

    Name of the corporate geodatabase version previously used to edit the record. (Source: BLM)

    Automatically generated ID number (Source: ESRI)

    Area of feature in internal units squared. (Source: ESRI)

    Length of feature in internal units. (Source: ESRI)

    Entity and attribute overview:
    For full description of data see Abstract. Data Standard if one exists may be found here: https://www.blm.gov/or/gis/data.php
Back to Top

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

    • U.S. Department of Interior, Bureau of Land Management (BLM)

  2. Who also contributed to the data set?

    Oregon BLM

  3. To whom should users address questions about the data?

    Dale Guenther
    US Forest Service
    System Analyst
    333 Southwest First Avenue
    Portland, OR97204

    (503) 808-2188 (voice)
Back to Top

Why was the data set created?

This dataset is used to display historic wildfire perimeters on maps. The number and spatial extent of fire across the landscape is important information for natural resource management and planning activities. Fire perimeters will be combined with a wide variety of other GIS datasets including habitat and special management areas for effects and impact analyses.

Back to Top

How was the data set created?

  1. Where did the data come from?

    BLM District Offices, unpublished material, .

    Type of source media: onLine
    Source contribution:
    BLM District Offices

  2. What changes have been made?

    Date: 20130301 (change 1 of 1)
    Created Fire_History geodatabase with feature classes, attributes, and domains according to the Fire History data standard. 2. Populated FIRE_POLY feature class with historical fire perimeters (1918-2012) submitted by each District, and adjusted attributes as needed. Attribute completness varied greatly across the submissions, particularly for perimeters pre-1980. 3. Loaded 23 missing large fire perimeters from NWCC_Fire_History_2000_2012 layer and adjusted attributes. 4. Identified and removed true duplicates.

    Person responsible for change:
    Barbara W. Haney
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR97208

    503-808-2741 (voice)

Back to Top

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?


  2. How accurate are the geographic locations?


  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?


  5. How consistent are the relationships among the observations, including topology?

    FIRE PERIMETER POLYGONS (FIRE_POLY) Description: Instance of Fire group. Geometry: Polygons do not cover the landscape, nor do they cover all BLM lands continuously. In addition, there may be islands ("donut holes") of non-burned area surrounded by burned area. An individual fire may consist of multiple unattached polygons. Such polygon pieces should be stored as individual polygon records with common attribute values not as multi-part polygons. There are potentially many fires covering the same area in different years so there will be overlapping polygons. Topology: No topology enforced. Integration Requirements: None.

Back to Top

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access constraints: PUBLIC DATA: None, these data are considered public domain.
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 from 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 data may be updated by the BLM without notification. DATA STEWARD APPROVAL: Craig Goodell, state data steward for FIRE_POLY, approved the use of this dataset on March 16, 2017.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Management Specialist
    P.O Box 2965
    Portland, OR97208

    503-808-6340 (voice)
    503-808-6419 (FAX)
    Contact Instructions:
    contact instructions

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    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.

  4. How can I download or order the data?

    • Availability in digital form:

    • Data format:
      in format Arc GIS (version Feature Class) Winzip

    • Cost to order the data: Contact distributor.

    • Special instructions:

      Data are only available through the Oregon/Washington State office of the Bureau of Land Management.

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

    Arc GIS, Winzip

Back to Top

Who wrote the metadata?

Last modified: 20130425
Last reviewed: 20170320

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR97208

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
Hours of Service: 8:00-4:00
Contact Instructions:

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata(FGDC-STD-001-1998)

Back to Top