Data Resource Management/Fire and Aviation, National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture 20080801 vector digital data Server=oracle-idb.pdx; Service=5151; User=s_r06$design; Version=SDE.DEFAULT firehistorypt Fire History points represent the location at which fires 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. enWildfire 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. 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. 1900 2007 Dates are compiled; wildfire ignition was observed for years before 1970, and were downloaded from NIFMID database in Kansas City after 1970. Complete At a minimum, completed annually by January 15, triggered by the event of annual Fire Season. Specific information and direction may be obtained from the Region6/PNW Spatial Data Maintenance Plan and the Fire History Edit Guide. -125.489651 -115.836932 53.016415 41.657916 364596.700000455941.2226561038385.1162111200176.369922 FSH 5109.14 - Individual Fire Report Handbook Fire History Fire Occurrence Historical Fire Ignition Point Fire None Pacific Northwest Region Deschutes National Forest Fremont-Winema National Forest Gifford Pinchot National Forest Malheur National Forest Mt. Baker-Snoqualmie National Forest Mt. Hood National Forest Ochoco National Forest Okanogan National Forest Olympic National Forest Rogue River-Siskiyou National Forest Siuslaw National Forest Umatilla National Forest Umpqua National Forest Wallowa-Whitman National Forest Wenatchee National Forest Willamette National Forest Colville National Forest Columbia River Gorge National Scenic Area California Idaho Oregon Washington Pacific Northwest EnvironmentISO 19115 Topic CategoryFire ManagementFire HistoryFireForest Service GIS Data Dictionary None 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. Dale Guenther Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture Data Steward mailing address

USDA Forest Service - Pacific Northwest Region

Portland Oregon 97208-3623 USA

P.O. Box 3623

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 Shapefile 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. This accuracy report refers to the Initial dataset, which had a thorough QA/QC process. 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. Maintenance cycle includes visual quality checking and cross checking between fire history data in Kansas City NIFMID Database. This logical consistency report refers to the "Initial dataset", which had a thorough QA/QC process. 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. This completeness report refers to the Initial dataset, which had a thorough QA/QC process. No testing was conducted for positional accuracy. Data Resource Management/Fire & Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture20071228 24000 computer program 1900 2006 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 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 Colleen Williams Data Standardization Team, Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture

Wallowa-Whitman National Forest

mailing address

P.O. Box 907

Baker CityOR97814USADatabase Standardization Specialist541-523-1253cmwilliams@fs.fed.us 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 was completed in 2007. Olympic National Forest and Mt Baker-Snoqualmie National Forest and Columbia River Gorge National Scenic Area, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture2008060624000computer program2001010120071231publication dateFirehistory_update_CSA1_NSA_OLY_MBS_2007.mdbFire History points 2001-2007 for the Columbia River Gorge National Scenic Area, and the Olympic and Mt Baker-Snoqualmie National Forests.

Olympic National Forest

mailing address

1835 Black Lake Blvd SW

OlympiaWA98512USAJeff MuehleckData Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of AgricultureGIS Analyst CSA1360-956-2402jmuehleck@fs.fed.usAs part of our annual maintenance of Fire History, points from this personal geodatabase have been incorporated into the Regional feature class.Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb20080718S_R06.FireHistoryPtMt. Hood National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture2008070224000computer program2001010120071231publication datefirehistory_update_mth_2007.mdbFire History points 2001-2007 for the Mt Hood National Forest.

Mt. Hood National Forest Headquarters

mailing address

16400 Champion Way

SandyOR97055USAJaimie L. BradburyData Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of AgricultureGIS Analyst CSA1503-668-1779jbradbury@fs.fed.usAs part of our annual maintenance of Fire History, points from this personal geodatabase have been incorporated into the Regional feature class.firehistory_update_mth_2007.mdb20080718S_R06.FireHistoryPt24000computer programfirehistory_update_csa4_2007.mdbMalheur and Umatilla and Wallowa-Whitman National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture200805292001010120071231publication dateFire History points 2001-2007 for the Malheur and Umatilla and Wallowa-Whitman National Forests.

Umatilla National Forest

2517 SW Hailey Ave.

mailing and physical addressPendletonOR97801USAAndrew Lacey Data Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture GIS Analyst CSA4541-278-3976 alacey@fs.fed.usAs part of our annual maintenance of Fire History, points from this personal geodatabase have been incorporated into the Regional feature class.firehistory_update_csa4_2007.mdb20080718S_R06.FireHistoryPtGifford Pinchot National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture2008081124000computer programfirehistory_update_GIP_2007a.mdb1995010120071231publication dateFire History points 1995-2005 for the Gifford Pinchot National Forest.firehistory_update_GIP_2007a.mdbS_R06.FireHistoryPt

Gifford Pinchot National Forest

mailing address

