Data Resource Management/Fire & Aviation, National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture 20071228 2 - includes 2006 update vector digital data http://www.blm.gov/or/gis/data.php FIRE_HISTORY_POINT: Fire History points represent the location at which fires in National Forests in the Forest Service Region 6 began. Historical Fire Points is a geospatial derivitive of the National Fire Occurrence Database at Kansas City. This data set was created to achieve consistant data, throughout Region 6, for management, planning or analysis involving fire history. It was during 2006 when DST, 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. Wildfire data is collected and maintained at the Forest and or District level to aid in tracking the areas affected by fire. KCFast is a web-based computer application that simplifies data retrieval from NIFMID. The Forest and or District level, retrieves a file from KCFast that contains all of the mandatory data fields required by the corporate data standard. The Forest uses this data to update and maintain the fire points of origin or fire history points dataset. The Fire Statistics System (FIRESTAT) is a USDA Forest Service application used to electronically enter information from the Individual Fire Report (form FS-5100-29) and store it in the Fire and Aviation Management Web system (FAMWEB). The FAMWEB Administration system is a USDA Forest Service application used to maintain the FAMWEB security information for all related applications using this security application at the Naional Interagency Fire Management Integrated Database (NIFMID) at the National Information Technology Center (NITC) in Kansas City, Missouri. FIRESTAT is a PC Client/Server software application, used to create and save Individual Fire Reports, the information is saved in the Oracle database on local network servers. The fire reports are then loaded into NIFMID, the database for fire occurrence data, at NITC in Kansas City. FIRESTAT is used to enter, update, and delete the required data on the Individual Fire Report form. This point 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 1900 until present. The Mt. Baker-Snoqualmie National Forests did not have dates or the year attached to their points. 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. All forests used NAD1927 datum. 19000101 20060101 Dates are compiled; wildfire ignition was observed for years before 1970, and were downloaded from NIFMID database in Kansas City after 1970. Complete -124.933333 -116.381398 49.000000 41.749934 ISO 19115 Topic Category Environment FSH 5109.14 - Individual Fire Report Handbook Fire Occurrence Fire History Fire Ignition Point Historical Fire Forest Service GIS Data Dictionary Fire Management Fire History Fire None Malheur National Forest Wenatchee National Forest Columbia River Gorge National Scenic Area Idaho Wallowa-Whitman National Forest Pacific Northwest Colville National Forest Washington Umatilla National Forest Siuslaw National Forest Gifford Pinchot National Forest Mt. Baker-Snoqualmie National Forest Willamette National Forest Okanogan National Forest Rogue River-Siskiyou National Forest Fremont-Winema National Forest Ochoco National Forest Mt. Hood National Forest California Deschutes National Forest Umpqua National Forest Oregon Pacific Northwest Region Olympic National Forest NON-BLM DATA - FOR INTERNAL USE ONLY - NOT FOR DISTRIBUTION. This data is available to internal Bureau of Land Management (BLM) staff, contractors and partners. All other requests for this data will be referred to the source agency. NON-BLM DATA - FOR INTERNAL USE ONLY - NOT FOR DISTRIBUTION. Users will take reasonable measures to ensure that this data is protected from disclosure. Users assume the entire risk associated with use of these data. The BLM has no liability for unintentional disclosure, nor for any use or misuse of the data. Users bear all responsibility in determining the fitness of this data for the intended use. Users must consider the following: time sensitivity of the data; spatial differences in measure, projection, or accuracy; differences in terminology, description, or place names. External source Metadata may not be complete, or reliable, or observe BLM, FGDC or ISO standards. Users will assume that no attempts have been made to verify, correct, or complete the source metadata, except where noted in a process step – the data and metadata are “as is” from the source. The BLM attempts to ensure that the external data in corporate holdings is current. Users are responsible for verifying the timeliness of data. The BLM is not responsible for maintenance or update, and offers no warranty of data. Users agree not to misrepresent the data, nor to imply that changes made were approved or endorsed by the BLM. Users will cite this data as source data in any products derived from this data. Users that modify data are obligated to describe in a process step the modifications made. The source organization may update this data without notification to users. Users will accept the data as is, with all faults. US Forest Service Dale Guenther System Analyst mailing

333 Southwest First Avenue

