S_R06.FireHistoryPl

Metadata also available as

Frequently-anticipated questions:

What does this data set describe?

Title: S_R06.FireHistoryPl
Abstract:
Fire History polygons represent the final mapped wildfire perimeter. These data are maintained at the Forest / District level to track the area affected by fire.
Supplemental_Information:
Fire History polygons represent the area which the wildfires burned. Wildfire data is collected and maintained at the Forest and or District level to aid in tracking the areas affected by fire. This data set was compiled by requesting each National Forests individual fire history coverage data, then standardizing the data according to the Forest Service National Data Dictionary Standards, Fire Management Theme, Fire History Layer, dated June 30, 2003. The data collected is from the years 780 until present. Two National Forests, the Olympic and Mt. Baker-Snoqualmie, had scientists from their PNW Labs do extensive research using carbon dating techniques to determine fire years for pre 1800 fire perimeters. The Gifford Pinchot and Siuslaw National Forests did not have Fire History spatial data of fire boundaries at the time this data set was created. The majority of the forests collected their data using UTM Coordinates in Zone 10. Those forests using UTM Zone 11 was MAL, UMA, and WAW. The forests who used TM Coordinates were GIP, WIN, COL, and WEN. The only forest using LCC Coordinates was OKA. Initially all forests used NAD1927 datum. Beginning in 2007 data maintenance procedures follow the R6 Fire History edit guide and are annually coordinated through Fire and Aviation Management / Data Resources Management at the Regional level.
  1. How should this data set be cited?

    Data Resource Management/Fire a, Pacific Northwest Region, Forest Servic, 20090624, S_R06.FireHistoryPl.

    Online Links:

    • Server=oracle-idb.pdx; Service=5151; User=s_r06$design; Version=SDE.DEFAULT

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -124.948188
    East_Bounding_Coordinate: -115.499410
    North_Bounding_Coordinate: 49.092291
    South_Bounding_Coordinate: 41.874934

  3. What does it look like?

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

    Beginning_Date: Data begins with 780, for those carbon dated, otherwise the beginning year is 1800.
    Ending_Date: 2008
    Currentness_Reference:
    Dates are compiled; wildfire ignition was observed for years after 1800, and were determined scientifically for years before 1800.

  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):

      • G-polygon (4835)

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

      The map projection used is Albers Conical Equal Area.

      Projection parameters:
      Standard_Parallel: 43.000000
      Standard_Parallel: 48.000000
      Longitude_of_Central_Meridian: -120.000000
      Latitude_of_Projection_Origin: 34.000000
      False_Easting: 600000.000000
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.100000
      Ordinates (y-coordinates) are specified to the nearest 0.100000
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Resolution: 1.000000
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    S_R06.FireHistoryPl
    INFO Polygon Attribute Table (Source: Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer)

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    NIFMID_CN
    Control Number generated in Oracle to uniquely identify each fire across all Forest Service Units. These control numbers are only generated, by FIRESTAT, for fires reported to the NIFMID database in Kansas City. Other fires included in this cover, but not reported through FIRESTAT, will have a null value for this field. (Source: FSH 5109.14, Chapter 30(34); Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer.)

    ValueDefinition
    Generated Unique CodeA unique code generated by Oracle or a null value if the fire was not reported to the FIRESTAT database. This Field is populated from the FIRESTAT database. (Example: 68829)

    NIFMID_LNK
    Unique code generated by concatenating data fields as downloaded from NIFMID, the National Fire Occurance Database in Kansas City. FIRESTAT_LNK is the matching field created by R6 DRM for linking to NIFMID. (Source: FSH 5109.14, Chapter 30(34); Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer.)

    ValueDefinition
    17 character code, AAARRFFYYYY######, where AAA is the Agency (taken from Protecting_Agency); RR is the Forest Service Region (taken from Reporting_FS_Region); FF is the Forest Number (taken from Reporting_FS_Unit); YYYY is the Fire Discovery Year (taken from Discovery_Date); and ###### is the Local_Number (taken from Fire_Number); with leading zero's to make it a 6 character, zero filled field. (Example: USF06112006000022)All parts of this code are right justified and zero filled. A unique 17 character code composed by concatenating the following fields from NIFMID, the National Fire Occurrence Database in Kansas City. Where AAA is Protecting_Agency, RR is Reporting_FS_Region, FF is Reporting_FS_Unit, YYYY is the year taken from Discovery_Date and ###### is the Fire_Number with leading zero's added to make it a 6 character, zero filled field.

    FIRE_NAME
    Final name of the fire, as stated in FSH 5109.14 "Do no include the word "Fire" as part of the name". Name may contain text and/or numbers. Example: Big Ridge (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer, FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29, in the Local Information found in the top portion of the Individual Wildland Fire Report form.)

    FIRE_DAY
    The day of the month the geographic data represents. (Example: 07) (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, taken from the Discovery_Date, found in the Occurrence Block on Form FS-5100-29, Individual Wildland Fire Report.)

    ValueDefinition
    01-31Double digit number representing the day of the month.

    FIRE_MONTH
    The month the geographic data represents. (Example: 09) (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, taken from the Discovery_Date, found in the Occurrence Block on Form FS-5100-29, Individual Wildland Fire Report.)

    ValueDefinition
    01-12Double digit number representing the month of the year.

    FIRE_YEAR
    The fire discovery year the geographic data represents. (Example: 2006) (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, taken from the Discovery_Date, found in the Occurrence Block on Form FS-5100-29, Individual Wildland Fire Report.)

    DATA_SOURCE_TEXT
    Describes the source of spatial data collection used. (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer.)

    ValueDefinition
    GPSGlobal Positioning System
    IRInfrared
    HDHand Drawn
    PIPhoto Interpretation
    OTHER:IKONOS imagery from 07/07/00Describe the source data. Be consistent and as specific as possible when describing OTHER data sources.
    GPS-IDT 
    GPS-IMT 
    MAP 
    MAP_PHOTO 
    MAP_PHOTO_GPS 
    OTHER:BIFZBurns Interagency Fire Zone (compiled by BLM)
    OTHER:BUFIREPTSBurns BLM District Fire Points
    OTHER:EMIEmigrant Creek Ranger District Fire Points (compiled by BLM)
    OTHER:KCFASTUSFS KCFAST National Fire Database (compiled by BLM)
    OTHER:MAFMalheur National Forest (compiled by BLM)
    OTHER:NIFMIDKCFAST National Fire Database (compiled by USFS)
    OTHER:NIFMID_BLMBLM NIFMID National Fire Database
    OTHER:ODFOregon Department of Forestry (compiled by BLM)
    OTHER:PCHAPCHA Database
    OTHER:PCHC 
    OTHER:SMSnow Mountain Ranger District fire points (compiled by BLM)
    OTHER:STATEState of Oregon (compiled by BLM)
    OTHER:REM 
    OTHER:Scientific Used Carbon DatingPNW Scientists used carbon dating techniques to determine year burned.

    COST
    Cost of suppression to the nearest dollar. $2,000,000 was spent on fire. (example: 2000000) (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29, found in the Description Block on the Individual Wildland Fire Report form.)

    LOCAL_NUMBER
    The Fire Number, required in NIFMID, is a three digit number assigned to the fire by the Forest Supervisor's Office. (Example: 090) (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29.)

    CAUSE
    Use Coding for "Statistical Cause" code, a one digit number (numbers 1-9) that identifies the broad statistical cause for the fire. (Source: Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Occurrence Block on the Individual Wildland Fire Report form.)

    ValueDefinition
    1Lightning
    2Equipment Use
    3Smoking
    4Campfire
    5Debris Burning
    6Railroad
    7Arson
    8Children
    9Miscellaneous

    REPORTED_ACRES
    Final acreage as reported on the final Incident Command System Status Report 209. (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29, found in the Description Block of the Individual Wildland Fire Report form.)

    If the fire involves less than one acre, report to the nearest tenth of an acre. If the fire involves one acre or more, report to the nearest whole acre. The minimum fire size is 0.1 acres and the maximum acres 999,999,999.

    SIZE_CLASS
    A one-letter code to categorize fires into size classes. Classification is based on the total acres burned, the final area burned by fire. Use coding as defined in the Fireline Handbook, single alpha characters A-G. (Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).)

    ValueDefinition
    A0 to .25 Acres
    B.26 to 9.9 Acres
    C10 to 99.9 Acres
    D100 to 299.9 Acres
    E300 to 999.9 Acres
    F1000 to 4999.9 Acres
    G5000+ Acres

    AGENCY
    Protecting Agency of Record at Origin legally responsible to provide primary protection for the land on which the fire started. (Source: FSH 5109.14 Individual Fire Report Handbook, found in the Identification Block on Form FS-5100-29, Individual Wildland Fire Report.)

    ValueDefinition
    AFSDepartment of Defense, Air Force
    ARMDepartment of Defense, Army
    BIAUSDI, Bureau of Indian Affairs
    BLMUSDI, Bureau of Land Management
    DNRWashington Department of Natural Resources (State)
    FWSUSDI, Fish and Wildlife Services
    IDState Lands in Idaho
    NAVDepartment of Defense, Navy
    NOPNo Protection
    NPSUSDI, National Park Service
    ODFOregon Department of Forestry (State)
    ORState Lands in Oregon
    OTHOther Federal Agency Land
    PVTPrivate Land
    FSUSDA, Forest Service
    WAState Lands in Washington

    COMMENTS
    Open text field for additional information. (Source: Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer.)

    R6_FID
    Unique Forest Identification Code. (Source: This field is open for use by individual forests, which have a unique number, necessary to link Fire History data to local forest records.)

    NIFMID_LNK_OLD
    This field is a copy of the original NIFMID_LNK field, as it was originally created, during the standardization process. (Source: This field was created by DRM. It is being kept to track when the NIFMID_LNK is changed, and will probably go away when it no longer serves any usefulness.)

    LINKFLAG
    This field was created during the standardization process, for quality checking purposes, to determine the quality of the data and how well its linking ability is with the NIFMID data at Kansas City. (Source: This field was created by DRM, and will probably go away when it no longer serves any usefulness. The initial use has been checking the link between the point fire history dataset and NIFMID data in Kansas City.)

    ValueDefinition
    DBL LINKHas duplicate NIFMID_LNK numbers in KC and has two points in the FireHistory dataset, but different spatial locations. Points appear on different Districts, fire numbers may be District fire numbers, rather then S.O. fire numbers, as used in KC.
    DUPSame point appears to be entered in KC two or three times. Spatial locations in FireHistory are close in proximity, making it appear these are duplicate points and only one should remain.
    GOODHas a NIFMID_LNK number in FireHistory dataset that matches with KC NIFMID data. All data appears to match between spatial dataset and KC database.
    GOOD1 DATEData from FireHistory only matches on the date field with KC NIFMID data, has not other data to match to.
    GOOD1, GOOD2, GOOD3, GOOD4, GOOD5, GOOD6The number (after GOOD) indicates how many item fields, from FireHistory, match with KC NIFMID data. Item fields beyond the NIFMID_LNK and FIRESTAT_LNK, that were used to match data on, was the FIRE_NAME to FIRE_NAME, COST to FIRE_COST_IN_DOLLARS, SIZE_CLASS to FIRE_SIZE_CLASS, REPORTED_ACRES to TOTAL_ACRES_BURNED, CAUSE to STATISTICAL_CAUSE, and FIRE_YEAR, FIRE_MONTH, FIRE_DAY to either IGNITION_DATE or DISCOVERY_DATE. The DISCOVERY_DATE in KC NIFMID database matched 90% of the time, if it did not match, then IGNITION_DATE matched the date in FireHistory.
    NO DATEFireHistory data has FIRE_YEAR, but no month and day, plus has other item fields to match on with good matches between FireHistory and KC NIFMID data.
    NO LINKFireHistory does not have a fire number, or correct S.O. fire number in the NIFMID_LNK field to use for a match with FIRESTAT_LNK field in the KC NIFMID data. May have other data in other item fields to match on, but no enough to make a good link with KC.
    NON FS DUPItem in FireHistory appears to be a duplicate, and the AGENCY field is not coded USF. Spatial locations in FireHistory are close in proximity, making it appear these are duplicate points and only one should remain.
    NON FSThe AGENCY field in FireHistory is not coded USF.
    NOT IN KCItem has a spatial location in FireHistory, as well as attribute data, but not found in KC NIFMID database.
    YEAR ONLYFireHistory spatial data only has FIRE_YEAR. Some spatial locations may look close to match KC NIFMID data. Could also have data in SIZE_CLASS field, but not enough data in other fields to make a good match with KC.
    PRIOR KCFireHistory spatial data with FIRE_YEAR before 1970. Kansas City NIFMID database only has data from 1970 to present.

    REV_DATE
    This is the date of feature creation or latest update. (Source: This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html.)

    DATA_SOURCE
    The Data Source is the source of the geographic position of the arc, polygon, or point. Each Data Source code description contains information on the data used to derive features. (Source: This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.)

    ValueDefinition
    01Original CFF
    02GPS - Uncorrected Data
    03GPS - Differentially Corrected Data
    04GPS Survey Grade and Sub-meter
    05Resurvey Plat
    06Photogrammetric Compilation
    07Digitized From Hardcopy PBS/SEQ
    08Digitized From Hardcopy Orthophoto quad
    09Automated Lands Project (ALP)
    20Digitized Other
    21Geographic Coordinate Database (GCDB)
    22Other Cadastral Information
    23Other Agency Digital
    24Other
    30Remote Sensing Data - Base Level
    31Remote Sensing Data - Mid Level
    32Remote Sensing Data - Broad Level
    33Remote Sensing Data - National Level

    ACCURACY
    This is the accuracy of the spatial location of the data. The expected difference between feature and real world object location. (Source: This is not a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field.)

    SHAPE
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    UNIT
    Four digit number code for Region and Forest. Region code is a two digit number code of the Forest Service region, of which the reporting unit belongs. Forest code is a two digit forest number that identifies the reporting forest unit. (Example: 0609) (Source: Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29)

    SHAPE.AREA
    Feature geometry. (Source: ESRI)

    SHAPE.LEN
    Feature geometry. (Source: ESRI)

    S_R06.FireHistoryPl_NIFMID_J
    This is a table join. Joining tables is appending the fields of one table to those of another through an attribute or field common to both tables. A join is usually used to attach more attributes to the attribute table of a geographic layer. This join is joining the attribute fields from the polygon spatial data, table S_R06.FireHistoryPl, with the attribute fields from the NIFMID database, table S_R06.Fire_NIFMID, by using the field common to both, NIFMID_LNK from the fire NIFMID database table and FIRESTAT_LNK from the Fire History point spatial data table. (Source: If you need additional information on table joins, use ArcMap Help, About Joining Attribute Tables.)

    Entity_and_Attribute_Overview:
    TWO PROCESS STEP SUMMARIES FOLLOW HERE, ONE FOR 2005 FOLLOWED BY THE UPDATE PROCESS OF 2007.
    METADATA SUMMARY OF ATTRIBUTE CODING USED BY DST DURING THE INITIAL FIRE HISTORY STANDARDIZATION PROCESS IN 2005.
    The black normal font text in this document is taken from the GIS Core Data Dictionary, June 30, 2003. The (text inside parenthesis) indicates where, why and what changes were made during the standardization process by DST, which is not documented in the GIS Core Data Dictionary standards.
    NIFMID_CN - Control number generated in Oracle to uniquely identify each fire across all Forest Service Units. These control numbers are only generated by FIRESTAT, for fires reported to the NIFMID database in Kansas City. Other fires included in this cover will have a null value for this field. Value Description: A unique code is generated by Oracle or a null value if the fire was not reported through FIRE STAT, to the NIFMID database. This field is populated from the Fire Stat database. This number can be found in the NIFMID Table under the column named FIRE_ID.
    NIFMID_LNK - A unique 17 character code composed of concatenating Agency, unit, subunit, discovery year and fire number as downloaded from the National Fire Occurrence Database in Kansas City via KCFast. Value Description: Concatenation of Agency, unit, subunit, discovery year and fire number. These standards are from the KCFast application. Code example, AAARRFFYYYY######, where AAA is the Agency; RR is the Forest Service Region; FF is the Forest Number; YYYY is the Fire Discovery Year; and ###### is the Fire Number with leading zero's to make it a 6 character, zero filled field. (Example: USF06012006000022). All parts of this code are right justified and zero filled. This code is used as a link between SDE and the NIFMID database in Kansas City. FIRESTAT_LNK, found in the table S_R06.FIRE_NIFMID, is the linking field composed by concatenating the following fields from NIFMID, the National Fire Occurrence Database in Kansas City. Where AAA is PROTECTING_AGENCY, RR is REPORTING_FS_REGION, FF is REPORTING_FS_UNIT, YYYY is the year taken from DISCOVERY_DATE and ###### is the FIRE_NUMBER with leading zero's added to make it a 6 character, zero filled field. (According to direction given to DST by Dale Guenther, where this field is null, it will be populated using an AML created by DST. The AML will generate this field, using the covers item fields, by concatenating AGENCY, unit, subunit, FIRE_YEAR, and LOCAL_NUMBER. If any of these item fields are null, they will be zero filled.)
    FIRE_NAME - The final name of the fire. Value Description: Name may contain text and/or numbers. (Because the FIRE_NAME was in all caps, mixed upper and lower case, had many symbols that could create problems within ArcGIS or in databases, this field was standardized. The AML used by DST contains a "Fix FIRE_NAME Routine" where it puts the fire name in proper case, rather then all Capitol letters. It removes any symbols like # & " _ . / from the fire name. The routine will also drop the word "Fire" from any fire name, as stated in FSH 5109.14 "Do not include the word "Fire" as part of the name", (e.g. Bear Fire would be Bear). Where FIRE_NAME is left blank, the field will be populated with "Unknown". Some examples of how names were changed follow below: )
    FROM TO Eagle Fire Eagle #456 456 Crossing #5 Crossing 5 Blue Lake II Blue Lake 2 Major_Creek_2 Major Creek 2 LONESOME/MCPINE Lonesome-McPine "Avery" Avery FIRE #450 Fire 450 R&R FIRE R-R MCDONALD RIDGE McDonald Ridge Big One 1&2 Big One 1-2 COTTON-BEAVER CREEK Cotton-Beaver Creek A. Dean A Dean B. C. Fire BC Meadow Cr. Meadow Creek Snowshoe Sp. Snowshoe Spring John's Rdg. John's Ridge
    FIRE_DAY - The day of the month that the geographic data represents. Value Description: Date that the data represents. Day must be zero-filled. If only the year is known, enter only the year and note the source in the comments field. (According to direction given to DST by Dale Guenther, this field can not be 00. If only the Month and Year is known enter 01 for the FIRE_DAY. If only the FIRE_YEAR is known leave this field blank.)
    FIRE_MONTH - The month that the geographic data represents. Value Description: Date that the data represents. Month must be zero-filled. If only the year is known, enter only the year and note the source in the comments field. (According to direction given to DST by Dale Guenther, this field can not be 00. If only the Day and Year is known enter 01 for the FIRE_MONTH. If only the FIRE_YEAR is known leave this field blank.)
    FIRE_YEAR - The year that the geographic data represents. Value Description: Date that the data represents. If only the year is known, enter only the year and note the source in the comments field. (According to direction given to DST by Dale Guenther, where this field had values like, 18yy, 18xx, or 19??, DST was instructed to use 1850 or 1900 with the comment "Exact fire year unknown", if there was room in the COMMENTS field.)
    LOCAL_NUMBER - It is important to use the FIRE_NUMBER, that was used in NIFMID, on the fire report for this field. This is a confusing field, because the GIS Data Dictionary does not give a good definition, and this is the field used to create the NIFMID_LNK. The FIRE_NUMBER, required in NIFMID, is a three digit number assigned to the fire by the Forest Supervisor's Office. Many NIFMID_LNK numbers do not match, or link, with the NIFMID database because this number was incorrect.
    (LOCAL_NUMBER - Clarification of LOCAL_NUMBER and the Fire Number used as the last 6 characters of the NIFMID_LNK. DST asked for clarification, because one is a 6 character field that is zero filled and LOCAL_NUMBER is a local identification number that is an 8 character field.) (Joe Frost gave this explanation. This issue comes up all the time and it is confusing. The NIFMID_LNK is the "smart key" used to link polygon data to the National Fire Statistics Database by using common information in both, the combination of AGENCY, Unit (region number), Sub-unit (forest number), FIRE_YEAR (discovery year), and Fire Number, provide a unique combination of values that will allow linking Polygon and Tabular data. If you do not have this basic information for each polygon then it is likely the fire which the polygon represents was not a statistical fire occurrence for a federal agency.) (Is the Fire Number the same as LOCAL_NUMBER? For the most part yes, but not always, the LOCAL_NUMBER leaves room for more flexibility and is defined as character, which allows the use of alpha numeric combinations, so the LOCAL_NUMBER can contain more information like which unit (District (D1), Supervisors Office (SO), etc.) issued the number. Ninety-eight percent of the time the LOCAL_NUMBER will match the Fire Number (I.E. local number SO-001 will equal fire number 000001)). (All statistical fire occurrences that are entered into the National Statistics Database must have a Fire Number assigned by the reporting unit. The LOCAL_NUMBER is not recorded in the National Fire Statistics Database and is for local use. The inclusion of the LOCAL_NUMBER in the National Data Standard, as an optional item, was to facilitate local linking of the polygon information to local tabular data. The LOCAL_NUMBER was requested by Region 8 because of the numbering system which they use on some units.) (Shouldn't the fields be the same length requirement in NIFMID_LNK (6 places) and LOCAL_NUMBER (8 places)? No, because there is only an assumed (not defined) relationship between the two fields. The Fire Number used in the NIFMID_LNK must be numeric and is required in the Fire Statistics Database. The LOCAL_NUMBER can contain a mix of alpha and numeric characters and is not required in the spatial data standard or in the Fire Statistics Database.)
    REPORTED_ACRES - Acres reported are the final acreage, as reported, on the final Incident Command System Status Report 209. (According to direction given to DST by Dale Guenther, where this field is blank, use GIS to calculate acres in the fire polygon cover. The formula used was AREA multiplied by the acres conversion factor of 0.0002471054.)
    SIZE_CLASS - Use coding as defined in the Fireline Handbook, FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). Value Description: A is 0 to .25 Acres, B is .26 to 9.9 Acres, C is 10 to 99.9 Acres, D is 100 to 299.9 Acres, E is 300 to 999.9 Acres, F is 1000 to 4999.9 Acres and G is 5000+ Acres. (According to direction given to DST by Dale Guenther, where this field is blank, use GIS to calculate SIZE_CLASS, using REPORTED_ACRES.)
    AGENCY - Use coding found in Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29. Handbook definition for this field states, "Enter the letter code of the agency legally responsible to provide primary protection for the land on which the fire started." (Because there was no code for DNR - Department of Natural Resources, and Oregon State Forestry, DST asked Dale Guenther for coding. DST was instructed to "Please make a new field, label as State." DST initially coded the State fires as DNR for Washington State fires and STA for Oregon fires. DST revisited this coding issue and has learned that State fires in Oregon should most likely be coded ODF - Oregon Department of Forestry. DST has asked Dale Guenther to make a determination if DNR and ODF are the best codes, and to add these codes to the GIS Core Data Dictionary. DST received direction from Dale, on March 23, 2006, that ODF would be the appropriate acronym. Dale said he would work with Joe Frost to get these changes added to the Data Dictionary.)
    R6_FID - Unique Forest Identification Code. This field is open for use by individual forests, which have a unique number, necessary to link Fire History data to local forest records.
    THESE WERE THE EDIT/UPDATE PROCESS STEPS USED BY DST DURING THE 2007 MAJOR UPDATE CYCLE.
    The Fire History, points and polygons, spatial data needs to link to the NIFMID database in Kansas City. Currently only points are in the Kansas City NIFMID database, but the polygon spatial data should contain the same NIFMID_LNK, as the points for linking purposes between SDE and NIFMID.
    THE FIRST STEP, was to quality check all updates to assure attribute data conforms to the data standards. Verify, at minimum, all mandatory item fields contain data. Those fields are NIFMID_CN, NIFMID_LNK, FIRE_NAME, FIRE_DAY, FIRE_MONTH, FIRE_YEAR, and DATA_SOURCE. All updates will be in ALBERS, NAD83 projection and contain the standardized items as listed in the FS National GIS Data Dictionary for the INFO attribute tables as shown below.
    NIFMID_CN NIFMID_LNK FIRE_NAME FIRE_DAY FIRE_MONTH FIRE_YEAR DATA_SOURCE COST LOCAL_NUMBER CAUSE REPORTED_ACRES SIZE_CLASS AGENCY COMMENTS R6_FID
    NIFMID_LNK - where this field was null it was populated by concatenating the covers item fields, AGENCY, unit, subunit, FIRE_YEAR, and LOCAL_NUMBER. If any of these item fields are null, they were zero filled.
    FIRE_NAME - Where data was available each individual fire making up a "Fire Complex", the name of the complex was identified in the COMMENTS field of each fire involved in that complex with a comment like " XYZ Complex fire". The word "Fire" was dropped from any fire name. Where the FIRE_NAME was in all caps, mixed upper and lower case, or had many different symbols, this field was standardized. All the fire names were put in proper case, and any symbols like # & " _ . / were removed from the fire name. The only "symbol" allowed is a hyphen or dash. Where FIRE_NAME was left blank, for fire perimeters, the field was populated with "Unknown".
    FIRE_DAY - Where this field was not a two digit number, a preceding zero was added to the one digit number. A Domain was created to set allowable values for attributes in this field.
    FIRE_MONTH - Where this field was not a two digit number, a preceding zero was added to the one digit number. A Domain was created to set allowable values for attributes in this field.
    CAUSE - A Domain was created to set allowable values for attributes in this field.
    REPORTED_ACRES - Where this field was blank, GIS was used to calculate acres using the fire polygons. Where acres were 0.01 through 0.09 the zero preceding the decimal point was dropped (example: 0.01 changed to 0.1). The formula used is AREA multiplied by the acres conversion factor of 0.0002471054.
    SIZE_CLASS - Where this field was blank, used GIS to calculate SIZE_CLASS, using REPORTED_ACRES. A Domain was created to set allowable values for attributes in this field.
    AGENCY - Dale Guenther approved the code for Washington Department of Natural Resources as DNR, and Oregon Department of Forestry as ODF. Dale said he would get these changes added to the Data Dictionary. The codes used in the fire history points and polygon spatial data in SDE, are inclusive of all codes. A Domain was created to set allowable values for attributes in this field.
    R6_FID - This field is open for use by individual forests, which have a unique number, necessary to link Fire History data to local forest records. IMPORTANT NOTE: The item field UNIT needs to be added to the FireHistoryPl feature class in SDE. Until this happens, the UNIT code is being held in the R6_FID field temporarily, where it did not contain any forest data.
    A "template" geodatabase was created, of each forest, to load their data in. This assured it was all in the standardized format, proper structure of the corporate feature data set, and also was to keep each forests updates separate to ease in the final update process to the existing data in SDE.
    FIRST a File of the Database Structure was Created - From ArcCatalog, expand the Database Connections folder. Make a connection to SDE in Portland Data Center. Find the feature data set S_R06.FireManagement, Right click on it and choose Export > XML Workspace Document. Select Schema Only under "What do you want to export:", fill in the location and file name under "Specify the output XML file:", uncheck "Export Metadata", select Next. In the window under, "Choose which items you want to export", make sure only the Include box is checked for S_R06.FireHistoryPl and S_R06.FireHistoryPt, now click Finish. Right click on the SDE connection you made earlier, and choose Disconnect. Expand the local C:\ drive file directory and navigate to where you created the .xml file, you should see the file you just created. This file is used when creating the "empty template" geodatabase.
    SECOND a Personal Geodatabase for Holding Updates was Created - Right click on folder where Personal Geodatabase will be created, choose New > Personal Geodatabase, rename geodatabase, (example: firehistory_update_FFF_YYYY.mdb, where FFF equals the forest's three letter abbreviation and YYYY the year the update is current to. In cases where the forests have been combined, like OKA/WEN, it would be firehistory_update_FFF_FFF_YYYY.mdb. If there are updates that span 2003-2006, the year entered would be 2006.)
    Next, the structure of the database is added by importing the XML file created earlier. Right click on personal geodatabase just created, choose Import > XML Workspace Document, when Import XML Workspace Document window opens, leave Data checked and navigate to the .XML file created earlier, in the "Specify the XML source to import:" block, select Next and Finish. Refresh folder containing the firehistory_update.mdb, expand the folder and the firehistory_update.mdb geodatabase. There should now be a feature data set FireManagement, which contains two feature classes FireHistoryPl and FireHistoryPt. This personal geodatabase is now ready to load data into.
    Now there are additional Fields in the geodatabase, just created, they are listed below (these are the same fields currently found in SDE):
    OBJECTID (system field, do not edit) SHAPE (system field, do not edit) NIFMID_CN NIFMID_LNK FIRE_NAME FIRE_DAY FIRE_MONTH FIRE_YEAR DATA_SOURCE_TEXT COST LOCAL_NUMBER CAUSE REPORTED_ACRES SIZE_CLASS AGENCY COMMENTS R6_FID UNIT LINKFLAG REV_DATE DATA_SOURCE ACCURACY NIFMID_LNK_OLD SHAPE_Area (POLYGONS only, system field, do not edit) SHAPE_Length (POLYGONS only, system field, do not edit)
    The definitions for the additional fields are listed below.
    DATA_SOURCE_TEXT - This field contains the same information as the DATA_SOURCE field in your spatial geodatabase or coverage. During the data loading process you need to make sure the Matching Source Field for this item is changed to DATA_SOURCE.
    UNIT - Enter the 4 digit number code for Region and Forest, or select from the list of allowable values. A Domain was created to set allowable values for attributes in this field.
    LINKFLAG - This field was created and populated to determine how well the FireHistory data linked with the NIFMID data in Kansas City. Currently only the points have a LINKFLAG code.
    REV_DATE - This is the date of feature creation or latest update, the proper date entry format is MM/DD/YYYY. This is a required field . DST entered either the date the update was received from the forest or the date DST made a change or addition if it was required as part of the standardization process.
    DATA_SOURCE - This is a required field. A Domain was created to set allowable values for attributes in this field. Where the DATA_SOURCE_TEXT code was only GPS, the number code of 02 was used because there was no indication the data was corrected. If no DATA_SOURCE_TEXT code was entered, or was not found in the Code Table, the number code of 24 was used. All fields that have no DATA_SOURCE_TEXT should be coded as 24 - Other.
    NIFMID_LNK_OLD - This field is a copy of the original NIFMID_LNK field, as it was created during the standardization process. When it was determined the NIFMID_LNK did not make a link to the Kansas City data, the NIFMID_LNK field was either corrected or deleted. This field is being kept to track when the NIFMID_LNK was changed, but will probably go away when it no longer serves any usefulness. If any new entries were added this field was calculated the same as NIFMID_LNK.
    Loading Data Into firehistory_updates.mdb Geodatabase - If updates are in a coverage right click on FireHistoryPl, if polygons, or FireHistoryPt, if points, select Load > Load Data, the Simple Data Loader window opens, select Next, navigate to the update cover in the "Input data" block, from the "Open Geodatabase" window select the region feature class if polygons or select the point feature class if points, choose Open, select Add, once all covers are listed in the "List of source data to load" window, select Next, make sure "I do not want to load all features into a subtype." is checked, select Next. In this window is a Target Field and Matching Source Field. For each target field, select the source field that should be loaded into it. Check through the list of fields making the following changes, opposite the Target Field for DATA_SOURCE_TEXT, click on <None> in the Matching Source Field and select DATA_SOURCE from the drop down list; opposite the Target Field for NIFMID_LNK_OLD, click on <None> in the Matching Source Field and select NIFMID_LNK from the drop down list; opposite the Target Field for DATA_SOURCE, in the Matching Source Field make sure <None> is selected from the drop down list. Look through the Matching Source Field and if there are any with a <None>, check to be sure the same data may not be listed under a different Item or Field Name in the cover you're loading data from. Once you're done checking all the fields, select Next, check "Load all of the source data", select Next then Finish.
    Editing the New Fields in the firehistory_updates.mdb Geodatabase - Open ArcMap, add the feature classes data was just loaded in. Open the attribute table of each feature class, make sure the new item fields are populated, by removing the <Null> value and entering the correct value for each field. The new fields needing to be populated are UNIT, REV_DATE, and DATA_SOURCE. Clear the <Null> value from the LINKFLAG field and anywhere else it may appear in the table. Check to make sure the DATA_SOURCE_TEXT field populated correctly. Make sure the COST field is populated where there were costs listed. Updates are moved to a folder on the T drive, create a new ArcMap project, and add the updates to it.
    Before Applying the Updates To SDE YOU MUST know which of the updates are going to make changes to EXISTING spatial data in SDE. This SPATIAL data will need to be deleted from SDE BEFORE applying the updates. If changes are just attribute changes, in SDE, DST made those edits to the SDE Version Copy.
    LOGIN to CITRIX, Open ArcCatalog, then open ArcMap from within ArcCatalog. This assures ArcCatalog and ArcMap are connected to the same server when they open. When opening ArcMap, create a new ArcMap, add the Version copy of S_R06.FireManagement, from SDE, the one having the edits and updates applied to it, it should have edit access privileges granted to you. All deletes, from the corporate data set in SDE, are completed first. All data being replaced, changed or updated, in some way, is easiest to delete the old version from SDE and replace with the new version in an update.
    Loading Updates into SDE, Version Copy of S_R06.FireManagement from ArcMap, on the Editor Toolbar, make sure the Task is "Create New Feature" and the Target is S_R06.FireHistoryPl (Pl for polygon or Pt for point), click on the Selection tab, from the Table of Contents tabs at the bottom. Right click on the update layer, select "Make This The Only Selectable Layer", Right click on the update layer again and choose "Select All" (providing this update contains only updates otherwise you will need to make your selections). The update layer should now be highlighted with bold text, followed by parentheses containing the number of selected features. Click on Edit, from the Main Menu, and select Copy. Click on Edit again and select Paste (you can also use the Copy and Paste icons from the Edit Toolbar). Now you should see the Target layer is highlighted in bold text with the same number in parentheses after it as the update layer had, and the update layer is no longer highlighted. Choose "Clear Selected Features" under Selection on the Main Menu or by right clicking on the target layer and selecting it from the drop down menu. Continue in this manner until all updates are applied to the Version copy for editing.
    Once all updates are applied to the Version copy, DST completed a QA/QC of the Version copy to assure all changes and updates were applied correctly.
    DST then reviewed the metadata for each feature class and made sure metadata was updated where necessary to reflect the current state of the data set.

Who produced the data set?

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

  2. Who also contributed to the data set?

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

    Dale Guenther
    Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    Data Steward
    USDA Forest Service - Pacific Northwest Region
    Portland, Oregon 97208-3623
    USA

    (503) 808-2188 (voice)
    dguenther@fs.fed.us

Why was the data set created?

This data set was created to achieve consistant data, throughout Region 6, for management, planning or analysis involving fire history. Historical Fire Perimeters is a geospatial derivitive of each National Forest's Historical Fire record, of the final forest fire boundaries. It was during 2006 when Region 6 Data Resource Management Data Standardization Team, collected all the spatial data available from each National Forest, in the Pacific Northwest Region. To maintain consistancy throughout Region 6, one standardized data set of the entire Region was created.

How was the data set created?

  1. From what previous works were the data drawn?

    S_R06.FireHistoryPl (source 1 of 10)
    Data Resource Management/Fire a, National Forests, Pacific Northwest Regi, 20071228, S_R06.FireHistoryPl (780-2006).

    Other_Citation_Details:
    The data collected is from the years 780 until present. Two National Forests, the Olympic and Mt. Baker-Snoqualmie, had scientists from their PNW Labs do extensive research using carbon dating techniques to determine fire years for pre 1800 fires.
    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established.
    This is a list of the data files DST received from each forest during the Initial Standardization Process completed in 2005.
    CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_1 shapefile (1992-2002) CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_2 shapefile (1992) CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_3 shapefile (1998) CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_4 shapefile (1993) GIP - 9/26/2005, Ron Pfeifer sent gp_firepl.e00 (Cover Not Usable) MBS - 7/20/2005, Paula James sent fh.e00 (1000-1990) MTH - 6/8/2005, used cover Rick Momsen standardized mthfirehis_pl.e00 (1982-1997) OLY - 6/21/2005, Scott Schreier sent fire_hist.e00 (780-1987) ROR - 7/20/2005, Carol Boyd sent fba_ror.e00 (1910-2003) SIS - 9/12/2005, Jody Thomas sent firehis_pl.e00 (1939-2002) UMP - 8/1/2005, Ed Hall sent ump_firehis_pl.e00 (1987-2003) WIL - 7/18/2005, Rosana Costello sent wil_firehist.e00 (1943-2003) DES - 6/8/2005, Dorothy Thomas sent des_fire.e00 (1800-2003) FRE - 8/8/2005, Laurie Campbell sent fre_fire_poly.e00 and fre_fires92.e00 (1922-1999) OCH - 6/8/2005, used cover Rick Momsen standardized ochfirehis_pl.e00 (1990-2002) WIN - 9/28/2005, Laurie Campbell sent fires-fph_d2b.e00 (1938-2004) MAL - 5/13/2005, Andrew Lacey sent firehis_pl_csa4.e00 (1900-2005) UMA - 5/13/2005, Andrew Lacey sent firehis_pl_csa4.e00 (1850-2005) WAW - 5/13/2005, Andrew Lacey sent firehis_pl_csa4.e00 (1910-2005) COL - 6/14/2005, Cindy Potestio sent firehis_pl_20021011.e00 (1909-2003) OKA/WEN - 5/9/2005, Pat Murphy sent firehist_oka.e00 (1910-2003)
    This is a list of the data files DST received from each forest during the First Update Cycle completed in 2007.
    CRGNSA - 8/6/2007, Cathy Bauer sent nsa_fire_hist_pl_03_06 shapefile MBS - 3/30/2007, Paula James sent firehis_pl_mbs_2006.e00 MTH - 3/30/2007, Jaimie Bradbury sent firehis_update_mth_2006.mdb OLY - 3/23/2007, Doug Sturhan sent firehis_update_oly_2006.e00 ROR - 7/26/2007, Jody Thomas sent fire2006.zip shapefile SIS - 6/5/2007, Jody Thomas sent fire_2005_updates_pl.e00 WIL - 5/25/2007, Rosana Costello sent firehis_pl_update_wil.zip geodatabase DES - 3/14/2007, Gini Stoddard said to retrieve cover from T:\ drive OCH - 3/23/2007, Bruce Wright sent fire_his.mdb MAL - 5/17/2007, Carolyn Winkler sent 2005_2006_firehis_pl shapefile UMA - 5/17/2007, Carolyn Winkler sent 2005_2006_firehis_pl shapefile WAW - 5/17/2007, Carolyn Winkler sent 2005_2006_firehis_pl shapefile COL - 3/22/2007, Cindy Potestio sent firehis_update_col_2006.mdb OKA/WEN - 3/29/2007, Pat Murphy sent firehis_pl_update_oka_wen_2006.e00

    Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb (source 2 of 10)
    Olympic National Forest and Mt , Pacific Northwest Region, Forest Servic, 20080606, Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons 2001-2007 for the Columbia River Gorge National Scenic Area, and the Olympic and Mt Baker-Snoqualmie National Forests.

    firehistory_update_mth_2007.mdb (source 3 of 10)
    Mt. Hood National Forest, Pacific Northwest Region, Forest Servic, 20080702, firehistory_update_mth_2007.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons 2001-2007 for the Mt Hood National Forest.

    firehistory_update_csa4_2007.mdb (source 4 of 10)
    Malheur and Umatilla and Wallow, Pacific Northwest Region, Forest Servic, 20080529, firehistory_update_csa4_2007.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons 2001-2007 for the Malheur and Umatilla and Wallowa-Whitman National Forests.

    firehistory_update_GIP_2007a.mdb (source 5 of 10)
    Gifford Pinchot National Forest, Pacific Northwest Region, Forest Servic, 20080811, firehistory_update_GIP_2007a.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons for the Gifford Pinchot National Forest represent perimeters of 100 acres or more for the years 2001-2007.

    firehistory_update_GIP_2007b.mdb (source 6 of 10)
    Gifford Pinchot National Forest, Pacific Northwest Region, Forest Servic, 20080811, firehistory_update_GIP_2007b.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons for the Gifford Pinchot National Forest represent perimeters of 50 acres or more for the years 1971 through 1998.

    firehistory_update_CSA3_2007.mdb (source 7 of 10)
    Deschutes and Fremont-Winema an, Pacific Northwest Region, Forest Servic, 20080731, firehistory_update_CSA3_2007.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons 2001-2007 for the Deschutes, Fremont-Winema and Ochoco National Forests.

    firehistory_update_col_2007.mdb (source 8 of 10)
    Colville National Forest, Pacific Northwest Region, Forest Servic, 20080125, firehistory_update_col_2007.mdb.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Fire History polygons 2001-2007 for the Colville National Forest.

    firehistory_update_fff_2007 (fff = Forest personal geodatabase) (source 9 of 10)
    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 24000
    Source_Contribution:
    The following Forests did not complete the steps as outlined in the Fire History edit guide. Step 3-completing metadata, and step 5-copy and file archive of update geodatabase. Therefore, their source information is undocumented. CSA2 - Rogue River Siskiyou, Siuslaw, Umpqua, Willamette CSA5 - Okanogan, Wenatchee

    S_R06.FireHistoryPl (source 10 of 10)
    Fire and Aviation Management/Da, Pacific Northwest Region, Forest Servic, 20090529, S_R06.FireHistoryPl.

    Type_of_Source_Media: computer program
    Source_Scale_Denominator: 1:24,000
    Source_Contribution:
    Fire season 2008 polygon fire location data was updated as part of a Pacific Northwest Region (R6) Fire History Data Maintenance "reply due" May 29, 2009, File Code 1390/5100 Memo dated February 27, 2009. The R6 Fire History Edit Guide provides the detailed instruction and guidance for this data maintenance cycle.

  2. How were the data generated, processed, and modified?

    Date: 28-Dec-2007 (process 1 of 12)
    Initial Standardization Phase was completed in 2005 and the First Major Update Cycle for 2006 data was completed in 2007. During the Initial Standardization Phase and the First Major Update Cycle, all Fire History data was submitted to Region 6 Data Resource Management (DRM) Data Standardization Team (DST), by each Forest's GIS Fire Data Manager, from Region 6, in ArcInfo coverage export file format or as shapefiles. During the update process the same file formats were received with the addition of personal geodatabases. Data files were received via e-mail or downloaded from the FTP server, ftp2.fs.fed.us. Data was re-formatted, standardized, and loaded into the Enterprise Fire History Region 6 feature dataset S_R06.FireManagement in SDE.

    Person who carried out this activity:

    Andrew Lacey
    Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    GIS Analyst CSA4
    Umatilla National Forest
    Pendleton, OR 97801
    USA

    541-278-3976 (voice)
    alacey@fs.fed.us

    Data sources used in this process:
    • Each individual National Forest submitted data files to Region 6 Data Resource Management (DRM) Data Standardization Team (DST), for the Initial Standardization Phase and the First Major Update Cycle.

    Date: Initial Standardization Phase was completed in 2005 and the First Major Update Cycle was completed in 2007. (process 2 of 12)
    The following information was taken from individual forests metadata, only where metadata was attached to data, when it was submitted to DST.
    MOUNT HOOD NATIONAL FOREST; Jaimie Bradbury, Acquired shapefile in UTM10, NAD27 from Jim Wrightson, Fire, Mt. Hood NF HQ. Projected shapefiles to Albers NAD83. Imported into polygon feature class with existing attribute fields in working personal geodatbase. Created new polygon feature class in final personal geodatabase. Imported National GIS Data Dictionary defined fields from standardized firehis_pl coverage. In ArcMap, copied and pasted polygons from working personal geodatabase into final personal geodatabase. Edited table to add values to fields. Submitted dataset update to Data Standardization Team (Colleen Williams) 3/30/2007.
    WILLAMETTE NATIONAL FOREST; May 2007 incorporated additions, fires from 2002, 2003, 2005, and 2006. These were provided by fire, as new perimeters to the fire history personal geodatabase created by the DST. Rosana Costello provided a geodatabase to Colleen Williams by May 30, 2007 for incorporation into the regional geodatabase. Additional attributes for NIFMID, and local fire numbers will be provided and populated at a later date, awaiting that information from Fire.
    DESCHUTES NATIONAL FOREST; Procedures Used: Polygons were delineated and manuscripted on a 1:24000 USGS quad base. Original data came from many sources: (1) Pre-1908, no formal records exist, however some reconstructions of the fire regimes of that time have been accomplished by tree ring and stand analysis. Work on the Deschutes NF has been done by Bill Hopkins, Bob Martin, and Steve Simon with district personnel pursuing ancient fires in specific management areas. Gini Stoddards efforts have not addressed this period. (2) 1908-1922, formal, and rather meticulous, fire atlases were kept for the forest during this time. Outlines of the larger fires were added to the atlases on an annual basis. Gini transferred these outlines to the USFS Quads using the section lines as a guide. Often the roads, topography, and/or the image on the 1979 or 1991 Orthogonal photos did not match the transferred outlines particularly well. Certainly there were many errors in the old base maps themselves as well as errors in location of the fires. Almost certainly the outlines of the fires from this era are generalizations since the scale is half inch per mile and the outlines are very smooth. All users of this GIS layer must be aware of the potential inaccuracy of the fire outlines for this time frame. Probably the interior regions of the fire have been accurately captured but there is most certainly errors along the edges. (3) 1923-ca 1940, no formal mapping of large fires was kept in atlas form. Since 50 to 70 years have passed since this era, and extensive logging has further obscured the signatures of these fires, it is nearly impossible to outline these fires from modern aerial photos. As a consequence, many fires from this time were not mapped, but they are carried in the database. The "Can't locate" comment in the remarks section indicates which fires (15 total), mostly from this era, were not mapped. At least five of these fires were greater than 1000 acres. This history needs to be further developed through other means such as newspaper accounts, private timber company records, other photos such as the lookout panoramas, and interviews. (4) 1940-present, Individual districts resumed the keeping of fire atlases with large fire outlines. In addition there are many Forest Service retirees and current employees who fought these fires or were involved with post fire sales and regeneration efforts. Of course, the photography for this era is also much more useful. The major photo series for the entire forest for this time were 1959 black and white, 1967 black and white, 1979 Orthogonal, 1991 Orthogonal, 1991 color, 1900 (exact years unknown) U2, and often special infra-red flights of specific fires. (5) Future, with the advent of GPS, it is unlikely that the methods used in this study (outline on mylar and digitized or scanned for transport into GIS) will be used in the future. Rather, each fire perimeter will be GPSd and those data will be fed directly into GIS. The desire to retain "hard copy", however, may lead to the annual update of the mylar quads stored in the SO Fire unit.
    Revisions or updates are made yearly. Reviews Applied to Data; the manuscripts were reviewed by Deschutes National Forest fire specialists. Related Spatial and Tabular Data Sets; this coverage incorporates ARC/INFO regions for overlapping fire polygons, a subclass table in INFO was created, the subclass is named fires. There may be PC data in the FID field.
    Other References Cited: Notes; A fundamental problem in a fire mapping project is the definition of terms or concepts. Some major considerations are as follows: What is a fire on the Deschutes NF? This project used USFS records, as a result, fires on land which was USFS at that time were recorded. Fires on other public lands or private lands that may now be USFS lands may have been missed. Generally, Gini tried to record as many fire outlines as possible on the USFS quads. Is fire intensity mapped? It was not possible within the time frame of this effort to make any of the fire distinctions regarding fire intensity that are essential to ecological impact assessments. In fact, it may not be possible to quantify intensity for most of the older fires. Indices of fire intensity might be calculated, however, from weather and stand data included in the old atlases. No attempt was made to differentiate between stand replacement and underburn fire behaviors. Certainly the reason some of the fires from the early part of this century are difficult to locate is that they were underburns with little canopy damage. This has probably changed to the extent that modern fires are much more likely to crown and leave a clear signature in the forest and on aerial photography. Where is the fire boundary? For recent fires it is usually the "cat line". Where possible Gini mapped where the fire stopped short of the line, or crossed it. With few exceptions small spots and unburned islands were not differentiated. This dataset is the most recent version, reflecting yearly updates. New fires are added yearly.
    Use Constraints on Deschutes data; Although manuscripted on a 1:24000 base, the data sources for this coverage are extremely variable, as stated earlier in Procedures Used. Due to the nature of data recording and mapping, some fires less than 100 acres may be omitted. This dataset may not be suitable for project level work. Data Set Credits belong to Robert J. Sherman and Karen Curtis, Deschutes National Forest Fire staff.
    Deschutes Process Steps and Process Description: 20011203 - Gini Stoddard UNION fire_perim01 fire01dir/crane-rg fire_perim 20011203 - Gini Stoddard ArcEdit /go/dataset/bend_ftrock/firedir/fire_perim 20011204 - D Rawson EXPORT cover fire_perim/coi/gis/des_fire_perim.e00 20011210 - E Young COPY fire_perim /go/des/fire_perim 20020108 - D Rawson Document fire_perim COPY /go/dataset/Deschutes/archive/fire_perim500 Other steps listed in metadata, but not repeated here, were Metadata imported and Dataset copied.
    CSA4 Blue Mountain Forests are UMATILLA, WALLOWA-WHITMAN and MALHEUR NATIONAL FORESTS; Supplemental Information on CSA4 Forests Data; is stated their coverage is only intended to track fires greater than or equal to ten acres. Fires involved as a complex are recorded under there original fire number and not the complex number. Attribute Accuracy Report on CSA4 Forests Data; states attributes were checked against valid values included in the Core Data standards data dictionary. A value of 100 was given with an Explanation that full outer joins were completed against lookup values for features. Logical Consistency Report stated permissible attribute values were checked using lookup values in ArcInfo Tables. Build was completed at publication time for polygon coverages if necessary, dangles were eliminated, and all editing used Arc9.x for the tests. Completeness Report stated the coverage was complete for all fires turned in through the year 2006, but there were still some missing 2006 fires being worked on by fire.
    CSA4 Forests Process Steps and Process Description: 20030609 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; New polygons are added as regions to the coverage from GPS collected files or are heads up digitized from hand drawn maps using roads, streams, and land ownership boundaries as guides. 20040920 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Blue Mountain Triforest coverage was created from individual forest coverages. Step one was to make each forest coverage structurally the same. Step 2 was to eliminate all overlap of identical fires. An example was the Summit fire. The Summit fire was a Malheur NF fire responsibility, so the polygon and region from the Malheur coverage was maintained and the polygon and region from the Umatilla coverage was eliminated. Step 3 was to append the three coverage region features together into one coverage. Step 4 was to do a region dissolve to eliminate any duplicate records beyond the cover-id. The dissolve was based on all the items beyond the cover-id item. Step 5 was to run regionclean to eliminate from the polygon features any unneeded polygons that were no longer needed to maintain unique region features. Coverage was then updated to the latest core standard, for this feature, and converted to double precision. 20050405 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Added one fire for year 2004 on Ukiah District. Added historical fires for pre-1900 and pre-1910 from historical records. Both of the sources for the 1900 and 1910 fires were at 1,000,000 scale. 20050407 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Added new field to the end of the region feature INFO table. The field was kcfire_id. It is used to connect to the PCHA Database and other historical databases. Move values from the local number field to this field for Wallowa-Whitman NF fires only. 20050513 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Moved values from KCfast_id field to nifmid_cn field and deleted kcfast_id field as being redundant. 20050609 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; Added three fire perimeters from old Snow Mountain District library. Fixed label errors - build coverage to add labels to empty polygons and removed duplicate labels from polygons. 20050722 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; Replaced the 604 fire in Snow Mountain with polygons from the Snow Mountain library "wif" coverage; these are more accurate because they show unburned areas. 20060131 - Carolyn Winkler, GIS Data Specialist on the Wallowa-Whitman National Forest; Wallowa-Whitman NF 2005 large fires added to coverage. Three Burns BLM 2005 fires added (two near the forest boundary and one within forest boundary). 2006 fires for Umatilla NF were added. 20060417 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Projected Data Set to USDA-FS R6 Albers Projection System. 20070213 - Debbie Rinehart, GIS Specialist on the Umatilla National Forest; Updated with 2006 fire polygons. Missing some polygons with what information that is in the fire history database. Informed the fire people of that and they are currently working on it. Removed a label point that was in error.
    COLVILLE NATIONAL FOREST; Process Steps and Process Description: Colville National Forest and vicinity extracted from zone-wide coverage. Overlapping fires within this cover are NOT complete regions. ArcInfo coverages from the Okanogan, Colville and Wenatchee were copied to an edit workspace where they were individually updated to meet new National Core Data Standards, then stitched together into one coverage for the EWZ. ArcInfo source contribution coverages were "fh" Colville cover, "rockcut" Colville cover, "fh" Okanogan cover, "wenhistfire" Wenatchee cover, "fire01bdy" Wenatchee cover, "fire70bdy" Wenatchee cover, "fire94bdy" Wenatchee cover, and "dinkelbdy" Wenatchee cover. Process Steps and Process Description: 20070208 - Janice Berube, GIS/DATA Services Specialist on the Colville National Forest; Updated with Colville NF 2006 fires, Day Creek and Bisbee. The region.fire attribute table was updated for fires greater than 100 acres with data copied from the firehis_pt layer. Fields updated were Fire_Name, Cost, Data_Source, Reported_Acres, and NIFMID_LNK and Local_Number. The NIFMID_LNK and Local_Number compare to the firehis_pt layer in /fsfiles/ref/library/gis/col. The data from these two fields originate in different blocks on the fire report form. 20040819 - Janice Berube, GIS/DATA Services Specialist on the Colville National Forest; 2003 fires were added to coverage. 20060320 - Cindy Potestio, GIS/DATA Services Analyst on the Colville National Forest; Reprojected to Region 6 Albers NAD83 projection. Two other processes were listed, one for dataset copied and metadata imported.

    Data sources used in this process:

    • Each individual National Forest submitted data files to DST, for the Initial Standardization Phase and the First Major Update Cycle. Where metadata was present in forest covers, the Process Step and Process Description was summarized here for each forest having metadata.

    Date: 18-Jul-2008 (process 3 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Person who carried out this activity:

    Jeff Muehleck
    Data Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    GIS Analyst CSA1
    Olympic National Forest
    Olympia, WA 98512
    USA

    360-956-2402 (voice)
    jmuehleck@fs.fed.us

    Data sources used in this process:
    • Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 18-Jul-2008 (process 4 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Person who carried out this activity:

    Jaimie L. Bradbury
    Data Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    GIS Analyst CSA1
    Mt. Hood National Forest Headquarters
    Sandy, OR 97055
    USA

    503-668-1779 (voice)
    jbradbury@fs.fed.us

    Data sources used in this process:
    • firehistory_update_mth_2007.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 18-Jul-2008 (process 5 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Data sources used in this process:

    • firehistory_update_csa4_2007.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 11-Aug-2008 (process 6 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Person who carried out this activity:

    Irene Ward
    Gifford Pinchot National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    GIS Analyst CSA1
    Gifford Pinchot National Forest
    Vancouver, WA 98682
    USA

    509-395-3366 (voice)

    Data sources used in this process:
    • firehistory_update_GIP_2007a.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 11-Aug-2008 (process 7 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Person who carried out this activity:

    Irene Ward
    Gifford Pinchot National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    Fire History feature class editor
    Gifford Pincho National Forest
    Vancouver, WA 98682
    USA

    509-395-3366 (voice)

    Data sources used in this process:
    • firehistory_update_GIP_2007b.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 31-Jul-2008 (process 8 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Person who carried out this activity:

    Dorothy Thomas
    Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    GIS Analyst CSA3
    Deschutes National Forest
    Bend, OR 97702
    USA

    541-383-5570 (voice)

    Data sources used in this process:
    • firehistory_update_CSA3_2007.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 25-Jan-2008 (process 9 of 12)
    As part of our annual maintenance of Fire History, polygons from this personal geodatabase have been incorporated into the Regional feature class.

    Person who carried out this activity:

    Cindi Potestio
    Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    GIS Analyst
    Three Rivers District, Kettle Falls Office
    Kettle Falls, WA 99141
    USA

    (509)738-7747 (voice)

    Data sources used in this process:
    • firehistory_update_col_2007.mdb

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 02-May-2009 (process 10 of 12)
    Fire season 2008 polygon fire spatial location data was updated as part of a Pacific Northwest Region (R6)Fire History Data Maintenance "reply due" May 29, 2009, File Code 1390/5100 memo dated February 27, 2009. The R6 Fire History Edit Guide provides the detailed input and qa/qc instruction and guidance for this data maintenance cycle. Pacific NW Forest in DRM Customer Service Area (CSA) Customer Service Area 1 Columbia Gorge National Scenic Area (CGNSA)-05/22/2009-csa1_Fire_09.gdb DRM Staff Jeff Muehleck360-956-2300 Data Steward CGNSA Staff Roland Rose 542 308-1700 Jeff processed two polygons for fires occuring in 2008 and prior that are not currently in the feature class. 100+ acre are required and 100- acre fires are optional Gifford Pinchot-04/16/2009-firehistory_update_GIP_2008.gdb DRM Staff Irene Ward509-395-3366 Fire Staff John Parsons360-891-5147 or 360-891-5000 Roberto Morganti, GIS Specialist workied with data steward John Parsons to create polygons for the historic large fires. NIFMID data was reviewed and used to populate attributes as available. Mt. Baker-Snoqualmie-CSA1_Fire_09.gdb DRM Staff Jeff Muehleck360-956-2300 Fire Staff N/A No 2008 Fire Perimeter Polygons for the MBS Mt. Hood-04/02/2009-firehistory_update_mth_2008.mdb DRM Staff JaimieBradbury503-668-1779 Fire Staff DebRoy503-668-1756 Editor Jaimie L. Bradbury. Local data steward Jim Wrightson. Fire perimeters acquired from Incident Team GIS specialist or downloaded from <ftp://ftp.nifc.gov/Incident_Specific_Data/PACIFIC_NW>. Includes Gnarl Ridge, Lake Lenore (AKA Schreiner Peak). Attributes entered from NIFMID. Olympic-CSA1_Fire_09.gdb DRM Staff Jeff Muehleck360-956-2300 Fire Staff N/A No 2008 Fire Perimeter Polygons for the Olympic
    Customer Service Area 2 (Jody Thomas-Completed update for entire CSA2) Rogue River-Siskiyou-05/22/2009-Firehistory_update_2008(not archived) DRM Staff-Jody Thomas541.471-6764 Fire Staff-DaveWickwire541.899-3800 Siuslaw-05/22/2009-Firehistory_update_2008(not archived) DRM Staff-Jody Thomas541.471-6764 Fire Staff-Dirk Shupe541.225-6405 Umpqua-05/22/2009-Firehistory_update_2008(not archived) DRM Staff-Jody Thomas541.471-6764 Fire Staff-Liza Castelberry541.957-3305 Willamette-05/22/2009-Firehistory_update_2008(not archived) DRM Staff Jody Thomas541.471-6764 Fire Staff-Dirk Shupe541.225-6405 Fire perimeters for the Rogue River Siskiyou, Umpqua, and Willamette National Forest were added into S_R06.FireManagment Feature dataset into the feature class of S_R06.FireHistoryPl and links established and validated with the records for these forests in the S_R06.FIRE_NIFMID table. In the spring of 2009, this information was received in the form of a shapefile from the data stewards of each of CSA forest.
    Customer Service Area 3 (Dorothy Thomas completed update for entire CSA3) Deschutes-06/24/2009-firehistory_update_DES_OCH_FRE_WIN_2008.gdb DRM Staff-Dorothy Thomas541.383-5570 Fire Staff-Bill Johnson541.383-5435 Fremont-Winema-06/24/2009-firehistory_update_DES_OCH_FRE_WIN_2008.gdb DRM Staff-Dorothy Thomas541.383-5570 Fire Staff-Clint Alberson541.947-6113 Ochoco-06/24/2009-firehistory_update_DES_OCH_FRE_WIN_2008.gdb DRM Staff-Dorothy Thomas541.383-5570 Fire Staff-David Owens541.416-6425 Large Fires identified from the NIFMID table, local contacts provided polygons, attributes populated by linking to NIFMID table.
    Customer Service Area 4 Malheur Umatilla-03/09/2009 Firehistory_pt_update_WWF_2007 DRM Staff Andrew Lacey 547.278-9730 Projected Shape file was created by merging 2 GPSed cleaned up shape files of the fire perimeters. This shape file was then loaded into a version of the firehistory_pl feature class in CITRIX arc catalog. The resulting added polygons were then posted to the Default version by the SDE Manager. Data Steward delegated review roles to DRM for the purpose of this update Wallowa-Whitman
    Customer Service Area 5 Colville-No 2008 Polygons for update. Okanogan and Wenatchee-06/24/2009-Firehistory_update_OKA_WEN_2008.gdb DRM Staff-Jack Rainford509.682-4944 Updated Large Fires for 2008

    Person who carried out this activity:

    Debra Kroeger
    Data Resources Management, Pacific Northwest Region, Forest Service, U.S.Department of Agriculture
    Data Administrator
    Grants Pass Interagency Office
    Grants Pass, OR 97526
    USA

    541 471-6716 (voice)
    dkroeger@fs.fed.us

    Data sources used in this process:
    • S_R06.FireHistoryPl

    Data sources produced in this process:

    • S_R06.FireHistoryPl

    Date: 01-Apr-2009 (process 11 of 12)
    NIFMID_LNK field updated to reflect FIRESTAT_LNK field in the FIRE_NIFMID table to enable linking between datasets. See enclosed scripts to be run in order #1, then #2 and finally #3. This changes the field for Forest Service occurences only where previously it started with USF and now must start with FS.

    Person who carried out this activity:

    Chris Strobl
    Data Resources Management, Pacific Northwest Region, Forest Service, U.S.Department of Agriculture
    Data Standardization Team
    Forest Service
    Portland, OR 97208-3623
    USA

    cstrobl@fs.fed.us

    Data sources used in this process:
    • FIRE_NIFMID Table

    Data sources produced in this process:

    • S_R06.FirehistoryPL

    Date: 25-Jun-2009 (process 12 of 12)
    Dataset copied.

    Data sources used in this process:

    • Service=sde:oracle9i; User=/; Version=S_R06.R06_LIB

  3. What similar or related data should the user be aware of?

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

  1. How well have the observations been checked?

    No tests for attribute accuracy were conducted. Only visual quality checking and cross checking between fire history data in Kansas City NIFMID Database, data from the fire history points and polygons, was conducted by Region 6 Data Resource Management (DRM) Data Standardization Team (DST), for questionable errors. DST communicated those questions to the responsible forest for verification and or correction. Maintenance cycle includes visual quality checking and cross checking between fire history data in Kansas City NIFMID Database.

  2. How accurate are the geographic locations?

    No testing was conducted for positional accuracy.

  3. How accurate are the heights or depths?

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

    Region 6 Data Resource Management (DRM) Data Standardization Team (DST) used queries and concatenation of fields to populate empty required attribute fields. Where reported_acres and or size_class fields were empty, DST used GIS ArcInfo Software to calculate and fill those attribute fields. DST conducted a visual survey on the fire history data that was collected and standardized in 2005. This survey was used to determine attribute completeness, for each forest, in the region. Attribute completeness was only determined based on the mandatory item fields in the data set, which contained fire history data. No accuracy check was made on the quality of the data, only if data existed, in the mandatory fields. Forest overall attribute completeness levels vary across the region. Depending on individual forests, attribute completeness ranges anywhere from 90 percent complete, to not complete. Attribute completeness, when averaging across the whole Region was 50 percent. The Gifford Pinchot and Siuslaw National Forests do not have spatial data for fire polygons. This completeness report refers to the Initial dataset, which had a thorough QA/QC process.

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

    Region 6 Data Resource Management (DRM) Data Standardization Team (DST) used grouping queries to examine the proper spelling and standardization of all text fields, and made changes where necessary. Duplicate entries were eliminated when possible. This logical consistency report refers to the Initial dataset, which had a thorough QA/QC process.

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:
The USDA Forest Service makes no claims, promises, or guarantees about the accuracy, completeness, or adequacy of the content; and expressly disclaims liability for errors and omissions. No warranty of any kind, implied, expressed or statutory, including but not limited to warranties of non-infringement of third party rights, title, merchantability, fitness for a particular purpose and freedom from computer virus, is given with respect to the contents or hyperlinks to other Internet resources. Reference to any specific commercial products, processes, or services, or the use of any trade, firm or corporation name is for the information and convenience of the public, and does not constitute endorsement or recommendation by the USDA Forest Service..

  1. Who distributes the data set? (Distributor 1 of 1)

    Dale Guenther
    Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    Data Steward
    Box 3623
    Portland, Oregon 97208-3623
    USA

    (503) 808-2188 (voice)
    dguenther@fs.fed.us

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

    Fire History polygons

  3. What legal disclaimers am I supposed to read?

    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. It is the responsibility of the data user to use the data appropriately and within the limitations of geospatial data in general, and these data in particular.
    The USDA Forest Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. Although these data have been processed successfully on a computer system at the USDA Forest Service, no warranty, expressed or implied, is made regarding the utility of the data on another system, or for general or scientific purposes; nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.

  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 14-Aug-2008
Last Reviewed: 14-Aug-2008
To be reviewed: None scheduled.
Metadata author:
Connie Rawson
Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Data Administrator Assistant
Deschutes National Forest
Bend, Oregon 97701
USA

(541) 383-4767 (voice)
(541) 383-4700 (FAX)
crawson@fs.fed.us

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

Generated by mp version 2.9.6 on Mon Sep 14 11:17:26 2009