10600 N.E. 51st Circle

VancouverWA98682USAIrene WardData Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of AgricultureGIS Analyst CSA1509-395-3366As part of our annual maintenance of Fire History, points from this personal geodatabase have been incorporated into the Regional feature class.2008081124000computer programfirehistory_update_GIP_2007b.mdbFire History Points 2007 for the Gifford Pinchot National Forest.Gifford Pinchot National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture200808112007010120071231publication date

Gifford Pinchot National Forest

mailing address

10600 N.E. 51st Circle

VancouverWA98682USAIrene WardData Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of AgricultureGIS Analyst CSA1509-395-3366As part of our annual maintenance of Fire History, points from this personal geodatabase have been incorporated into the Regional feature class.firehistory_update_GIP_2007b.mdb20080811S_R06.FireHistoryPtDeschutes and Fremont-Winema and Ochoco National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture2008073124000computer programfirehistory_update_CSA3_2007.mdbFire History Points 2001-2007 for the Deschutes, Fremont-Winema and Ochoco National Forest.20071231publication date24000computer programfirehistory_update_col_2007.mdbColville National Forest, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture200801252001010120071231publication dateFire History Points 2001-2007 for the Colville National Forest.As part of our annual maintenance of Fire History, points from this personal geodatabase have been incorporated into the Regional feature class.

Three Rivers District, Kettle Falls Office

255 W 11th

mailing addressKettle FallsWA99141USACindi PotestioData Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of AgricultureCSA5 GIS Analyst (509)738-7747firehistory_update_col_2007.mdb20080125S_R06.FireHistoryPt24000computer programfirehistory_update_fff_2007 (fff = Forest personal geodatabase)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, WenatcheeDataset copied.\\166.6.122.178\f\library\gis\r06\siskiyou\fire\firehistoryrrsis.mdb2009012915232100Dataset copied.\\LTIBLKVPWX2\C$\gis\geodatabase_conversion\firehistoryupdates\firehistory_update_wil_2008.mdb2009062309271500 USDA Forest Service-Pacific Northwest Region, Fire History Ignition Points Vector Entity point 63322 Point 298 SimplePointFALSE0FALSEFALSE coordinate pair 0.100000 0.100000 meters Albers Conical Equal Area43.00000048.000000-120.00000034.000000600000.0000000.000000 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983NAD_1983_Oregon_Washington_Albers 1.000000 Explicit elevation coordinate included with horizontal coordinates S_R06.FireHistoryPt INFO Point AttributeTable Forest Service GIS Data Dictionary(FSGDD), Fire Management Theme, Fire History Layer Feature Class0 FIDFIDOID400Internal feature number.ESRISequential 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. 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_CNString34 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. NIFMID_LNKString17 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_NAMEString34 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 FIRE_DAYString2 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 FIRE_MONTHString2 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 FIRE_YEARString4 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 COSTNumber9 DATA_SOURCDATA_SOURCString34 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. CAUSENumber4 LOCAL_NUMBLOCAL_NUMBString8 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. SIZE_CLASSString1 REPORTED_AREPORTED_AFloat1911 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. AGENCYString3 COMMENTS Open text field for additional information. Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. COMMENTSString60 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. R6_FIDString30 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) Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0601 Deschutes National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0602 Fremont National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0603 Gifford Pinchot National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0604 Malheur National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0605 Mt. Baker-Snoqualmie National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0606 Mt. Hood National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0607 Ochoco National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0608 Okanogan National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0609 Olympic National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0610 Rogue River National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0611 Siskiyou National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0612 Siuslaw National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0614 Umatilla National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0615 Umpqua National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0616 Wallowa-Whitman National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0617 Okanogan-Wenatchee National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0618 Willamette National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0620 Winema National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0621 Colville National Forest Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 0622 Columbia River Gorge National Scenic Area Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29 Identifies ownership of each feature object. UNITString4 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. 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. DBL LINK Has 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). DUP Same 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). GOOD Has a NIFMID_LNK number in FireHistory dataset that matches with KC NIFMID data. All data appears to match between spatial dataset and KC database. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). GOOD1 DATE Data from FireHistory only matches on the date field with KC NIFMID data, has not other data to match to. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). GOOD1, GOOD2, GOOD3, GOOD4, GOOD5, GOOD6 The 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). NO DATE FireHistory 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). NO LINK FireHistory 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). NON FS DUP Item 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). NON FS The AGENCY field in FireHistory is not coded USF. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). NOT IN KC Item has a spatial location in FireHistory, as well as attribute data, but not found in KC NIFMID database. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). YEAR ONLY FireHistory 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. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). PRIOR KC FireHistory spatial data with FIRE_YEAR before 1970. Kansas City NIFMID database only has data from 1970 to present. Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC). Code represents the quality of the data and how good the link to NIFMID database in Kansas City is. This field is used to aid in determining how accurate and/or complete the attribute data is, as well as, how great the potential to link with the NIFMID database in Kansas City is. LINKFLAGString10 REV_DATE This is the date of feature creation or latest update. 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. The proper date entry format is MM/DD/YYYY REV_DATEDate8 ACCURACY This is the accuracy of the spatial location of the data. The expected difference between feature and real world object location. 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. Coordinates defining the features. Go to web location for complete description. ACCURACYFloat1911 DATA_SOU_1DATA_SOU_1String2 SHAPE Feature geometry. ESRI Coordinates defining the features. ShapeGeometry000 NIFMID_L_1NIFMID_L_1String17 S_R06.FireHistoryPt_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 point spatial data, table S_R06.FireHistoryPt, 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 If you need additional information on table joins, use ArcMap Help, About Joining Attribute Tables Relationship 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. Dale Guenther Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture Data Steward mailing address Portland Oregon 97208-3623 USA