Portland OR 97204 US (503) 808-2188 dguenther@fs.fed.us Unclassified Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 1; ESRI ArcCatalog 9.2.2.1350 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 DST, for questionable errors. DST communicated those questions to the responsible forest for verification and or correction. Region 6 Data Resource Management (DRM) Data Standardization Team (DST) used grouping queries to examine the proper spelling and standardization of all coverage attribute text fields, and made changes where necessary. Duplicate entries were eliminated when possible. 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 99 percent complete, to not complete. Attribute completeness, when averaging across the whole Region was 65 percent. The Mt. Baker-Snoqualmie National Forests do not have fire dates or years for their point spatial data in this dataset. No testing was conducted for positional accuracy. Data Resource Management/Fire & Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture 20071228 24000 onLine 19000101 20060101 Most current data available within the stated time period. Data was collected and maintained at Kansas City for fire points beginning with the year 1970. Data before 1970 was collected and maintained at the Forest and/or District levels. Unknown 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 - 6/30/2005, Cathy Bauer sent Fire_pts_7__2005 shapefile (1992-2004) GIP - 2/10/2005, use cover Rick Momsen standardized GIP_Firehis_pt.zip (1970-1994) MBS - 2/10/2005, use cover Rick Momsen standardized MBS_Firehis_pt.zip (No Year Info) MTH - 2/10/2005, use cover Rick Momsen standardized MTH_Firehis_pt.zip (1985-2003) OLY - 6/22/2005, use cover Rick Momsen standardized OLY_Firehis_pt.zip (1970-2003) ROR - 2/10/2005, use cover Rick Momsen standardized ROR_Firehis_pt.zip (1970-2003) SIS - 2/10/2005, use cover Rick Momsen standardized SIS_Firehis_pt.zip (1970-2004) SIU - 2/10/2005, use cover Rick Momsen standardized SIU_Firehis_pt.zip (1970-2001) UMP - 2/10/2005, use cover Rick Momsen standardized UMP_Firehis_pt.zip (1970-2001) WIL - 2/10/2005, use cover Rick Momsen standardized WIL_Firehis_pt.zip (1970-2003) DES - 6/15/2005, use cover Rick Momsen standardized DES_Firehis_pt.zip (1980-2002) FRE - 9/7/2005, Laurie Campbell sent fre_firept.e00 (1949-1999) OCH - 7/29/2005, Bruce Wright sent firehis_pt.e00 (1970-2004) WIN - 8/2/2005, Laurie Campbell sent firehist_pt_win.e00 (1912-2004) MAL - 7/30/2005, Dave Stockdale sent firehis_pt.e00 (1919-2004) UMA - 7/31/2005, Andrew Lacey said download firehis_pt from fsweb.f14.r6 (1970-2004) WAW - 7/31/2005, Danielle Bernard said download firehis_pt from fsweb.f16.r6 (1970-2004) COL - 8/2/2005, Janice Berube sent col_fire_pt05.e00 (1938-2005) OKA - 8/9/2005, Jack Rainford sent Okanogan_fire_pt_history.e00 (1900-2004) WEN - 8/2/2005, Pat Murphy sent firehispt.e00.zip (1900-2004) This is a list of the data files DST received from each forest during the First Update Cycle completed in 2007. CRGNSA - 8/8/2007, Cathy Bauer sent nsa_fire_pts_2005 shapefile CRGNSA - 8/8/2007, Cathy Bauer sent nsa_fire_pts_2006 shapefile GIP - 3/30/2007, Irene Ward sent firehis_update_gip_2006.mdb MTH - 3/30/2007, Jaimie Bradbury sent firehis_update_mth_2006.mdb OLY - 4/6/2007, Doug Sturhan sent firehis_pt_update_oly.e00 ROR - 6/5/2007, Jody Thomas sent fire0506.zip shapefile SIS - 6/5/2007, Jody Thomas sent fire0506.zip shapefile UMP - 2/26/2007, Ed Hall sent firehis_pt_update_2006_ump.e00 UMP - 2/27/2007, Ed Hall sent firehis_pt_update_2002_2005_ump.e00 FRE - 7/26/2007, Dennis Griffin sent shapefile, unable to use, incomplete, only contained Lat/Long OCH - 3/23/2007, Bruce Wright sent fire_his.mdb (Complete forest update/replacement) WIN - 7/26/2007, Laurie Campbell sent winema_firehist_pt.zip, Arc Export MAL - 3/26/2007, Dave Stockdale sent m_firehis_pt.e00 (Complete forest update/replacement) UMA - 3/9/2007, Andrew Lacey sent firehis_pt.e00 (Complete forest update/replacement) WAW - 3/16/2007, Danielle Bernard sent 2005-2006 shapefiles on a DVD COL - 3/22/2007, Cindy Potestio sent firehis_update_col_2006.mdb OKA/WEN - 3/30/2007, Pat Murphy sent firehis_pt_update_oka_wen_2006.e00 The following information was taken from individual forests metadata, only where metadata was attached to data, when it was submitted to DST. GIFFORD PINCHOT NATIONAL FOREST; Fire History points for 2006 were summarized from Fire Reports into FIRESTAT 2006 for GIS.xls by Dispatch (Amy Davis). Location information was in degrees, minutes, seconds or Township, Range, Section (fractions) descriptions. Amy used a conversion tool on her PC to convert to decimal degrees and entered the latitude/longitudes into the .xls file. Irene Ward formatted a copy of the .xls (fires06.xls) using Excel and MS Access to add and define the standard data fields, populated Agency, Data_Source, Cause (a numeric field from the initial Cause text field), Size_Class from Reported_Acres field, and formatted Fire_Day and Fire_Month with leading zeros, and Fire_Name using the PROPER function to have first letter of a word in upper case, the rest in lower case (and checked for the other syntax requirement for fire names). The resulting event table (Fires06) was brought into ArcMap, for Display X,Y. Had first added SDE feature class S_R06.FireManagement/S_R06.FireHistoryPt in ArcMap, so could use it's spatial reference when exporting the point events. Exported to a personal geodatabase for loading into a template personal geodatabase created per draft Fire History Edit Guide, March 27, 2007 from the R6 DRM Data Standardization Team (Colleen Williams). MOUNT HOOD NATIONAL FOREST; Jaimie Bradbury acquired 3 point shapefiles by year (2004, 2005, 2006) in UTM10 NAD27 from Jim Wrightson, Fire, Mt. Hood NF HQ, as queried and generated from the National Fire Occurrence Database, NIFMID. Jaimie projected shapefiles to Albers NAD83 and imported each year into separate point feature class with existing attribute fields in working personal geodatabase. Created new point feature class in final personal geodatabase, imported National GIS Data Dictionary defined fields from standardized forehis_pt coverage. Loaded separate year point feature classes from working personal geodatabase into single point feature class in final personal geodatabase, mapping fields available to match National GIS Data Dictionary fields. In ArcMap, joined working personal geodatabase tables for each fire occurrence year to the fire history point feature class in the final personal geodatabase, calculated value for NIFMID_LNK by concatenating fields as described in National GIS Data Dictionary. NIFMID number was not provided with original data. Calculated FIRE_DAY, FIRE_MONTH, and FIRE_YEAR values by parsing DISC_DATE field using VBScript function DatePart (interval, date_field). Added two missing points by creating event layer from longitude, latitude x,y coordinates in decimal degrees supplied by Jim Wrightson. Saved as shapefile with original shapefiles. Projected to Albers NAD83, saved with other projected shapefiles, imported into working personal geodatabase, and loaded into point feature class in final personal geodatabase. Fire history corporate dataset update was submitted to Data Standardization Team (Colleen Williams) 3/30/2007. UMPQUA NATIONAL FOREST; Points were imported from a spreadsheet using decimal degrees, converted to a shapefile, and then a coverage. Spreadsheet retrieved from fire database. MALHEUR NATIONAL FOREST; The points layer was developed through the FAMWEB, KC Fast, fire, fire reports. Choose the "Corporate GIS for Administrative Unit format". The file that is produced contains all of the mandatory data fields required by the corporate data standard. A username and password is required to use this site. In most cases the Fire Management Officer or Dispatcher on the Forest unit will have access to the web site and know how t run the query. Once the file has been downloaded to a PC, run the fire-hispt_con.aml. The aml is designed to process data that has been downloaded from the databasea dn will create an output "GIS" coverage. Data from the south end of the forest (within the BIFZ fire planning unit) up to date through 2004. Data from the north end is only complete through 2002. Process Steps and Process Description: 20050210 - Rick Momsen, Data Standardization Team contractor through Titan Corp.; standardized coverage to agree with the GIS Core Data Dictionary. 20050523 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; copied to double precision. 20050715 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; Updated with fire points from BLM Burns District (Stacy Fenton). Layer created from various sources: Burns BLM, Malheur NF, Snow Mountain District, NIFMID/KCFAST national database. Since almost all of Malheur's points from before 2002 were hand-drawn ("HD"), I decided to use the BLM layer which had a more accurate location. To make it easier I also used the BLM 2002 NIFMID locations. I added the FS attributes to the BLM layer and calculated the values in from BLM. Where the locations overlapped, I deleted the FS point. On the NIFMID points I manually calculated the values from the FS coverage onto the BLM point. Snow Mountain fire points before 1993 were added from the Snow Mountain library fire_pcha and fire_pt layers: from 1985-92 from pcha as that was more accurate; before 1985 from fire_pt. The final steps were to clip the BLM layer to the Malheur watershed extent, remove the BLM attributes, and merge the BLM layer into the firehis_pt coverage. 20060327 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; Reprojected to Region 6 Albers NAD83 projection. 20070323 - Teri Corning-Sevey, GIS/Data Services Specialist on the Malheur National Forest; Updated with 2006 fire season points. UMATILLA NATIONAL FOREST; Completeness Report: All fires less than ten acres and start locations for larger fires are shown in this coverage to the effect that fire locations where given to the Umatilla GIS for input. The coverage is completed each year for each year to follow. Process Steps and Process Description: 20040429 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Pathfinder office gps files, other venders gps files, ascii text files of lat and long coordinates from kcfast, heads up digitizing using DRGS. Year update process is to pull new locations from KCFAST database. You need to have a WIMS username and password. Go to http://famweb.nwcg.gov/ and select KCFAST, Fire, Fire Reports. Put in administrative unit (0614), begin year and end year. Then select corporate GIS for Administration unit. The report will go to a FTP site and retrieve from there. Take text file report and add column headings by inserting a new text line at start of file. Project file using ArcCatalog assuming a geographic projection with a NAD83 Datum from North America. Then reproject to local projection. Match PAT table and append to existing coverage. 20041222 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Added in 2004 year fire start locations. All locations were derived from the data in the KCFast database. All locations were derived from the Latitude and Longitude stored in the database for the 2004 fires. All Lat and Long were assumed to be in NAD83 Geographic and then reprojected to the local projection. 20050627 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Dropped redundant items that are also in the PCHA database. Corrected the locations of some points where the Lat and Long values were incorrectly entered. 20060301 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Reprojected to Region 6 Albers NAD83 projection. 20070309 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Added calendar year 2005 and 2006 fires from Information in the NIFMID and or KCFast interface. Points were reprojected from a NAD83 Geographic Projection into the local projection. COLVILLE NATIONAL FOREST; Process Steps and Process Description: 19990112 - Dave Larson on the Colville National Forest; Colville NF - FOC Oracle database on DG converted to Info and added to FOC.pat. 20010307 - Janice Berube on the Colville National Forest; Added fire occurrence points for 1999 and 2000 - Colville NF. 20040121 - Janice Berube on the Colville National Forest; Fire starts added for 2002 and 2003 (with Nancy Cassel) - Colville NF. 20050121 - Rick Momsen, Data Standardization Team contractor through Titan Corp.; standardized coverage to agree with the GIS Core Data Dictionary. Metadata updated. 20050128 - Cindy Potestio on the Colville National Forest; Fire starts for 2004 (Colville NF) added (with Jimmy Corvino), missing information added for fires back to 1994, metadata updated. 20060119 - Janice Berube, GIS/Data Services Specialist on the Colville National Forest; Fire starts for 2005 (Colville NF) added (with Nancy Cassel). Matched attribute fields to a R6 data standardization copy by Colleen Williams requested by Dale Guenther for the National Data Warehouse on 07/29/05. Removed SO- from local_number. Deleted USF0608 points outside of Colville NF administrative boundary. Changed Agency field for BIA points. Newport District added 2002/2003 BIA points. These points have missing attributes which will be completed at a later date. 20060320 - Cindy Potestio, GIS/Data Services Analyst on the Colville National Forest; Reprojected to Region 6 Albers NAD83 projection. 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. 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. Each individual National Forest submitted data files to DST, for the Initial Standardization Phase and the First Major Update Cycle. 20071228 Data Standardization Team, Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture Colleen Williams Database Standardization Specialist mailing

