S_R06.FireHistoryPl

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
Data Resource Management/Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Publication_Date: 20090624
Title: S_R06.FireHistoryPl
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage:
Server=oracle-idb.pdx; Service=5151; User=s_r06$design; Version=SDE.DEFAULT
Description:
Abstract:
Fire History polygons represent the final mapped wildfire perimeter. These data are maintained at the Forest / District level to track the area affected by fire.
Purpose:
This data set was created to achieve consistant data, throughout Region 6, for management, planning or analysis involving fire history. Historical Fire Perimeters is a geospatial derivitive of each National Forest's Historical Fire record, of the final forest fire boundaries. It was during 2006 when Region 6 Data Resource Management Data Standardization Team, collected all the spatial data available from each National Forest, in the Pacific Northwest Region. To maintain consistancy throughout Region 6, one standardized data set of the entire Region was created.
Supplemental_Information:
Fire History polygons represent the area which the wildfires burned. Wildfire data is collected and maintained at the Forest and or District level to aid in tracking the areas affected by fire. This data set was compiled by requesting each National Forests individual fire history coverage data, then standardizing the data according to the Forest Service National Data Dictionary Standards, Fire Management Theme, Fire History Layer, dated June 30, 2003. The data collected is from the years 780 until present. Two National Forests, the Olympic and Mt. Baker-Snoqualmie, had scientists from their PNW Labs do extensive research using carbon dating techniques to determine fire years for pre 1800 fire perimeters. The Gifford Pinchot and Siuslaw National Forests did not have Fire History spatial data of fire boundaries at the time this data set was created. The majority of the forests collected their data using UTM Coordinates in Zone 10. Those forests using UTM Zone 11 was MAL, UMA, and WAW. The forests who used TM Coordinates were GIP, WIN, COL, and WEN. The only forest using LCC Coordinates was OKA. Initially all forests used NAD1927 datum. Beginning in 2007 data maintenance procedures follow the R6 Fire History edit guide and are annually coordinated through Fire and Aviation Management / Data Resources Management at the Regional level.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20100101
Range_of_Dates/Times:
Beginning_Date:
Data begins with 780, for those carbon dated, otherwise the beginning year is 1800.
Ending_Date: 2008
Currentness_Reference:
Dates are compiled; wildfire ignition was observed for years after 1800, and were determined scientifically for years before 1800.
Status:
Progress: Complete
Maintenance_and_Update_Frequency:
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.
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -124.948188
East_Bounding_Coordinate: -115.499410
North_Bounding_Coordinate: 49.092291
South_Bounding_Coordinate: 41.874934
Keywords:
Theme:
Theme_Keyword_Thesaurus: FSH 5109.14 - Individual Fire Report Handbook
Theme_Keyword: Fire History
Theme_Keyword: Fire Occurrence
Theme_Keyword: Historical Fire
Theme_Keyword: Fire
Theme:
Theme_Keyword_Thesaurus: FSH 5109.14 - Individual Fire Report Handbook
Theme_Keyword: Fire History
Theme_Keyword: Fire Occurrence
Theme_Keyword: Historical Fire
Theme_Keyword: Fire
Theme:
Theme_Keyword_Thesaurus: FSH 5109.14 - Individual Fire Report Handbook
Theme_Keyword: Fire History
Theme_Keyword: Fire Occurrence
Theme_Keyword: Historical Fire
Theme_Keyword: Fire
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Umpqua National Forest
Place_Keyword: Oregon
Place_Keyword: Pacific Northwest
Place_Keyword: Pacific Northwest Region
Access_Constraints: None
Use_Constraints:
The USDA Forest Service makes no claims, promises, or guarantees about the accuracy, completeness, or adequacy of the content; and expressly disclaims liability for errors and omissions. No warranty of any kind, implied, expressed or statutory, including but not limited to warranties of non-infringement of third party rights, title, merchantability, fitness for a particular purpose and freedom from computer virus, is given with respect to the contents or hyperlinks to other Internet resources. Reference to any specific commercial products, processes, or services, or the use of any trade, firm or corporation name is for the information and convenience of the public, and does not constitute endorsement or recommendation by the USDA Forest Service..
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Dale Guenther
Contact_Organization:
Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Contact_Position: Data Steward
Contact_Address:
Address_Type: mailing address
Address: USDA Forest Service - Pacific Northwest Region
Address: USDA Forest Service - Pacific Northwest Region
City: Portland
State_or_Province: Oregon
Postal_Code: 97208-3623
Country: USA
Contact_Voice_Telephone: (503) 808-2188
Contact_Electronic_Mail_Address: dguenther@fs.fed.us
Security_Information:
Security_Classification: Unclassified
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 1; ESRI ArcCatalog 9.2.2.1350

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
No tests for attribute accuracy were conducted. Only visual quality checking and cross checking between fire history data in Kansas City NIFMID Database, data from the fire history points and polygons, was conducted by Region 6 Data Resource Management (DRM) Data Standardization Team (DST), for questionable errors. DST communicated those questions to the responsible forest for verification and or correction. Maintenance cycle includes visual quality checking and cross checking between fire history data in Kansas City NIFMID Database.
Logical_Consistency_Report:
Region 6 Data Resource Management (DRM) Data Standardization Team (DST) used grouping queries to examine the proper spelling and standardization of all text fields, and made changes where necessary. Duplicate entries were eliminated when possible. This logical consistency report refers to the Initial dataset, which had a thorough QA/QC process.
Completeness_Report:
Region 6 Data Resource Management (DRM) Data Standardization Team (DST) used queries and concatenation of fields to populate empty required attribute fields. Where reported_acres and or size_class fields were empty, DST used GIS ArcInfo Software to calculate and fill those attribute fields. DST conducted a visual survey on the fire history data that was collected and standardized in 2005. This survey was used to determine attribute completeness, for each forest, in the region. Attribute completeness was only determined based on the mandatory item fields in the data set, which contained fire history data. No accuracy check was made on the quality of the data, only if data existed, in the mandatory fields. Forest overall attribute completeness levels vary across the region. Depending on individual forests, attribute completeness ranges anywhere from 90 percent complete, to not complete. Attribute completeness, when averaging across the whole Region was 50 percent. The Gifford Pinchot and Siuslaw National Forests do not have spatial data for fire polygons. This completeness report refers to the Initial dataset, which had a thorough QA/QC process.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report: No testing was conducted for positional accuracy.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Data Resources Managment/Fire and Aviation Management, National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Publication_Date: 20071228
Title:
S_R06.FireHistoryPl (Initial SDE Feature class and 2007 Maintenance Cycle)
Other_Citation_Details:
The data collected is from the years 780 until 2006. Two National Forests, the Olympic and Mt.Baker-Snoqualmie, had scientists from their PNW Labs do extensive research using carbon dating techniques to determine fire years for pre 1800 fires.
Source_Scale_Denominator: 1:24,000
Type_of_Source_Media: computer program
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 780
Ending_Time: 2006
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation:
S_R06.FireHistoryPl (Initial SDE Feature Class and 2007 Maintenance update including polygons for the years 780 through 2006).
Source_Contribution:
Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established. Standardization of local unit Fire History data was completed in 2005. The first update/maintenance cycle was completed on local unit Fire History data in 2007 this included fire history polygons through the 2006 Fire Season.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Data Resources Managment/Fire and Aviation Management, National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Publication_Date: 20071228
Title:
S_R06.FireHistoryPl (Initial SDE Feature class and 2007 Maintenance Cycle)
Source_Scale_Denominator: 1:24,000
Type_of_Source_Media: computer program
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20010101
Ending_Date: 20071231
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation:
S_R06.FireHistoryPl (Initial SDE Feature Class and 2007 Maintenance update including polygons for the years 780 through 2006).
Source_Contribution:
Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established. Standardization of local unit Fire History data was completed in 2005. The first update/maintenance cycle was completed on local unit Fire History data in 2007 this included fire history polygons through the 2006 Fire Season.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Data Resources Managment/Fire and Aviation Management, National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Publication_Date: 20071228
Title:
S_R06.FireHistoryPl (Initial SDE Feature class and 2007 Maintenance Cycle)
Source_Scale_Denominator: 1:24,000
Type_of_Source_Media: computer program
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20010101
Ending_Date: 20081231
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation:
S_R06.FireHistoryPl (Initial SDE Feature Class and 2007 Maintenance update including polygons for the years 780 through 2006).
Source_Contribution:
Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established. Standardization of local unit Fire History data was completed in 2005. The first update/maintenance cycle was completed on local unit Fire History data in 2007 this included fire history polygons through the 2006 Fire Season.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Data Resources Managment/Fire and Aviation Management, National Forests, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Publication_Date: 20071228
Title:
S_R06.FireHistoryPl (Initial SDE Feature class and 2007 Maintenance Cycle)
Source_Scale_Denominator: 1:24,000
Type_of_Source_Media: computer program
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20090401
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation:
S_R06.FireHistoryPl (Initial SDE Feature Class and 2007 Maintenance update including polygons for the years 780 through 2006).
Source_Contribution:
Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established. Standardization of local unit Fire History data was completed in 2005. The first update/maintenance cycle was completed on local unit Fire History data in 2007 this included fire history polygons through the 2006 Fire Season.
Process_Step:
Process_Description:
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.
Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established.
This is a list of the data files DST received from each forest during the Initial Standardization Process completed in 2005.
CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_1 shapefile (1992-2002) CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_2 shapefile (1992) CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_3 shapefile (1998) CRGNSA - 7/5/2005, Cathy Bauer sent fire_polys72005_4 shapefile (1993) GIP - 9/26/2005, Ron Pfeifer sent gp_firepl.e00 (Cover Not Usable) MBS - 7/20/2005, Paula James sent fh.e00 (1000-1990) MTH - 6/8/2005, used cover Rick Momsen standardized mthfirehis_pl.e00 (1982-1997) OLY - 6/21/2005, Scott Schreier sent fire_hist.e00 (780-1987) ROR - 7/20/2005, Carol Boyd sent fba_ror.e00 (1910-2003) SIS - 9/12/2005, Jody Thomas sent firehis_pl.e00 (1939-2002) UMP - 8/1/2005, Ed Hall sent ump_firehis_pl.e00 (1987-2003) WIL - 7/18/2005, Rosana Costello sent wil_firehist.e00 (1943-2003) DES - 6/8/2005, Dorothy Thomas sent des_fire.e00 (1800-2003) FRE - 8/8/2005, Laurie Campbell sent fre_fire_poly.e00 and fre_fires92.e00 (1922-1999) OCH - 6/8/2005, used cover Rick Momsen standardized ochfirehis_pl.e00 (1990-2002) WIN - 9/28/2005, Laurie Campbell sent fires-fph_d2b.e00 (1938-2004) MAL - 5/13/2005, Andrew Lacey sent firehis_pl_csa4.e00 (1900-2005) UMA - 5/13/2005, Andrew Lacey sent firehis_pl_csa4.e00 (1850-2005) WAW - 5/13/2005, Andrew Lacey sent firehis_pl_csa4.e00 (1910-2005) COL - 6/14/2005, Cindy Potestio sent firehis_pl_20021011.e00 (1909-2003) OKA/WEN - 5/9/2005, Pat Murphy sent firehist_oka.e00 (1910-2003)
This is a list of the data files DST received from each forest during the First Update Cycle completed in 2007.
CRGNSA - 8/6/2007, Cathy Bauer sent nsa_fire_hist_pl_03_06 shapefile MBS - 3/30/2007, Paula James sent firehis_pl_mbs_2006.e00 MTH - 3/30/2007, Jaimie Bradbury sent firehis_update_mth_2006.mdb OLY - 3/23/2007, Doug Sturhan sent firehis_update_oly_2006.e00 ROR - 7/26/2007, Jody Thomas sent fire2006.zip shapefile SIS - 6/5/2007, Jody Thomas sent fire_2005_updates_pl.e00 WIL - 5/25/2007, Rosana Costello sent firehis_pl_update_wil.zip geodatabase DES - 3/14/2007, Gini Stoddard said to retrieve cover from T:\ drive OCH - 3/23/2007, Bruce Wright sent fire_his.mdb MAL - 5/17/2007, Carolyn Winkler sent 2005_2006_firehis_pl shapefile UMA - 5/17/2007, Carolyn Winkler sent 2005_2006_firehis_pl shapefile WAW - 5/17/2007, Carolyn Winkler sent 2005_2006_firehis_pl shapefile COL - 3/22/2007, Cindy Potestio sent firehis_update_col_2006.mdb OKA/WEN - 3/29/2007, Pat Murphy sent firehis_pl_update_oka_wen_2006.e00
Source_Used_Citation_Abbreviation:
Each individual National Forest submitted data files to Region 6 Data Resource Management (DRM) Data Standardization Team (DST), for the Initial Standardization Phase and the 2007 Maintenance Cycle.
Process_Date: 20070601
Source_Produced_Citation_Abbreviation:
S_R06.FireHistoryPl (Initial SDE and 2007 Maintenance Polygons through 2006 fire season)
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Colleen Williams
Contact_Organization:
Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Contact_Position: Database Standardization Specialist
Contact_Address:
Address_Type: mailing address
Address: Wallowa-Whitman National Forest
Address: Wallowa-Whitman National Forest
City: Baker City
State_or_Province: OR
Postal_Code: 97814
Country: USA
Contact_Voice_Telephone: 541 523-1253
Contact_Electronic_Mail_Address: cmwilliams@fs.fed.us
Process_Step:
Process_Description:
Fire season 2007 polygon fire spatial location data was updated as part of a Pacific Northwest Region (R6)Fire History annual data maintenance reply due memo, dated April22,2008; file code 1390/5100; Subject Region6 Fire History and Fuel Treatment Data Maintenance. The R6 Fire History Edit Guide provides the detailed input and qa/qc instruction and guidance for this data maintenance cycle.
Pacific NW Forest in DRM Customer Service Area (CSA) Customer Service Area 1 Columbia River Gorge National Scenic Area-20080606-Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb Olympic-20080606-Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb Mt.Baker Snoqualmie-20080606-Firehistory_update_CSA1_NSA_OLY_MBS_2007.mdb Jeff Muehleck,GIS Analyst CSA1,360-956-2402,email muehleck@fs.fed.us Gifford Pinchot-20080811-firehistory_update_GIP_2007a.mdb & firehistory_update_GIP_2007b.mdb Irene Ward,GIS Analyst CSA1,509-395-3366,email iward@fs.fed.us Mt. Hood-20080702-firehistory_update_mth_2007.mdb Jaimie L. Bradbury,GIS Analyst CSA1,503-668-1779,email jbradbury@fs.fed.us Customer Service Area 2 Missing firehistory_update_fff_2007 (fff = Forest personal geodatabase) Rogue River-Siskiyou,Siuslaw,Umpqua,Willamette-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. Jody Thomas,GIS Analyst CSA2,541 471-6764,email jathomas01@fs.fed.us Customer Service Area 3 Deschutes-20080731-firehistory_update_CSA3_2007.mdb Fremont-Winema-20080731-firehistory_update_CSA3_2007.mdb Ochoco-20080731-firehistory_update_CSA3_2007.mdb Dorothy Thomas,GIS Analyst CSA3,541-383-5570,email dthomas04@fs.fed.us Customer Service Area 4 Umatilla-20080529-firehistory_update_csa4_2007.mdb WallowaWhitman-20080529-firehistory_update_csa4_2007.mdb Malheur-20080529-firehistory_update_csa4_2007.mdb Andrew Lacey, GIS Analyst CSA4,541 278-3976,email alacey@fs.fed.us
Customer Service Area 5 Colville-20080125-firehistory_update_col_2007.mdb Missing firehistory_update_fff_2007 (fff = Forest personal geodatabase) Okanogan and Wenatchee-Did not complete the steps as outlined in the Fire History edit guide. Step3-completing metadata,and step5-copy and file archive of update geodatabase. Therefore, their source information is undocumented. Cindi Potestio,GIS Analyst CSA5,509-738-7747,email cpotestio@fs.fed.us
Source_Used_Citation_Abbreviation:
Forest Geodatabase FireHistory_update_fff_2007.mdb or Forest features from local dataset,
Process_Date: 20080718
Source_Produced_Citation_Abbreviation: S_R06.FireHistoryPl (2008 Data Maintenance 2001-2007 Polygons)
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Debra Kroeger/Mike Braymen/CSA Fire Business Leads
Contact_Organization:
Data Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Contact_Position: Data Administrator/Geodatabase Design Coordinator/GIS Analyst
Contact_Address:
Address_Type: mailing address
Address: Grants Pass Interagency Office
Address: Grants Pass Interagency Office
City: Grants Pass
State_or_Province: OR
Postal_Code: 97526
Country: USA
Contact_Voice_Telephone: 541 471-6716
Contact_Electronic_Mail_Address: dkroeger@fs.fed.us
Process_Step:
Process_Description:
Fire season 2008 polygon fire spatial location data was updated as part of a Pacific Northwest Region (R6)Fire History Data Maintenance "reply due" May 29, 2009, File Code 1390/5100 memo dated February 27, 2009. The R6 Fire History Edit Guide provides the detailed input and qa/qc instruction and guidance for this data maintenance cycle. Pacific NW Forest in DRM Customer Service Area (CSA) Customer Service Area 1 Columbia Gorge National Scenic Area (CGNSA)-05/22/2009-csa1_Fire_09.gdb DRM Staff Jeff Muehleck360-956-2300 Data Steward CGNSA Staff Roland Rose 542 308-1700 Jeff processed two polygons for fires occuring in 2008 and prior that are not currently in the feature class. 100+ acre are required and 100- acre fires are optional Gifford Pinchot-04/16/2009-firehistory_update_GIP_2008.gdb DRM Staff Irene Ward509-395-3366 Fire Staff John Parsons360-891-5147 or 360-891-5000 Roberto Morganti, GIS Specialist workied with data steward John Parsons to create polygons for the historic large fires. NIFMID data was reviewed and used to populate attributes as available. Mt. Baker-Snoqualmie-CSA1_Fire_09.gdb DRM Staff Jeff Muehleck360-956-2300 Fire Staff N/A No 2008 Fire Perimeter Polygons for the MBS Mt. Hood-04/02/2009-firehistory_update_mth_2008.mdb DRM Staff JaimieBradbury503-668-1779 Fire Staff DebRoy503-668-1756 Editor Jaimie L. Bradbury. Local data steward Jim Wrightson. Fire perimeters acquired from Incident Team GIS specialist or downloaded from <ftp://ftp.nifc.gov/Incident_Specific_Data/PACIFIC_NW>. Includes Gnarl Ridge, Lake Lenore (AKA Schreiner Peak). Attributes entered from NIFMID. Olympic-CSA1_Fire_09.gdb DRM Staff Jeff Muehleck360-956-2300 Fire Staff N/A No 2008 Fire Perimeter Polygons for the Olympic
Customer Service Area 2 (Jody Thomas-Completed update for entire CSA2) Rogue River-Siskiyou-05/22/2009-Firehistory_update_2008(not archived) DRM Staff-Jody Thomas541.471-6764 Fire Staff-DaveWickwire541.899-3800 Siuslaw-05/22/2009-Firehistory_update_2008(not archived) DRM Staff-Jody Thomas541.471-6764 Fire Staff-Dirk Shupe541.225-6405 Umpqua-05/22/2009-Firehistory_update_2008(not archived) DRM Staff-Jody Thomas541.471-6764 Fire Staff-Liza Castelberry541.957-3305 Willamette-05/22/2009-Firehistory_update_2008(not archived) DRM Staff Jody Thomas541.471-6764 Fire Staff-Dirk Shupe541.225-6405 Three Unknown fires on the Willamette were labeled and assigned the correct year. Fire perimeters for the Rogue River Siskiyou, Umpqua, and Willamette National Forest were added into S_R06.FireManagment Feature dataset into the feature class of S_R06.FireHistoryPl and links established and validated with the records for these forests in the S_R06.FIRE_NIFMID table. In the spring of 2009, this information was received in the form of a shapefile from the data stewards of each of CSA forest.
Customer Service Area 3 (Dorothy Thomas completed update for entire CSA3) Deschutes-06/24/2009-firehistory_update_DES_OCH_FRE_WIN_2008.gdb DRM Staff-Dorothy Thomas541.383-5570 Fire Staff-Bill Johnson541.383-5435 Fremont-Winema-06/24/2009-firehistory_update_DES_OCH_FRE_WIN_2008.gdb DRM Staff-Dorothy Thomas541.383-5570 Fire Staff-Clint Alberson541.947-6113 Ochoco-06/24/2009-firehistory_update_DES_OCH_FRE_WIN_2008.gdb DRM Staff-Dorothy Thomas541.383-5570 Fire Staff-David Owens541.416-6425 Large Fires identified from the NIFMID table, local contacts provided polygons, attributes populated by linking to NIFMID table.
Customer Service Area 4 Malheur Umatilla-03/09/2009 Firehistory_pt_update_WWF_2007 DRM Staff Andrew Lacey 547.278-9730 Projected Shape file was created by merging 2 GPSed cleaned up shape files of the fire perimeters. This shape file was then loaded into a version of the firehistory_pl feature class in CITRIX arc catalog. The resulting added polygons were then posted to the Default version by the SDE Manager. Data Steward delegated review roles to DRM for the purpose of this update Wallowa-Whitman
Customer Service Area 5 Colville-No 2008 Polygons for update. Okanogan and Wenatchee-06/24/2009-Firehistory_update_OKA_WEN_2008.gdb DRM Staff-Jack Rainford509.682-4944 Updated Large Fires for 2008
Source_Used_Citation_Abbreviation:
Forest Geodatabase FireHistory_update_fff_2008.gdb and/or SDE Version Editting
Process_Date: Unknown
Source_Produced_Citation_Abbreviation: S_R06.FireHistoryPl (2009 Maintenance Cycle 2001-2008 Polygons)
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Debra Kroeger/Chris Strobl/CSA Fire Business Leads
Contact_Organization:
Data Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Contact_Position: Data Administrator,Data Standardization Specialist/GIS Analyst
Contact_Address:
Address_Type: mailing address
Address: Grants Pass Interagency Office
Address: Grants Pass Interagency Office
City: Grants Pass
State_or_Province: OR
Postal_Code: 97526
Country: USA
Contact_Voice_Telephone: 541 471-6716
Contact_Electronic_Mail_Address: dkroeger@fs.fed.us
Process_Step:
Process_Description:
NIFMID_LNK field updated to reflect FIRESTAT_LNK field in the FIRE_NIFMID table to enable linking between datasets. See enclosed scripts to be run in order #1, then #2 and finally #3. This changes the field for Forest Service occurences only where previously it started with USF and now must start with FS.
Source_Used_Citation_Abbreviation: S_R06.FIRE_NIFMID (Table)
Process_Date: 20090401
Source_Produced_Citation_Abbreviation: S_R06.FireHistoryPl (Feature Class)
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chris Strobl
Contact_Organization:
Data Resources Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Contact_Position: GIS Data Standardization Analyst
Contact_Address:
Address_Type: mailing address
Address: Forest Service, Pacific Northwest Regional Office
Address: Forest Service, Pacific Northwest Regional Office
City: Portland
State_or_Province: OR
Postal_Code: 97208-3623
Country: USA
Contact_Voice_Telephone: 503 808-2649
Contact_Electronic_Mail_Address: cstrobl@fs.fed.us

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 4835

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 43.000000
Standard_Parallel: 48.000000
Longitude_of_Central_Meridian: -120.000000
Latitude_of_Projection_Origin: 34.000000
False_Easting: 600000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.100000
Ordinate_Resolution: 0.100000
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: S_R06.FireHistoryPl
Entity_Type_Definition: INFO Polygon Attribute Table
Entity_Type_Definition_Source:
Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: NIFMID_CN
Attribute_Definition:
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.
Attribute_Definition_Source:
FSH 5109.14, Chapter 30(34); Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Generated Unique Code
Enumerated_Domain_Value_Definition:
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)
Enumerated_Domain_Value_Definition_Source:
Forest Service National Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer.
Attribute:
Attribute_Label: NIFMID_LNK
Attribute_Definition:
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.
Attribute_Definition_Source:
FSH 5109.14, Chapter 30(34); Forest Service GIS Data Dictionary (FSGDD), Fire Management Theme, Fire History Layer.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value:
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)
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
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.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute:
Attribute_Label: FIRE_NAME
Attribute_Definition:
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
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer, FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29, in the Local Information found in the top portion of the Individual Wildland Fire Report form.
Attribute_Domain_Values:
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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".
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: FIRE_DAY
Attribute_Definition:
The day of the month the geographic data represents. (Example: 07)
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, taken from the Discovery_Date, found in the Occurrence Block on Form FS-5100-29, Individual Wildland Fire Report.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 01-31
Enumerated_Domain_Value_Definition: Double digit number representing the day of the month.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute_Value_Accuracy_Explanation: Date
Attribute:
Attribute_Label: FIRE_MONTH
Attribute_Definition: The month the geographic data represents. (Example: 09)
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, taken from the Discovery_Date, found in the Occurrence Block on Form FS-5100-29, Individual Wildland Fire Report.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 01-12
Enumerated_Domain_Value_Definition: Double digit number representing the month of the year.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute_Value_Accuracy_Explanation: Date
Attribute:
Attribute_Label: FIRE_YEAR
Attribute_Definition:
The fire discovery year the geographic data represents. (Example: 2006)
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, taken from the Discovery_Date, found in the Occurrence Block on Form FS-5100-29, Individual Wildland Fire Report.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute_Value_Accuracy_Explanation: Date
Attribute:
Attribute_Label: DATA_SOURCE_TEXT
Attribute_Definition: Describes the source of spatial data collection used.
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: GPS
Enumerated_Domain_Value_Definition: Global Positioning System
Enumerated_Domain_Value_Definition_Source:
Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer.
Enumerated_Domain:
Enumerated_Domain_Value: IR
Enumerated_Domain_Value_Definition: Infrared
Enumerated_Domain_Value_Definition_Source:
Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer.
Enumerated_Domain:
Enumerated_Domain_Value: HD
Enumerated_Domain_Value_Definition: Hand Drawn
Enumerated_Domain_Value_Definition_Source:
Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer.
Enumerated_Domain:
Enumerated_Domain_Value: PI
Enumerated_Domain_Value_Definition: Photo Interpretation
Enumerated_Domain_Value_Definition_Source:
Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer.
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:IKONOS imagery from 07/07/00
Enumerated_Domain_Value_Definition:
Describe the source data. Be consistent and as specific as possible when describing OTHER data sources.
Enumerated_Domain_Value_Definition_Source:
Forest Service National Data Dictionary, Fire Management Theme, Fire History Layer.
Enumerated_Domain:
Enumerated_Domain_Value: GPS-IDT
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: GPS-IMT
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: MAP
Enumerated_Domain_Value_Definition_Source: Fremont National Forest
Enumerated_Domain:
Enumerated_Domain_Value: MAP_PHOTO
Enumerated_Domain_Value_Definition_Source: Fremont National Forest
Enumerated_Domain:
Enumerated_Domain_Value: MAP_PHOTO_GPS
Enumerated_Domain_Value_Definition_Source: Fremont National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:BIFZ
Enumerated_Domain_Value_Definition: Burns Interagency Fire Zone (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:BUFIREPTS
Enumerated_Domain_Value_Definition: Burns BLM District Fire Points
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:EMI
Enumerated_Domain_Value_Definition: Emigrant Creek Ranger District Fire Points (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:KCFAST
Enumerated_Domain_Value_Definition: USFS KCFAST National Fire Database (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:MAF
Enumerated_Domain_Value_Definition: Malheur National Forest (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:NIFMID
Enumerated_Domain_Value_Definition: KCFAST National Fire Database (compiled by USFS)
Enumerated_Domain_Value_Definition_Source: Malheur, Umatilla, and Wallowa-Whitman National Forests
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:NIFMID_BLM
Enumerated_Domain_Value_Definition: BLM NIFMID National Fire Database
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:ODF
Enumerated_Domain_Value_Definition: Oregon Department of Forestry (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:PCHA
Enumerated_Domain_Value_Definition: PCHA Database
Enumerated_Domain_Value_Definition_Source: Ochoco and Olympic National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:PCHC
Enumerated_Domain_Value_Definition_Source: Olympic National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:SM
Enumerated_Domain_Value_Definition: Snow Mountain Ranger District fire points (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:STATE
Enumerated_Domain_Value_Definition: State of Oregon (compiled by BLM)
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:REM
Enumerated_Domain_Value_Definition_Source: Malheur National Forest
Enumerated_Domain:
Enumerated_Domain_Value: OTHER:Scientific Used Carbon Dating
Enumerated_Domain_Value_Definition:
PNW Scientists used carbon dating techniques to determine year burned.
Enumerated_Domain_Value_Definition_Source:
DST created this code for polygon data on the Olympic and Mt. Baker-Snoqualmie National Forests.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: COST
Attribute_Definition:
Cost of suppression to the nearest dollar. $2,000,000 was spent on fire. (example: 2000000)
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29, found in the Description Block on the Individual Wildland Fire Report form.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
Round to the nearest dollar. The matching field found in the NIFMID database at Kansas City is Fire_Cost_In_Dollars.
Attribute_Value_Accuracy_Explanation: Dollars
Attribute:
Attribute_Label: LOCAL_NUMBER
Attribute_Definition:
The Fire Number, required in NIFMID, is a three digit number assigned to the fire by the Forest Supervisor's Office. (Example: 090)
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
Matching field in NIFMID database in Kansas City is Fire_Number.
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: CAUSE
Attribute_Definition:
Use Coding for "Statistical Cause" code, a one digit number (numbers 1-9) that identifies the broad statistical cause for the fire.
Attribute_Definition_Source:
Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29, found in the Occurrence Block on the Individual Wildland Fire Report form.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Lightning
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: Equipment Use
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition: Smoking
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 4
Enumerated_Domain_Value_Definition: Campfire
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition: Debris Burning
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: Railroad
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition: Arson
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition: Children
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition: Miscellaneous
Enumerated_Domain_Value_Definition_Source:
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.
Attribute:
Attribute_Label: REPORTED_ACRES
Attribute_Definition:
Final acreage as reported on the final Incident Command System Status Report 209.
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer. FSH 5109.14 Individual Fire Report Handbook, Form FS-5100-29, found in the Description Block of the Individual Wildland Fire Report form.
Attribute_Domain_Values:
Unrepresentable_Domain:
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.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute:
Attribute_Label: SIZE_CLASS
Attribute_Definition:
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.
Attribute_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: A
Enumerated_Domain_Value_Definition: 0 to .25 Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Enumerated_Domain:
Enumerated_Domain_Value: B
Enumerated_Domain_Value_Definition: .26 to 9.9 Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Enumerated_Domain:
Enumerated_Domain_Value: C
Enumerated_Domain_Value_Definition: 10 to 99.9 Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Enumerated_Domain:
Enumerated_Domain_Value: D
Enumerated_Domain_Value_Definition: 100 to 299.9 Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Enumerated_Domain:
Enumerated_Domain_Value: E
Enumerated_Domain_Value_Definition: 300 to 999.9 Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Enumerated_Domain:
Enumerated_Domain_Value: F
Enumerated_Domain_Value_Definition: 1000 to 4999.9 Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Enumerated_Domain:
Enumerated_Domain_Value: G
Enumerated_Domain_Value_Definition: 5000+ Acres
Enumerated_Domain_Value_Definition_Source: FSH 5109.32a/NWCG Handbook 3 (PMS 410-1).
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
Where this field was blank, GIS was used to calculate SIZE_CLASS, using REPORTED_ACRES.
Attribute:
Attribute_Label: AGENCY
Attribute_Definition:
Protecting Agency of Record at Origin legally responsible to provide primary protection for the land on which the fire started.
Attribute_Definition_Source:
FSH 5109.14 Individual Fire Report Handbook, found in the Identification Block on Form FS-5100-29, Individual Wildland Fire Report.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: AFS
Enumerated_Domain_Value_Definition: Department of Defense, Air Force
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: ARM
Enumerated_Domain_Value_Definition: Department of Defense, Army
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: BIA
Enumerated_Domain_Value_Definition: USDI, Bureau of Indian Affairs
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: BLM
Enumerated_Domain_Value_Definition: USDI, Bureau of Land Management
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: DNR
Enumerated_Domain_Value_Definition: Washington Department of Natural Resources (State)
Enumerated_Domain_Value_Definition_Source:
Dale Guenther approved the code for Washington State, Department of Natural Resources, DNR.
Enumerated_Domain:
Enumerated_Domain_Value: FWS
Enumerated_Domain_Value_Definition: USDI, Fish and Wildlife Services
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: ID
Enumerated_Domain_Value_Definition: State Lands in Idaho
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: NAV
Enumerated_Domain_Value_Definition: Department of Defense, Navy
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: NOP
Enumerated_Domain_Value_Definition: No Protection
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: NPS
Enumerated_Domain_Value_Definition: USDI, National Park Service
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: ODF
Enumerated_Domain_Value_Definition: Oregon Department of Forestry (State)
Enumerated_Domain_Value_Definition_Source:
Dale Guenther approved the code for Oregon State, Department of Forestry, ODF.
Enumerated_Domain:
Enumerated_Domain_Value: OR
Enumerated_Domain_Value_Definition: State Lands in Oregon
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: OTH
Enumerated_Domain_Value_Definition: Other Federal Agency Land
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: PVT
Enumerated_Domain_Value_Definition: Private Land
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: FS
Enumerated_Domain_Value_Definition: USDA, Forest Service
Enumerated_Domain_Value_Definition_Source:
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.
Enumerated_Domain:
Enumerated_Domain_Value: WA
Enumerated_Domain_Value_Definition: State Lands in Washington
Enumerated_Domain_Value_Definition_Source:
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.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
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.
Attribute:
Attribute_Label: COMMENTS
Attribute_Definition: Open text field for additional information.
Attribute_Definition_Source:
Forest Service GIS Data Dictionary, Fire Management Theme, Fire History Layer.
Attribute:
Attribute_Label: R6_FID
Attribute_Definition: Unique Forest Identification Code.
Attribute_Definition_Source:
This field is open for use by individual forests, which have a unique number, necessary to link Fire History data to local forest records.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
Temporarily, only if this field is not being used by the forest, this field is holding the UNIT information, which is the four digit number code for Region and Forest. (Example: 0609)
Attribute_Value_Accuracy_Explanation:
Once the UNIT item field is added to this feature class, this information will no longer be held in this field.
Attribute:
Attribute_Label: NIFMID_LNK_OLD
Attribute_Definition:
This field is a copy of the original NIFMID_LNK field, as it was originally created, during the standardization process.
Attribute_Definition_Source:
This field was created by DRM. It is being kept to track when the NIFMID_LNK is changed, and will probably go away when it no longer serves any usefulness.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: LINKFLAG
Attribute_Definition:
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.
Attribute_Definition_Source:
This field was created by DRM, and will probably go away when it no longer serves any usefulness. The initial use has been checking the link between the point fire history dataset and NIFMID data in Kansas City.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: DBL LINK
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: DUP
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: GOOD
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: GOOD1 DATE
Enumerated_Domain_Value_Definition:
Data from FireHistory only matches on the date field with KC NIFMID data, has not other data to match to.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: GOOD1, GOOD2, GOOD3, GOOD4, GOOD5, GOOD6
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: NO DATE
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: NO LINK
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: NON FS DUP
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: NON FS
Enumerated_Domain_Value_Definition: The AGENCY field in FireHistory is not coded USF.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: NOT IN KC
Enumerated_Domain_Value_Definition:
Item has a spatial location in FireHistory, as well as attribute data, but not found in KC NIFMID database.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: YEAR ONLY
Enumerated_Domain_Value_Definition:
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.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Enumerated_Domain:
Enumerated_Domain_Value: PRIOR KC
Enumerated_Domain_Value_Definition:
FireHistory spatial data with FIRE_YEAR before 1970. Kansas City NIFMID database only has data from 1970 to present.
Enumerated_Domain_Value_Definition_Source:
Created by DRM to aid in quality checking of the attribute data, and linking ability with NIFMID data in Kansas City (KC).
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
Code represents the quality of the data and how good the link to NIFMID database in Kansas City is.
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: REV_DATE
Attribute_Definition: This is the date of feature creation or latest update.
Attribute_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: The proper date entry format is MM/DD/YYYY
Attribute:
Attribute_Label: DATA_SOURCE
Attribute_Definition:
The Data Source is the source of the geographic position of the arc, polygon, or point. Each Data Source code description contains information on the data used to derive features.
Attribute_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 01
Enumerated_Domain_Value_Definition: Original CFF
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 02
Enumerated_Domain_Value_Definition: GPS - Uncorrected Data
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 03
Enumerated_Domain_Value_Definition: GPS - Differentially Corrected Data
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 04
Enumerated_Domain_Value_Definition: GPS Survey Grade and Sub-meter
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 05
Enumerated_Domain_Value_Definition: Resurvey Plat
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 06
Enumerated_Domain_Value_Definition: Photogrammetric Compilation
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 07
Enumerated_Domain_Value_Definition: Digitized From Hardcopy PBS/SEQ
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 08
Enumerated_Domain_Value_Definition: Digitized From Hardcopy Orthophoto quad
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 09
Enumerated_Domain_Value_Definition: Automated Lands Project (ALP)
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 20
Enumerated_Domain_Value_Definition: Digitized Other
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 21
Enumerated_Domain_Value_Definition: Geographic Coordinate Database (GCDB)
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 22
Enumerated_Domain_Value_Definition: Other Cadastral Information
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 23
Enumerated_Domain_Value_Definition: Other Agency Digital
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 24
Enumerated_Domain_Value_Definition: Other
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 30
Enumerated_Domain_Value_Definition: Remote Sensing Data - Base Level
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 31
Enumerated_Domain_Value_Definition: Remote Sensing Data - Mid Level
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 32
Enumerated_Domain_Value_Definition: Remote Sensing Data - Broad Level
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Enumerated_Domain:
Enumerated_Domain_Value: 33
Enumerated_Domain_Value_Definition: Remote Sensing Data - National Level
Enumerated_Domain_Value_Definition_Source:
This is a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field and Code Definitions.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy:
Where the DATA_SOURCE_TEXT code was only GPS, the number code of 02 for GPS - Uncorrected Data was used because there was no indication the data was corrected. If a code was entered, but not found in the Code Table, the number code of 24 was used. All fields that had no DATA_SOURCE_TEXT information is coded 24.
Attribute_Value_Accuracy_Explanation:
Go to web location for complete explanation, www.fs.fed.us/gac/metadata/feature_level.html.
Attribute:
Attribute_Label: ACCURACY
Attribute_Definition:
This is the accuracy of the spatial location of the data. The expected difference between feature and real world object location.
Attribute_Definition_Source:
This is not a required field according to the Forest Service Metadata Users Guide for Feature Level Metadata, found at www.fs.fed.us/gac/metadata/feature_level.html. Go to this web location for a complete description of this field.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy_Explanation: Go to web location for complete description.
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: UNIT
Attribute_Definition:
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)
Attribute_Definition_Source: Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy_Explanation: Identifies ownership of each feature object.
Attribute:
Attribute_Label: SHAPE_Length
Attribute_Definition: Length of feature in internal units.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: SHAPE_Area
Attribute_Definition: Area of feature in internal units squared.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Detailed_Description:
Entity_Type:
Entity_Type_Label: S_R06.FireHistoryPl_NIFMID_J
Entity_Type_Definition:
This is a table join. Joining tables is appending the fields of one table to those of another through an attribute or field common to both tables. A join is usually used to attach more attributes to the attribute table of a geographic layer. This join is joining the attribute fields from the polygon spatial data, table S_R06.FireHistoryPl, with the attribute fields from the NIFMID database, table S_R06.Fire_NIFMID, by using the field common to both, NIFMID_LNK from the fire NIFMID database table and FIRESTAT_LNK from the Fire History point spatial data table.
Entity_Type_Definition_Source:
If you need additional information on table joins, use ArcMap Help, About Joining Attribute Tables.
Overview_Description:
Entity_and_Attribute_Overview:
TWO PROCESS STEP SUMMARIES FOLLOW HERE, ONE FOR 2005 FOLLOWED BY THE UPDATE PROCESS OF 2007.
METADATA SUMMARY OF ATTRIBUTE CODING USED BY DST DURING THE INITIAL FIRE HISTORY STANDARDIZATION PROCESS IN 2005.
The black normal font text in this document is taken from the GIS Core Data Dictionary, June 30, 2003. The (text inside parenthesis) indicates where, why and what changes were made during the standardization process by DST, which is not documented in the GIS Core Data Dictionary standards.
NIFMID_CN - Control number generated in Oracle to uniquely identify each fire across all Forest Service Units. These control numbers are only generated by FIRESTAT, for fires reported to the NIFMID database in Kansas City. Other fires included in this cover will have a null value for this field. Value Description: A unique code is generated by Oracle or a null value if the fire was not reported through FIRE STAT, to the NIFMID database. This field is populated from the Fire Stat database. This number can be found in the NIFMID Table under the column named FIRE_ID.
NIFMID_LNK - A unique 17 character code composed of concatenating Agency, unit, subunit, discovery year and fire number as downloaded from the National Fire Occurrence Database in Kansas City via KCFast. Value Description: Concatenation of Agency, unit, subunit, discovery year and fire number. These standards are from the KCFast application. Code example, AAARRFFYYYY######, where AAA is the Agency; RR is the Forest Service Region; FF is the Forest Number; YYYY is the Fire Discovery Year; and ###### is the Fire Number with leading zero's to make it a 6 character, zero filled field. (Example: USF06012006000022). All parts of this code are right justified and zero filled. This code is used as a link between SDE and the NIFMID database in Kansas City. FIRESTAT_LNK, found in the table S_R06.FIRE_NIFMID, is the linking field composed by concatenating the following fields from NIFMID, the National Fire Occurrence Database in Kansas City. Where AAA is PROTECTING_AGENCY, RR is REPORTING_FS_REGION, FF is REPORTING_FS_UNIT, YYYY is the year taken from DISCOVERY_DATE and ###### is the FIRE_NUMBER with leading zero's added to make it a 6 character, zero filled field. (According to direction given to DST by Dale Guenther, where this field is null, it will be populated using an AML created by DST. The AML will generate this field, using the covers item fields, by concatenating AGENCY, unit, subunit, FIRE_YEAR, and LOCAL_NUMBER. If any of these item fields are null, they will be zero filled.)
FIRE_NAME - The final name of the fire. Value Description: Name may contain text and/or numbers. (Because the FIRE_NAME was in all caps, mixed upper and lower case, had many symbols that could create problems within ArcGIS or in databases, this field was standardized. The AML used by DST contains a "Fix FIRE_NAME Routine" where it puts the fire name in proper case, rather then all Capitol letters. It removes any symbols like # & " _ . / from the fire name. The routine will also drop the word "Fire" from any fire name, as stated in FSH 5109.14 "Do not include the word "Fire" as part of the name", (e.g. Bear Fire would be Bear). Where FIRE_NAME is left blank, the field will be populated with "Unknown". Some examples of how names were changed follow below: )
FROM TO Eagle Fire Eagle #456 456 Crossing #5 Crossing 5 Blue Lake II Blue Lake 2 Major_Creek_2 Major Creek 2 LONESOME/MCPINE Lonesome-McPine "Avery" Avery FIRE #450 Fire 450 R&R FIRE R-R MCDONALD RIDGE McDonald Ridge Big One 1&2 Big One 1-2 COTTON-BEAVER CREEK Cotton-Beaver Creek A. Dean A Dean B. C. Fire BC Meadow Cr. Meadow Creek Snowshoe Sp. Snowshoe Spring John's Rdg. John's Ridge
FIRE_DAY - The day of the month that the geographic data represents. Value Description: Date that the data represents. Day must be zero-filled. If only the year is known, enter only the year and note the source in the comments field. (According to direction given to DST by Dale Guenther, this field can not be 00. If only the Month and Year is known enter 01 for the FIRE_DAY. If only the FIRE_YEAR is known leave this field blank.)
FIRE_MONTH - The month that the geographic data represents. Value Description: Date that the data represents. Month must be zero-filled. If only the year is known, enter only the year and note the source in the comments field. (According to direction given to DST by Dale Guenther, this field can not be 00. If only the Day and Year is known enter 01 for the FIRE_MONTH. If only the FIRE_YEAR is known leave this field blank.)
FIRE_YEAR - The year that the geographic data represents. Value Description: Date that the data represents. If only the year is known, enter only the year and note the source in the comments field. (According to direction given to DST by Dale Guenther, where this field had values like, 18yy, 18xx, or 19??, DST was instructed to use 1850 or 1900 with the comment "Exact fire year unknown", if there was room in the COMMENTS field.)
LOCAL_NUMBER - It is important to use the FIRE_NUMBER, that was used in NIFMID, on the fire report for this field. This is a confusing field, because the GIS Data Dictionary does not give a good definition, and this is the field used to create the NIFMID_LNK. The FIRE_NUMBER, required in NIFMID, is a three digit number assigned to the fire by the Forest Supervisor's Office. Many NIFMID_LNK numbers do not match, or link, with the NIFMID database because this number was incorrect.
(LOCAL_NUMBER - Clarification of LOCAL_NUMBER and the Fire Number used as the last 6 characters of the NIFMID_LNK. DST asked for clarification, because one is a 6 character field that is zero filled and LOCAL_NUMBER is a local identification number that is an 8 character field.) (Joe Frost gave this explanation. This issue comes up all the time and it is confusing. The NIFMID_LNK is the "smart key" used to link polygon data to the National Fire Statistics Database by using common information in both, the combination of AGENCY, Unit (region number), Sub-unit (forest number), FIRE_YEAR (discovery year), and Fire Number, provide a unique combination of values that will allow linking Polygon and Tabular data. If you do not have this basic information for each polygon then it is likely the fire which the polygon represents was not a statistical fire occurrence for a federal agency.) (Is the Fire Number the same as LOCAL_NUMBER? For the most part yes, but not always, the LOCAL_NUMBER leaves room for more flexibility and is defined as character, which allows the use of alpha numeric combinations, so the LOCAL_NUMBER can contain more information like which unit (District (D1), Supervisors Office (SO), etc.) issued the number. Ninety-eight percent of the time the LOCAL_NUMBER will match the Fire Number (I.E. local number SO-001 will equal fire number 000001)). (All statistical fire occurrences that are entered into the National Statistics Database must have a Fire Number assigned by the reporting unit. The LOCAL_NUMBER is not recorded in the National Fire Statistics Database and is for local use. The inclusion of the LOCAL_NUMBER in the National Data Standard, as an optional item, was to facilitate local linking of the polygon information to local tabular data. The LOCAL_NUMBER was requested by Region 8 because of the numbering system which they use on some units.) (Shouldn't the fields be the same length requirement in NIFMID_LNK (6 places) and LOCAL_NUMBER (8 places)? No, because there is only an assumed (not defined) relationship between the two fields. The Fire Number used in the NIFMID_LNK must be numeric and is required in the Fire Statistics Database. The LOCAL_NUMBER can contain a mix of alpha and numeric characters and is not required in the spatial data standard or in the Fire Statistics Database.)
REPORTED_ACRES - Acres reported are the final acreage, as reported, on the final Incident Command System Status Report 209. (According to direction given to DST by Dale Guenther, where this field is blank, use GIS to calculate acres in the fire polygon cover. The formula used was AREA multiplied by the acres conversion factor of 0.0002471054.)
SIZE_CLASS - Use coding as defined in the Fireline Handbook, FSH 5109.32a/NWCG Handbook 3 (PMS 410-1). Value Description: A is 0 to .25 Acres, B is .26 to 9.9 Acres, C is 10 to 99.9 Acres, D is 100 to 299.9 Acres, E is 300 to 999.9 Acres, F is 1000 to 4999.9 Acres and G is 5000+ Acres. (According to direction given to DST by Dale Guenther, where this field is blank, use GIS to calculate SIZE_CLASS, using REPORTED_ACRES.)
AGENCY - Use coding found in Individual Fire Report Handbook FSH 5109.14, Form FS-5100-29. Handbook definition for this field states, "Enter the letter code of the agency legally responsible to provide primary protection for the land on which the fire started." (Because there was no code for DNR - Department of Natural Resources, and Oregon State Forestry, DST asked Dale Guenther for coding. DST was instructed to "Please make a new field, label as State." DST initially coded the State fires as DNR for Washington State fires and STA for Oregon fires. DST revisited this coding issue and has learned that State fires in Oregon should most likely be coded ODF - Oregon Department of Forestry. DST has asked Dale Guenther to make a determination if DNR and ODF are the best codes, and to add these codes to the GIS Core Data Dictionary. DST received direction from Dale, on March 23, 2006, that ODF would be the appropriate acronym. Dale said he would work with Joe Frost to get these changes added to the Data Dictionary.)
R6_FID - Unique Forest Identification Code. This field is open for use by individual forests, which have a unique number, necessary to link Fire History data to local forest records.
THESE WERE THE EDIT/UPDATE PROCESS STEPS USED BY DST DURING THE 2007 MAJOR UPDATE CYCLE.
The Fire History, points and polygons, spatial data needs to link to the NIFMID database in Kansas City. Currently only points are in the Kansas City NIFMID database, but the polygon spatial data should contain the same NIFMID_LNK, as the points for linking purposes between SDE and NIFMID.
THE FIRST STEP, was to quality check all updates to assure attribute data conforms to the data standards. Verify, at minimum, all mandatory item fields contain data. Those fields are NIFMID_CN, NIFMID_LNK, FIRE_NAME, FIRE_DAY, FIRE_MONTH, FIRE_YEAR, and DATA_SOURCE. All updates will be in ALBERS, NAD83 projection and contain the standardized items as listed in the FS National GIS Data Dictionary for the INFO attribute tables as shown below.
NIFMID_CN NIFMID_LNK FIRE_NAME FIRE_DAY FIRE_MONTH FIRE_YEAR DATA_SOURCE COST LOCAL_NUMBER CAUSE REPORTED_ACRES SIZE_CLASS AGENCY COMMENTS R6_FID
NIFMID_LNK - where this field was null it was populated by concatenating the covers item fields, AGENCY, unit, subunit, FIRE_YEAR, and LOCAL_NUMBER. If any of these item fields are null, they were zero filled.
FIRE_NAME - Where data was available each individual fire making up a "Fire Complex", the name of the complex was identified in the COMMENTS field of each fire involved in that complex with a comment like " XYZ Complex fire". The word "Fire" was dropped from any fire name. Where the FIRE_NAME was in all caps, mixed upper and lower case, or had many different symbols, this field was standardized. All the fire names were put in proper case, and any symbols like # & " _ . / were removed from the fire name. The only "symbol" allowed is a hyphen or dash. Where FIRE_NAME was left blank, for fire perimeters, the field was populated with "Unknown".
FIRE_DAY - Where this field was not a two digit number, a preceding zero was added to the one digit number. A Domain was created to set allowable values for attributes in this field.
FIRE_MONTH - Where this field was not a two digit number, a preceding zero was added to the one digit number. A Domain was created to set allowable values for attributes in this field.
CAUSE - A Domain was created to set allowable values for attributes in this field.
REPORTED_ACRES - Where this field was blank, GIS was used to calculate acres using the fire polygons. Where acres were 0.01 through 0.09 the zero preceding the decimal point was dropped (example: 0.01 changed to 0.1). The formula used is AREA multiplied by the acres conversion factor of 0.0002471054.
SIZE_CLASS - Where this field was blank, used GIS to calculate SIZE_CLASS, using REPORTED_ACRES. A Domain was created to set allowable values for attributes in this field.
AGENCY - Dale Guenther approved the code for Washington Department of Natural Resources as DNR, and Oregon Department of Forestry as ODF. Dale said he would get these changes added to the Data Dictionary. The codes used in the fire history points and polygon spatial data in SDE, are inclusive of all codes. A Domain was created to set allowable values for attributes in this field.
R6_FID - This field is open for use by individual forests, which have a unique number, necessary to link Fire History data to local forest records. IMPORTANT NOTE: The item field UNIT needs to be added to the FireHistoryPl feature class in SDE. Until this happens, the UNIT code is being held in the R6_FID field temporarily, where it did not contain any forest data.
A "template" geodatabase was created, of each forest, to load their data in. This assured it was all in the standardized format, proper structure of the corporate feature data set, and also was to keep each forests updates separate to ease in the final update process to the existing data in SDE.
FIRST a File of the Database Structure was Created - From ArcCatalog, expand the Database Connections folder. Make a connection to SDE in Portland Data Center. Find the feature data set S_R06.FireManagement, Right click on it and choose Export > XML Workspace Document. Select Schema Only under "What do you want to export:", fill in the location and file name under "Specify the output XML file:", uncheck "Export Metadata", select Next. In the window under, "Choose which items you want to export", make sure only the Include box is checked for S_R06.FireHistoryPl and S_R06.FireHistoryPt, now click Finish. Right click on the SDE connection you made earlier, and choose Disconnect. Expand the local C:\ drive file directory and navigate to where you created the .xml file, you should see the file you just created. This file is used when creating the "empty template" geodatabase.
SECOND a Personal Geodatabase for Holding Updates was Created - Right click on folder where Personal Geodatabase will be created, choose New > Personal Geodatabase, rename geodatabase, (example: firehistory_update_FFF_YYYY.mdb, where FFF equals the forest's three letter abbreviation and YYYY the year the update is current to. In cases where the forests have been combined, like OKA/WEN, it would be firehistory_update_FFF_FFF_YYYY.mdb. If there are updates that span 2003-2006, the year entered would be 2006.)
Next, the structure of the database is added by importing the XML file created earlier. Right click on personal geodatabase just created, choose Import > XML Workspace Document, when Import XML Workspace Document window opens, leave Data checked and navigate to the .XML file created earlier, in the "Specify the XML source to import:" block, select Next and Finish. Refresh folder containing the firehistory_update.mdb, expand the folder and the firehistory_update.mdb geodatabase. There should now be a feature data set FireManagement, which contains two feature classes FireHistoryPl and FireHistoryPt. This personal geodatabase is now ready to load data into.
Now there are additional Fields in the geodatabase, just created, they are listed below (these are the same fields currently found in SDE):
OBJECTID (system field, do not edit) SHAPE (system field, do not edit) NIFMID_CN NIFMID_LNK FIRE_NAME FIRE_DAY FIRE_MONTH FIRE_YEAR DATA_SOURCE_TEXT COST LOCAL_NUMBER CAUSE REPORTED_ACRES SIZE_CLASS AGENCY COMMENTS R6_FID UNIT LINKFLAG REV_DATE DATA_SOURCE ACCURACY NIFMID_LNK_OLD SHAPE_Area (POLYGONS only, system field, do not edit) SHAPE_Length (POLYGONS only, system field, do not edit)
The definitions for the additional fields are listed below.
DATA_SOURCE_TEXT - This field contains the same information as the DATA_SOURCE field in your spatial geodatabase or coverage. During the data loading process you need to make sure the Matching Source Field for this item is changed to DATA_SOURCE.
UNIT - Enter the 4 digit number code for Region and Forest, or select from the list of allowable values. A Domain was created to set allowable values for attributes in this field.
LINKFLAG - This field was created and populated to determine how well the FireHistory data linked with the NIFMID data in Kansas City. Currently only the points have a LINKFLAG code.
REV_DATE - This is the date of feature creation or latest update, the proper date entry format is MM/DD/YYYY. This is a required field . DST entered either the date the update was received from the forest or the date DST made a change or addition if it was required as part of the standardization process.
DATA_SOURCE - This is a required field. A Domain was created to set allowable values for attributes in this field. Where the DATA_SOURCE_TEXT code was only GPS, the number code of 02 was used because there was no indication the data was corrected. If no DATA_SOURCE_TEXT code was entered, or was not found in the Code Table, the number code of 24 was used. All fields that have no DATA_SOURCE_TEXT should be coded as 24 - Other.
NIFMID_LNK_OLD - This field is a copy of the original NIFMID_LNK field, as it was created during the standardization process. When it was determined the NIFMID_LNK did not make a link to the Kansas City data, the NIFMID_LNK field was either corrected or deleted. This field is being kept to track when the NIFMID_LNK was changed, but will probably go away when it no longer serves any usefulness. If any new entries were added this field was calculated the same as NIFMID_LNK.
Loading Data Into firehistory_updates.mdb Geodatabase - If updates are in a coverage right click on FireHistoryPl, if polygons, or FireHistoryPt, if points, select Load > Load Data, the Simple Data Loader window opens, select Next, navigate to the update cover in the "Input data" block, from the "Open Geodatabase" window select the region feature class if polygons or select the point feature class if points, choose Open, select Add, once all covers are listed in the "List of source data to load" window, select Next, make sure "I do not want to load all features into a subtype." is checked, select Next. In this window is a Target Field and Matching Source Field. For each target field, select the source field that should be loaded into it. Check through the list of fields making the following changes, opposite the Target Field for DATA_SOURCE_TEXT, click on <None> in the Matching Source Field and select DATA_SOURCE from the drop down list; opposite the Target Field for NIFMID_LNK_OLD, click on <None> in the Matching Source Field and select NIFMID_LNK from the drop down list; opposite the Target Field for DATA_SOURCE, in the Matching Source Field make sure <None> is selected from the drop down list. Look through the Matching Source Field and if there are any with a <None>, check to be sure the same data may not be listed under a different Item or Field Name in the cover you're loading data from. Once you're done checking all the fields, select Next, check "Load all of the source data", select Next then Finish.
Editing the New Fields in the firehistory_updates.mdb Geodatabase - Open ArcMap, add the feature classes data was just loaded in. Open the attribute table of each feature class, make sure the new item fields are populated, by removing the <Null> value and entering the correct value for each field. The new fields needing to be populated are UNIT, REV_DATE, and DATA_SOURCE. Clear the <Null> value from the LINKFLAG field and anywhere else it may appear in the table. Check to make sure the DATA_SOURCE_TEXT field populated correctly. Make sure the COST field is populated where there were costs listed. Updates are moved to a folder on the T drive, create a new ArcMap project, and add the updates to it.
Before Applying the Updates To SDE YOU MUST know which of the updates are going to make changes to EXISTING spatial data in SDE. This SPATIAL data will need to be deleted from SDE BEFORE applying the updates. If changes are just attribute changes, in SDE, DST made those edits to the SDE Version Copy.
LOGIN to CITRIX, Open ArcCatalog, then open ArcMap from within ArcCatalog. This assures ArcCatalog and ArcMap are connected to the same server when they open. When opening ArcMap, create a new ArcMap, add the Version copy of S_R06.FireManagement, from SDE, the one having the edits and updates applied to it, it should have edit access privileges granted to you. All deletes, from the corporate data set in SDE, are completed first. All data being replaced, changed or updated, in some way, is easiest to delete the old version from SDE and replace with the new version in an update.
Loading Updates into SDE, Version Copy of S_R06.FireManagement from ArcMap, on the Editor Toolbar, make sure the Task is "Create New Feature" and the Target is S_R06.FireHistoryPl (Pl for polygon or Pt for point), click on the Selection tab, from the Table of Contents tabs at the bottom. Right click on the update layer, select "Make This The Only Selectable Layer", Right click on the update layer again and choose "Select All" (providing this update contains only updates otherwise you will need to make your selections). The update layer should now be highlighted with bold text, followed by parentheses containing the number of selected features. Click on Edit, from the Main Menu, and select Copy. Click on Edit again and select Paste (you can also use the Copy and Paste icons from the Edit Toolbar). Now you should see the Target layer is highlighted in bold text with the same number in parentheses after it as the update layer had, and the update layer is no longer highlighted. Choose "Clear Selected Features" under Selection on the Main Menu or by right clicking on the target layer and selecting it from the drop down menu. Continue in this manner until all updates are applied to the Version copy for editing.
Once all updates are applied to the Version copy, DST completed a QA/QC of the Version copy to assure all changes and updates were applied correctly.
DST then reviewed the metadata for each feature class and made sure metadata was updated where necessary to reflect the current state of the data set.

Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Dale Guenther
Contact_Organization:
Fire and Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
Contact_Position: Data Steward
Contact_Address:
Address_Type: mailing address
Address: Box 3623
City: Portland
State_or_Province: Oregon
Postal_Code: 97208-3623
Country: USA
Contact_Voice_Telephone: (503) 808-2188
Contact_Electronic_Mail_Address: dguenther@fs.fed.us
Resource_Description: Fire History polygons
Distribution_Liability:
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.

Metadata_Reference_Information:
Metadata_Date: 20080814
Metadata_Review_Date: 20080814
Metadata_Future_Review_Date: None scheduled.
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Regional Office - Pacific Northwest Region,
Contact_Person: Jody Thomas
Contact_Position: GIS Analyst
Contact_Address:
Address_Type: Mailing and physical
Address: 2164 NE Spalding Rd
City: Grants Pass
State_or_Province: OR
Postal_Code: 97526-
Country: USA
Contact_Voice_Telephone: (541) 471-6764
Contact_TDD/TTY_Telephone: ( ) -
Contact_Facsimile_Telephone: (541) 471-6512
Contact_Electronic_Mail_Address: jathomas01@fs.fed.us
Hours_of_Service: 8-5 M-F
Contact_Instructions:
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Security_Information:
Metadata_Security_Classification: Unclassified
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.9.6 on Mon Mar 19 16:42:43 2012