Burn Intensity for the 1994 Thunderbolt Fire within Boise National Forest, Idaho

Burn Intensity for the 1994 Thunderbolt Fire within Boise National Forest, Idaho

Frequently-asked questions:


What does this data set describe?

Title:
Burn Intensity for the 1994 Thunderbolt Fire within Boise National Forest, Idaho

Abstract:
This data set reflects fire intensity as measured by canopy scorch for the 1994 Thunderbolt Fire, Cascade Ranger District, Boise National Forest, Idaho.

Supplemental information:
Procedures_Used:
Field crews surveyed fire area (ground and air).  Islands < 40 acres usually not mapped.  Burn polygons drawn on paper copies 7 1/2 minute USGS topographical maps, then remanuscripted 1:24000 stable mylar.  Digitized Arc-Info RMSE .003, clean weed 10.

Reviews_Applied_to_Data:
Manuscripts compared with field maps to check for line and attribute accuracy.

  1. How should this data set be cited?

    Boise National Forest GIS staff, Unknown, Burn Intensity for the 1994 Thunderbolt Fire within Boise National Forest, Idaho: Boise National Forest GIS Staff, Boise, ID, USA.

    Online links:
  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -115.68816014
    East: -115.49810397
    North: 44.87519103
    South: 44.69444056

  3. What does it look like?

    http://insideidaho.org/data/BNF/image/thunfire_bnf_bnf.gif (GIF)
    Simple image of the data set at full extent

    Thumbnail image:

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

    Calendar date: 1994
    Currentness reference:
    ground condition

  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):
      • Point (90)
      • String (238)
      • GT-polygon composed of chains (91)
      • Node, planar graph (165)
      • Point (224)

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

      The grid coordinate system used is Universal Transverse Mercator

      Universal Transverse Mercator
      UTM zone number: 11
      Transverse Mercator projection parameters:
      Scale factor at central meridian: 0.999600
      Longitude of central meridian: -117.000000
      Latitude of projection origin: 0.000000
      False easting: 500000.000000
      False northing: 0.000000

      Planar coordinates are encoded using Coordinate Pair.
      Abscissae (x-coordinates) are specified to the nearest 1.
      Ordinates (y-coordinates) are specified to the nearest 1.
      Planar coordinates are specified in meters.

      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.
      The flattening of the ellipsoid used is 1/294.9786982.

  7. How does the data set describe geographic features?

    THUNFIRE.PAT
    Polygon attribute table, Thunderbolt Fire Fire Intensity (Source: Field mapping)

    -
    Polygon attribute table, Thunderbolt Fire Fire Intensity (Source: Field mapping)
                      

    Sequential unique whole numbers that are automatically generated.

    ACRES
    Acres calcualted from area (area / 4046.85) (Source: Calculated)
                      

    Coordinates defining the features.

    AREA
    Area of poly/region in square coverage units (Source: Computed)
                      

    Whole numbers that are automatically generated.

    BIS
    Burn Intensity, canopy scorch (Source: See narrative)
                      

    BIS (burn intensity), relative estimate of fire intensity as measured by canopy scorch. Generally areas > 40 acres mapped. Scorch canopy defined as fire killed needles and leaves that remain on trees or brush. U - Not Burned. Canopy not scorched. L - Low, < 50%. Canopy "green" with scattered scorched canopy areas. M - 51-100%, usually > 75%. Canopy "red", scattered black, green areas. H - 100%. Canopy completely consumed. Canopy black.

    BIS_INT
    Integer equivalent of bis, for use in GRID (Source: L=1, M=2, H=3, UB=99)
                      

    BIS (burn intensity), relative estimate of fire intensity as measured by canopy scorch. Generally areas > 40 acres mapped. Scorch canopy defined as fire killed needles and leaves that remain on trees or brush. U - Not Burned. Canopy not scorched. L - Low, < 50%. Canopy "green" with scattered scorched canopy areas. M - 51-100%, usually > 75%. Canopy "red", scattered black, green areas. H - 100%. Canopy completely consumed. Canopy black.

    DISS
    Item used to dissolve into perimeter (Source: user defined)
                      

    BIS (burn intensity), relative estimate of fire intensity as measured by canopy scorch. Generally areas > 40 acres mapped. Scorch canopy defined as fire killed needles and leaves that remain on trees or brush. U - Not Burned. Canopy not scorched. L - Low, < 50%. Canopy "green" with scattered scorched canopy areas. M - 51-100%, usually > 75%. Canopy "red", scattered black, green areas. H - 100%. Canopy completely consumed. Canopy black.

    PERIMETER
    Perimeter of poly/region in coverage units (Source: Computed)
                      

    Positive real numbers that are automatically generated.

    THUNFIRE#
    Internal feature number (Source: Computed)
                      

    Sequential unique whole numbers that are automatically generated.

    THUNFIRE-ID
    User-assigned feature number (Source: User-defined)
                      

    THUNFIRE.AAT
    Attribute table of THUNFIRE.AAT (Source: ARC/INFO)

    -
    Attribute table of TBIS. (Source: ARC/INFO)
                      

    Sequential unique whole numbers that are automatically generated.

    FNODE#
    Internal number of from-node (Source: Computed)
                      

    Coordinates defining the features.

    LENGTH
    Length of arc in coverage units (Source: Computed)
                      

    Positive real numbers that are automatically generated.

    LPOLY#
    Internal number of poly to left of arc (Source: Computed)
                      

    Positive real numbers that are automatically generated.

    RPOLY#
    Internal number of poly to right of arc (Source: Computed)
                      

    Sequential unique whole numbers that are automatically generated.

    THUNFIRE#
    Internal feature number (Source: Computed)
                      

    THUNFIRE-ID
    User-assigned feature number (Source: User-defined)
                      

    TNODE#
    Internal number of to-node (Source: Computed)
                      

    DISS
    Unknown (Source: Unknown)
                      

    BIS_INT
    Unknown (Source: Unknown)
                      

    BOLT_BI
    Unknown (Source: Unknown)
                      

    THUNFIRE.NAT
    Attribute table of THUNFIRE.NAT (Source: ARC/INFO)

    -
    Attribute table of TBIS. (Source: ARC/INFO)
                      

    Sequential unique whole numbers that are automatically generated.

    ARC#
    Unknown (Source: Unknown)
                      

    Coordinates defining the features.

    THUNFIRE#
    Internal feature number (Source: Computed)
                      

    THUNFIRE-ID
    User-assigned feature number (Source: User-defined)
                      

    Sequential unique whole numbers that are automatically generated.

    THUNFIRE-ID
    User-defined feature number. (Source: ESRI)
                      

    Entity and attribute overview:
    BIS (burn intensity), relative estimate of fire intensity as measured by canopy scorch. Generally areas > 40 acres mapped.  Scorch canopy defined as fire killed needles and leaves that remain on trees or brush.
    UB - canopy not scorched.
    L - Low, < 50%. Canopy "green" with scattered scorched canopy areas.
    M - 51-100%, usually > 75%. Canopy "red", scattered black, green areas.
    H - 100%.  Canopy completely consumed.  Canopy black.
    

    Entity and attribute detail citation:
    Not Available
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)

    • Boise National Forest GIS staff

  2. Who also contributed to the data set?

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

    Diane McConnaughey
    Boise National Forest GIS Staff
    GIS Specialist
    1249 South Vinnell Way
    Suite 200
    
    Boise, ID 83709
    USA

    (208) 373-4247 (voice)
    dmcconnaughey@fs.fed.us