Wallowa-Whitman National Forest

P.O. Box 907

Baker City OR 97814 US 541-523-1253 cmwilliams@fs.fed.us USDA Forest Service-Pacific Northwest Region, Fire History Ignition Points Vector Entity point 61284 2e-008 2e-008 Decimal Degrees D North American 1983 GRS 1980 6378137.0 298.257222101 Fire History Points INFO Point Attribute Table Forest Service GIS Data Dictionary(FSGDD), Fire Management Theme, Fire History Layer FIRE_MONTH The month the geographic data represents. (Example: 09) 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. 01-12 Double digit number representing the month of the year. 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 from 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. Date PERIMETER FIREHIS_PT FIREHIS__1 FIRE_YEAR The fire discovery year the geographic data represents. (Example: 2006) 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. If only the year is known, enter only the year and note the source in the comments field. Where this field had values like, 18yy, 18xx, or 19??; Per instruction from Dale Guenther it was changed to 1850 or 1900 with the comment "Exact fire year unknown", if there was room in the COMMENTS field. Date OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. COST Cost of suppression to the nearest dollar. $2,000,000 was spent on fire. (example: 2000000) 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. Round to the nearest dollar. The matching field found in the NIFMID database at Kansas City is Fire_Cost_In_Dollars. Dollars 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. FSH 5109.14, Chapter 30(34); Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer. Generated Unique Code A 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) Forest Service National Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer. 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. FSH 5109.14, Chapter 30(34); Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer. 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. This code is used as a link between SDE, the table S_R06.Fire_NIFMID, and the NIFMID database in Kansas City, the National Fire Occurrence Database. All parts of this code are right justified and zero filled. Where this field is null, populate by concatenating the dataset item fields, AGENCY, Unit, Subunit, FIRE_YEAR, and LOCAL_NUMBER. If any of these item fields are null, they will be zero filled. 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 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. During the standardization process, the word "Fire" was dropped from any fire name, if "fire" was in the last place. An example is "Bear Fire" would be "Bear", but "Fire In The Hole" would remain unchanged. Where the fire name was in all caps, it was changed to mixed upper and lower case, proper case. (Example: BEAR CREEK was changed to Bear Creek). If symbols like #&"_./ were contained in the fire name, they were removed. (Example: LONESOME/MCPINE was changed to Lonesome-McPine or FIRE #450 was changed to Fire 450). The only symbol allowed was a hypen or dash. Where FIRE_NAME was left blank, the field was populated with "Unknown". The assigned name of the fire, a 34 character field. Fires that belong to a "Complex Fire", the name of the Complex they belong to should be stated in the COMMENTS field. FIRE_DAY The day of the month the geographic data represents. (Example: 07) 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. 01-31 Double digit number representing the day of the month. 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 from 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. Date CAUSE Use Coding for "Statistical Cause" code, a one digit number (numbers 1-9) that identifies the broad statistical cause for the fire. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Occurrence Block on the Individual Wildland Fire Report form. 1 Lightning Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 2 Equipment Use Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 3 Smoking Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 4 Campfire Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 5 Debris Burning Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 6 Railroad Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 7 Arson Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 8 Children Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 9 Miscellaneous Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Occurrence Block on Form 5100-29, Individual Wildland Fire Report. 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. FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). A 0 to .25 Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). B .26 to 9.9 Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). C 10 to 99.9 Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). D 100 to 299.9 Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). E 300 to 999.9 Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). F 1000 to 4999.9 Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). G 5000+ Acres FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). Where this field was blank, GIS was used to calculate SIZE_CLASS, using REPORTED_ACRES. AGENCY Protecting Agency of Record at Origin legally responsible to provide primary protection for the land on which the fire started. FSH 5109.14 Individual Fire Report Handbook, found in the Identification Block on Form FS-5100-29, Individual Wildland Fire Report. AFS Department of Defense, Air Force Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. ARM Department of Defense, Army Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. BIA USDI, Bureau of Indian Affairs Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. BLM USDI, Bureau of Land Management Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. DNR Washington Department of Natural Resources (State) Dale Guenther approved the code for Washington State, Department of Natural Resources, DNR. FWS USDI, Fish and Wildlife Services Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. ID State Lands in Idaho Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. NAV Department of Defense, Navy Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. NOP No Protection Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. NPS USDI, National Park Service Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. ODF Oregon Department of Forestry (State) Dale Guenther approved the code for Oregon State, Department of Forestry, ODF. OR State Lands in Oregon Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. OTH Other Federal Agency Land Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. PVT Private Land Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. USF USDA, Forest Service Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. WA State Lands in Washington Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Identification Block of the Individual Wildland Fire Report form. Those values found in the NIFMID database, but not listed in the FSH 5109.14, are ODF and DNR were put in the list of value definitions and given the assumed definition. COMMENTS Open text field for additional information. Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. 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. SHAPE Feature geometry. ESRI Coordinates defining the features. DATA_SOURC Describes the source of spatial data collection used. Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. GPS Global Positioning System Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. IR Infrared Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. HD Hand Drawn Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. PI Photo Interpretation Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. OTHER:IKONOS imagery from 07/07/00 Describe the source data. Be consistent and as specific as possible when describing OTHER data sources. Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer. GPS-IDT Malheur National Forest GPS-IMT Malheur National Forest MAP Fremont National Forest MAP_PHOTO Fremont National Forest MAP_PHOTO_GPS Fremont National Forest OTHER:BIFZ Burns Interagency Fire Zone (compiled by BLM) Malheur National Forest OTHER:BUFIREPTS Burns BLM District Fire Points Malheur National Forest OTHER:EMI Emigrant Creek Ranger District Fire Points (compiled by BLM) Malheur National Forest OTHER:KCFAST USFS KCFAST National Fire Database (compiled by BLM) Malheur National Forest OTHER:MAF Malheur National Forest (compiled by BLM) Malheur National Forest OTHER:NIFMID KCFAST National Fire Database (compiled by USFS) Malheur, Umatilla, and Wallowa-Whitman National Forests OTHER:NIFMID_BLM BLM NIFMID National Fire Database Malheur National Forest OTHER:ODF Oregon Department of Forestry (compiled by BLM) Malheur National Forest OTHER:PCHA PCHA Database Ochoco and Olympic National Forest OTHER:PCHC Olympic National Forest OTHER:SM Snow Mountain Ranger District fire points (compiled by BLM) Malheur National Forest OTHER:STATE State of Oregon (compiled by BLM) Malheur National Forest OTHER:REM Malheur National Forest OTHER:Scientific Used Carbon Dating PNW Scientists used carbon dating techniques to determine year burned. DST created this code for polygon data on the Olympic and Mt. Baker-Snoqualmie National Forests. Initial definitions were left to open text, giving direction to describe the source of spatial data collection using keywords (e.g. GPS) where possible. Describe the source of data. Be consistent and as specific as possible when describing OTHER data sources. With open text source descriptions, it has allowed for several variations of the same source type. Some source types were combined, but no definitions of those combinations, refer to the single source for definitions. All source types listed in the dataset are listed here, but not all have definitions of their meaning. LOCAL_NUMB The Fire Number, required in NIFMID, is a three digit number assigned to the fire by the Forest Supervisor's Office. (Example: 090) Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29. Matching field in NIFMID database in Kansas City is Fire_Number. This is a confusing field, not well defined previously. It becomes problematic when the fire number is not the same number as reported to Kansas City NIFMID database. Old numbers may consist of district or local numbers and text, if used, the NIFMID_LNK field will not have a valid link to the Kansas City NIFMID database. POLYGONID SCALE ANGLE REPORTED_A Final acreage as reported on the final Incident Command System Status Report 209. 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. Where this field was blank, GIS is used to calculate acres using the fire polygons, if available. The formula used is AREA multiplied by the acres conversion factor of 0.0002471054. Bureau of Land Management Eric Hiebenthal GIS Data Management Specialist mailing

P.O Box 2965

Portland OR 97208 US 503-808-6340 503-808-6419 ehiebent@blm.gov contact instructions BLM INTERNAL USE. NOT FOR DISTRIBUTION. Distribution requests from outside the BLM for this data will be referred to the source agency. The BLM has no liability for the unintentional disclosure of data. The BLM assumes no responsibility for errors or omissions and makes no warranty to the accuracy, reliability, or completeness of this data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. BLM computers successfully processed this data. The BLM makes no warranty, expressed or implied, regarding the use of this data on any other system, or for general or scientific purposes, nor does distribution constitute or imply any such warranty. The BLM has no liability for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM. Contact distributor. Data are only available through the Oregon/Washington State office of the Bureau of Land Management. 20080117 Bureau of Land Management, Oregon State Office Roger Mills GIS Specialist mailing

P.O. Box 2965

Portland OR 97208 US (503) 808-6340 tdd/tty phone (503) 808-6419 r2mills@blm.gov 8:00-4:00 None FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time Unclassified