USDA Forest Service - Pacific Northwest Region

P.O. Box 3623

503-808-2188 dguenther@fs.fed.us Fire History points 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. 0.0000.000 20080811 20080801 None Scheduled. Connie Rawson Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture Data Adminstrator Assistant mailing and physical address

Deschutes National Forest, Bend Fort Rock Ranger District

Bend Oregon 97701 USA

1230 NE 3rd, Suite A-262

(541) 383-4767 (541) 383-4700 crawson@fs.fed.us FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time Unclassified enhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile 2009062309271500FALSE20091117150631002009111715063100{7AC2ACBE-3A3A-4AD6-892E-67A3F6B044E8}FeatureClassToFeatureClass T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt T:\FS\NFS\R06\Program\ResourceInfoMgmt\GIS\CSA2\Workspace\angigi\Converting_lib\Wil\shapefiles firehistorypt.shp # "NIFMID_CN 'NIFMID_CN' true true false 34 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,NIFMID_CN,-1,-1;NIFMID_LNK 'NIFMID_LNK' true true false 17 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,NIFMID_LNK,-1,-1;FIRE_NAME 'FIRE_NAME' true true false 34 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,FIRE_NAME,-1,-1;FIRE_DAY 'FIRE_DAY' true true false 2 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,FIRE_DAY,-1,-1;FIRE_MONTH 'FIRE_MONTH' true true false 2 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,FIRE_MONTH,-1,-1;FIRE_YEAR 'FIRE_YEAR' true true false 4 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,FIRE_YEAR,-1,-1;DATA_SOURC 'DATA_SOURC' true true false 34 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,DATA_SOURCE_TEXT,-1,-1;COST 'COST' true true false 4 Long 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,COST,-1,-1;LOCAL_NUMB 'LOCAL_NUMB' true true false 8 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,LOCAL_NUMBER,-1,-1;CAUSE 'CAUSE' true true false 2 Short 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,CAUSE,-1,-1;REPORTED_A 'REPORTED_A' true true false 8 Double 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,REPORTED_ACRES,-1,-1;SIZE_CLASS 'SIZE_CLASS' true true false 1 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,SIZE_CLASS,-1,-1;AGENCY 'AGENCY' true true false 3 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,AGENCY,-1,-1;COMMENTS 'COMMENTS' true true false 60 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,COMMENTS,-1,-1;R6_FID 'R6_FID' true true false 30 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,R6_FID,-1,-1;UNIT 'UNIT' true true false 4 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,UNIT,-1,-1;LINKFLAG 'LINKFLAG' true true false 10 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,LINKFLAG,-1,-1;REV_DATE 'REV_DATE' true true false 8 Date 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,REV_DATE,-1,-1;DATA_SOU_1 'DATA_SOURCE' true true false 2 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,DATA_SOURCE,-1,-1;ACCURACY 'ACCURACY' true true false 8 Double 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,ACCURACY,-1,-1;NIFMID_L_1 'NIFMID_L_1' true true false 17 Text 0 0 ,First,#,T:\FS\Reference\GIS\r06_wil\Data\FireHistory.mdb\FireManagement\FireHistoryPt,NIFMID_LNK_OLD,-1,-1" # T:\FS\NFS\R06\Program\ResourceInfoMgmt\GIS\CSA2\Workspace\angigi\Converting_lib\Wil\shapefiles\firehistorypt.shpMicrosoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.3000firehistorypt364596.7455941.2226561200176.3699221038385.1162111-122.979981-121.77885344.85299943.3742511ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\ds.fs.fed.us\EFS\\FS\NFS\R06\Program\ResourceInfoMgmt\GIS\CSA2\Workspace\angigi\Converting_lib\Wil\shapefiles\firehistorypt.shpLocal Area Network0.000ShapefileNAD_1983_Oregon_Washington_Albers020091117