Back to Top

Why was the data set created?

The data are intended to assist efforts surrounding broad-scale forest planning for analysis in fire-recovery: soil stabilization, reestablishing vegetation, and protection of other resources such as wildlife, riparian habitat, water quality, fisheries and timber. These data should be displayed and analyzed at scales appropriate for 1:24,000-scale data. No responsibility is assumed by the Boise National Forest GIS Staff in the use of these data.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 19941021 (change 1 of 58)
    DTHOM IMPORT COVER TBOLT TBOLT

    Date: 19941021 (change 2 of 58)
    DTHOM RENAME TBOLT TEMP

    Date: 19941021 (change 3 of 58)
    DTHOM CLEAN TEMP TBOLT 10 10 POLY

    Date: 19941021 (change 4 of 58)
    DTHOM ARCEDIT /PROJECTS/BNF/TBOLT

    Date: 19941021 (change 5 of 58)
    DTHOM BUILD TBOLT POLY

    Date: 19941021 (change 6 of 58)
    DTHOM CREATELABELS TBOLT

    Date: 19941022 (change 7 of 58)
    DTHOM ARCEDIT /PROJECTS/BNF/TBOLT

    Date: 19941024 (change 8 of 58)
    DTHOM EXPORT COVER TBOLT TBOLT

    Date: 19941024 (change 9 of 58)
    DTHOM ARCEDIT /PROJECTS/BNF/TBOLT

    Date: 19941024 (change 10 of 58)
    DTHOM BUILD TBOLT POLY

    Date: 19941024 (change 11 of 58)
    DTHOM IDEDIT TBOLT POLY

    Date: 19941024 (change 12 of 58)
    IMPORT COVER TBOLT TBOLT

    Date: 19941025 (change 13 of 58)
    COPY TBOLT THUNDER/TBOLT

    Date: 19941026 (change 14 of 58)
    EXPORT COVER TBOLT TBOLT

    Date: 19941027 (change 15 of 58)
    RENAME TBOLT TBINT

    Date: 19941027 (change 16 of 58)
    ARCEDIT /GRD/XXSPACE/THUNDER/TBINT

    Date: 19941027 (change 17 of 58)
    BUILD TBINT LINE

    Date: 19941027 (change 18 of 58)
    BUILD TBINT NODE

    Date: 19941027 (change 19 of 58)
    IDEDIT TBINT LINE

    Date: 19941027 (change 20 of 58)
    BUILD TBINT POLY

    Date: 19941027 (change 21 of 58)
    ARCEDIT /GRD/XXSPACE/THUNDER/TBINT

    Date: 19941027 (change 22 of 58)
    ARCEDIT /GRD/XXSPACE/THUNDER/TBINT

    Date: 19941027 (change 23 of 58)
    BUILD TBINT LINE

    Date: 19941027 (change 24 of 58)
    BUILD TBINT NODE

    Date: 19941027 (change 25 of 58)
    IDEDIT TBINT LINE

    Date: 19941027 (change 26 of 58)
    BUILD TBINT POLY

    Date: 19941027 (change 27 of 58)
    IDEDIT TBINT POLY

    Date: 19941027 (change 28 of 58)
    ARCEDIT /GRD/XXSPACE/THUNDER/TBINT

    Date: 19941028 (change 29 of 58)
    EXPORT COVER TBINT TBINT

    Date: 19941030 (change 30 of 58)
    EXPORT COVER TBINT TBINT

    Date: 19941103 (change 31 of 58)
    COPY /GRD/XXSPACE/THUNDER/TBINT TBINT

    Date: 19941104 (change 32 of 58)
    EXPORT COVER TBINT TBINT

    Date: 19941130 (change 33 of 58)
    EXPORT COVER TBINT THBIS.E00

    Date: 19941209 (change 34 of 58)
    EXPORT COVER /GRD/XXSPACE/CASCADE/TBINT /BNF1/BAT_EXPORTS/TBINT

    Date: 19950420 (change 35 of 58)
    EXTERNALALL

    Date: 19950420 (change 36 of 58)
    EXTERNALALL

    Date: 19950420 (change 37 of 58)
    EXTERNALALL

    Date: 19950420 (change 38 of 58)
    EXTERNALALL

    Date: 19950512 (change 39 of 58)
    EXTERNALALL

    Date: 19950512 (change 40 of 58)
    EXTERNALALL

    Date: 19950512 (change 41 of 58)
    EXTERNALALL

    Date: 19950512 (change 42 of 58)
    EXTERNALALL

    Date: 19950531 (change 43 of 58)
    EXTERNALALL

    Date: 19950531 (change 44 of 58)
    EXTERNALALL

    Date: 19950609 (change 45 of 58)
    COPY TBINT /FIRE2/94FIRES/TBINT

    Date: 19950613 (change 46 of 58)
    RENAME TBINT TBIS

    Date: 19960429 (change 47 of 58)
    DMCCONNA   DOCUMENT TBIS CREATE DMCCONNA

    Date: 19960429 (change 48 of 58)
    DMCCONNA EXPORT COVER TBIS /WRK/COV_DEV/TBIS NONE

    Date: 19960507 (change 49 of 58)
    DMCCONNA  EXPORT COVER /FIRE2/94FIRES/TBIS TBIS

    Date: 19960531 (change 50 of 58)
    DMCCONNA EXPORT COVER /FIRE2/94FIRES/TBIS TIBS NONE

    Date: 19970708 (change 51 of 58)
    EXTERNALALL

    Date: 19970715 (change 52 of 58)
    DMCCONNA IMPORT COVER TBIS TBIS

    Date: 19980105 (change 53 of 58)
    DMCCONNA EXPORT COVER /FSFILES/REF/LIBRARY/GIS/BOISE/FIRE/TBIS TBIS

    Date: 19980105 (change 54 of 58)
    DMCCONNA EXPORT COVER /FSFILES/REF/LIBRARY/GIS/BOISE/FIRE/TBIS TBIS

    Date: 19980925 (change 55 of 58)
    DMCCONNA COPY TBIS /FSFILES/OFFICE/GISDEV/BNFDEV/TBIS

    Date: 19990525 (change 56 of 58)
    DMCCONNA COPY TBIS /FSFILES/REF/LIBRARY/GIS/BOISE/FIRE/TBOLT

    Date: 20000707 (change 57 of 58)
    PROJECTCOPY COVER BBEXPFOR COVER THUNFIRE
    
    The original ArcInfo coverage did not have a projection defined.
    

    Person responsible for change:
    Lily Wai
    University of Idaho Library
    Head of Government Documents
    University of Idaho Library
    Moscow, ID 83844-2350
    USA

    208-885-6344 (voice)
    208-885-6817 (FAX)
    lwai@uidaho.edu
    Hours of Service: 9:00 am - 5:00 pm (Pacific Time), Monday - Friday

    Date: 20000707 (change 58 of 58)
    EXPORT COVER THUNFIRE THUNFIRE_BNF_BNF.E00
    
    The orginal coverage contributed by Diane McConnaughey was imported into ARC/INFO, renamed, and exported.  The file was then compressed using GZIP.
    
    Metadata included with the original coverage (created using DOCUMENT.AML) was imported.  If the metadata was not FGDC compliant, it was updated to be compliant.
    

    Person responsible for change:
    Bruce Godfrey
    University of Idaho Library
    GIS Specialist
    PO Box 442350
    Moscow, ID 83844-2350
    USA

    208-885-6463 (voice)
    208-885-6817 (FAX)
    bgodfrey@uidaho.edu

Back to Top

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

  1. How well have the observations been checked?

    See Entity_Attribute_Information

  2. How accurate are the geographic locations?

    Unknown

  3. How accurate are the heights or depths?

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

    Unknown

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

    Polygon and chain-node topology present.

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: None
Use constraints:
None

Distributor 1 of 1

  1. Who distributes the data set?

    Bruce Godfrey
    University of Idaho Library
    GIS Specialist
    PO Box 442350
    Moscow, ID 83844-2350
    USA

    208-885-6463 (voice)
    208-885-6817 (FAX)
    bgodfrey@uidaho.edu

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    Although these data have been processed successfully on a computer system at the University of Idaho Library, no warranty, expressed or implied, is made regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty.

  4. How can I download or order the data?

  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?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 19960429
Last reviewed: 20040527

Metadata author:
Diane McConnaughey
Boise National Forest GIS Staff
GIS Specialist
1249 South Vinnell Way
Suite 200
Boise, ID 83709
USA

(208) 373-4247 (voice)
dmcconnaughey@fs.fed.us

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

Metadata extensions used:
  • http://www.esri.com/metadata/esriprof80.html

  • Back to Top