Fire History (Perimeters And Origins) Spatial Data Standard
State Data StandardsOR/WA Bureau of Land ManagementFIRE HISTORYSPATIAL DATA STANDARDFire History, Version 1.0July 26, 2013Page 1
State Data StandardsOR/WA Bureau of Land ManagementTABLE OF TITILEGeneral InformationRoles and ResponsibilitiesFOIA CategoryRecords Retention ScheduleSecurity/Access/SensitivityKeywordsData Set OverviewDescriptionUsageSponsor/Affected PartiesRelationship to Other DatasetsData Category/Architecture LinkRelationship to the Department of the Interior Enterprise Architecture –Data Resource ModelFire History Data Organization/StructureData Management ProtocolsAccuracy RequirementsCollection, Input, and Maintenance ProtocolsUpdate Frequency and Archival ProtocolsStatewide MonitoringFire History Schema (Simplified)FIRE POLYFIRE POINTProjection and Spatial ExtentSpatial Entity CharacteristicsAttribute Characteristics and DefinitionsACCURACY FTBLM ORG CDCAUSE CATCAUSE DETCLASSIFIERCOMMENTSCOMPLEX NAMECONTROL DATEFire History, Version 1.0July 26, 51515Page 2
State Data StandardsOR/WA Bureau of Land .197.207.217.227.237.24891011COORD DATECOORD SRCDISC TIMEFIRE CODEFIRE DSCRV DATEFIRE NAMEFIRE NUMFIRE YEARGIS ACRESINC IDLOCAL NUMOUT DATETOT ACRES RPTDUNIT IDWFMI IDVERSION NAMEAssociated Files or DatabasesLayer Files (Publication Views)Editing ProceduresOregon/Washington Data Framework Abbreviations and Acronyms Used in this Standard25AppendixAA.1Domains (Valid Values)26BLM ORG CD26A.2COORD SRC27A.3FIRE CAUSE CAT27A.4FIRE UNIT ID27Fire History, Version 1.0July 26, 2013Page 3
State Data StandardsOR/WA Bureau of Land Management1. GENERAL INFORMATIONDataset (Theme) Name: Fire History (Perimeters and Origins)Dataset (Feature Class): FIRE POLY, FIRE POINT1.1 ROLES AND RESPONSIBILITIESRolesState Data StewardsLead GIS SpecialistState DataAdministratorState RecordsAdministratorFire History, Version 1.0ResponsibilitiesThe State Data Steward, Dale Guenther, 503-808-2188, is responsible forapproving data standards and business rules, developing QualityAssurance/Quality Control procedures, identifying potential privacy issues,and ensuring that data is managed as a corporate resource. The State DataSteward coordinates with field office data stewards, the state dataadministrator, Geographic Information System (GIS) coordinators, andnational data stewards. The State Data Steward also reviews geospatialmetadata for completeness and quality.The Lead GIS Specialist, Barbara Haney, 503-808-2741, works with datastewards to convert business needs into GIS applications and derive datarequirements and participates in the development of data standards. TheGIS specialist coordinates with system administrators and GIS coordinatorsto manage the GIS databases. The lead GIS specialist works with dataeditors to make sure data is being input into the Spatial Database Engineconsistently and in accordance with the established data standard. The leadGIS specialist is a resource for the editors when they have questions orwhen they are new to editing a particular data set, and can help answerquestions about how to query and display the data set for mapping andanalysis.The State Data Administrator, Stanley Frazier, 503-808-6009, providesinformation management leadership, data modeling expertise, andcustodianship of the state data models. The State Data Administratorensures that defined processes for development of data standards andmetadata are followed, and that they are consistent and complete. TheState Data Administrator is responsible for making data standards andmetadata accessible to all users. The State Data Administrator alsocoordinates with data stewards and GIS coordinators to respond to nationalspatial data requests.The acting State Records Administrator, Jan McCormick, 503-808-6675,assists the State Data Steward to identify any privacy issues related tospatial data. The State Records Administrator also provides direction andguidance on data release and fees. The State Records Administrator alsoensures that data has been classified under the proper records retentionschedule and determines appropriate Freedom of Information Act category.Table 1 Role and ResponsibilitiesJuly 26, 2013Page 4
State Data StandardsOR/WA Bureau of Land Management1.2 FOIA CATEGORYPublic1.3 RECORDS RETENTION SCHEDULEGRS BLM 20/52 (Electronic Records/Geographic Information Systems)TEMPORARY. Delete when no longer needed for administrative, legal, audit, or other operationalpurposes (subject to any records freeze or holds that may be in place).1.4 SECURITY/ACCESS/SENSITIVITYThe Fire History set of themes do not require any additional security other than that provided by theGeneral Support System (the hardware/software infrastructure of the Oregon/Washington (OR/WA)Bureau of Land Management (BLM).This data is not sensitive and there are no restrictions on access to this data either from within the BLMor external to the BLM.There are or no privacy issues or concerns associated with these data themes.1.5 KEYWORDSKeywords that can be used to locate this dataset include: fire, wildfire, wildland fire, fire history, fireperimeters, and fire origins.2. DATASET OVERVIEW2.1 DESCRIPTIONThis dataset represents final perimeters (FIRE POLY) and origins (FIRE POINT) of fires that occurnaturally (e.g., lightning) or by humans accidentally (e.g., escaped campfire) or maliciously. The datasetincludes some, but not all, historic fire perimeters (fires declared ‘out’ in calendar years prior to thecurrent year). It is expected that the number of fire perimeters will continually grow as fires are addedwith each fire season and as more historic fire perimeters become available. There is no lower size limitfor fires to be included, although BLM does require capture of a final perimeter on fires 10 acres orlarger in Type 1 (BLM land protected by BLM) and Type 2 (BLM land protected by another Federalagency under a cooperative agreement or contract; including mutual aid agreements) scenarios. Singletree ignitions and extremely small fires are generally omitted from FIRE POLY and found only onFIRE POINT. In addition, while FIRE POINT contains fire origin points for most of the fires whoseperimeters are included on FIRE POLY, there are perimeters without a corresponding point;particularly for historic fires. Attributes for FIRE POLY and FIRE POINT are largely identical. Basicinformation including name, year, standard fire number and code, ignition cause, and collectioninformation comprise the attributes.Fire History, Version 1.0July 26, 2013Page 5
State Data StandardsOR/WA Bureau of Land Management2.2 USAGEThis dataset is used to display fires (both current and historic) on maps. The number and spatial extentof fires across the landscape is important information for natural resource management and planningactivities. Fire perimeters will be combined with a wide variety of other GIS datasets including habitatand special management areas for effects and impact analyses.2.3 SPONSOR/AFFECTED PARTIESThe sponsor for this data set is the Deputy State Director, Resource Planning, Use and Protection. Firesare assigned to a particular agency unit and so do not require interagency coordination for data captureor maintenance.2.4 RELATIONSHIP TO OTHER DATASETSBoth the BLM National Fire Program and the National Wildfire Coordinating Group have data standardson this same subject and this standard is designed so that translation to those standards can be easilydone. In addition, both of those standards are likely to be revised in Fiscal Year 2014 which may makerevisions to this standard necessary. This standard should be considered an interim standard until thosehigher level standard revisions are completed and any needed changes are made.The BURN dataset contains prescribed fire which is considered a land treatment and described in thetreatments data standard. Occasionally, a wildfire is controlled in a way that allows it to be used as atreatment and occasionally, a prescribed fire escapes and becomes a wildfire. Wildfires usually receivepost-fire treatments. The perimeter polygon may be duplicated on treatment datasets such as REVEG(revegetation). Firebreaks created in fire suppression are placed on the line structures dataset(STRCT ARC). Wildfire points of origin are obtained from each fire dispatch office’s WildfireComputer Aided Dispatch (WildCAD) application. Data from WildCAD is also put into the WildlandFire Management Information (WFMI) system, official repository for Department of the Interior (DOI)fire points of origin, the Fire Statistics System (FireStat), official repository for United States ForestService fire points of origin and other agency (including Oregon Department of Forestry) databases.Fire causes changes to vegetation and current landscape vegetative cover, and habitat datasets should beupdated with recent fire perimeters and modified as older fires revegetate.The FIRE POLY is equivalent to the national BLM Fire Occurrence and History Perimeter (FPER) datastandard and will be uploaded to this dataset annually or whenever requested. The attributes and spatialcharacteristics of FIRE POLY are designed for easy cross-walk to FPER. The FIRE POLY also agreeswith the interagency National Wildfire Coordination Group data standard.During the fire season, perimeters for ongoing incidents are posted to the National Interagency FireCenter file transfer site (ftp.nifc.gov) by fire team GIS specialists and other fire support entities such asthe Northwest Coordination Center. These perimeters are used by the United States Geological Survey(USGS) Geospatial Multi-Agency Coordination Group (Geomac), the interagency incident informationsystem Inciweb and other online mapping sites.Fire History, Version 1.0July 26, 2013Page 6
State Data StandardsOR/WA Bureau of Land ManagementThe BLM OR/WA fire perimeters can be added to FIRE POLY whenever necessary, but at least at theend of every fire season. It is assumed that updates to national and interagency databases andapplications such as Geomac, Landfire, and the Wildland Fire Decision Support System will be handledvia FPER.2.5 DATA CATEGORY/ARCHITECTURE LINKThese data themes are a portion of the Oregon Data Framework(2013 03 19 MC Statement Hennagin.pdf). The ODF utilizes the concept of inheritance to definespecific instances of data. All OR/WA resource-related data are divided into three general categories:Activities, Resources, and Boundaries. These general categories are broken into sub-categories thatinherit spatial characteristics and attributes from their parent category. These sub-categories may befurther broken into more specific groups until the basic data set that cannot be further sub-divided.Those basic data sets inherit all characteristics of all groups/categories above them. The basic data setsare where physical data gets populated (those groups/categories above them do not contain actual data,but set parameters that all data of that type must follow). See the ODF Overview (figure 2) for asimplified schematic of the entire ODF showing the overall organization and entity inheritance. TheWILDFIRE entities are highlighted. For additional information about the ODF, contact:OR/WA State Data AdministratorBureau of Land ManagementP.O. Box 2965Portland, OR 97208503-808-6009In the ODF, Wildfire is considered a natural resource and categorized as follows:ODFResourcesWildfireFIRE POLYFIRE POINT2.6 RELATIONSHIP TO THE DEPARTMENT OF THE INTERIOR ENTERPRISEARCHITECTURE - DATA RESOURCE MODELThe DOI’s Enterprise Architecture contains a component called the Data Resource Model. This modeladdresses the concepts of data sharing, data description, and data context. This data standard providesinformation needed to address each of those areas. Data sharing is addressed through completedocumentation and simple data structures which make sharing easier. Data description is addressedthrough the section on Attribute Descriptions. Data context is addressed through the data organizationand structure portions of this document. In addition, the DOI Data Resource Model categorizes data byuse of standardized Data Subject Areas and Information Classes. For this data set, the Data SubjectArea and Information Class are: Data Subject Area: Geospatial Information Class: LocationFire History, Version 1.0July 26, 2013Page 7
State Data StandardsOR/WA Bureau of Land Management2.7 FIRE HISTORY DATA ORGANIZATION / STRUCTUREFigure 1 Data Organization StructureFire History, Version 1.0July 26, 2013Page 8
State Data StandardsOR/WA Bureau of Land Management3. DATA MANAGEMENT PROTOCOLS3.1 ACCURACY REQUIREMENTSRequired attributes have an accuracy of at least 95 percent.Fire perimeters and points of origin have a wide range of positional accuracy due to the variety ofcapture methods (e.g., foot, ground vehicle, helicopter, infrared imagery) and often poor map records ofhistoric fires. Four attributes are included to provide accuracy information: COORD SRC for themethod, ACCURACY FT for the estimated error, COORD DATE for the date the coordinates werecollected, and CLASSIFIER for the source of the collected perimeter data.3.2 COLLECTION, INPUT, AND MAINTENANCE PROTOCOLSThe most common input methods for fire perimeters and points are Global Positioning System (GPS)coordinates or digitized from maps. There may be infrared imaging available to assist in refining theperimeter. It is usual that the perimeter will be updated daily or even hourly as the fire progresses. Onlythe final perimeter is retained in FIRE POLY. Intermediate fire progression polygons might be retainedin specific fire project directories and archived. It is unlikely that fire perimeters will be updated afterthe final perimeter is captured. Historic fires, however, may be added to or updated if better maprecords are found.Fires may and often do overlap older fires. An individual fire may consist of multiple unattachedpolygons. These polygon pieces should be stored as individual polygon records with common attributevalues not as multi-part polygons. In addition, there may be islands ("donut holes") of non-burned areasurrounded by burned area.The FIRE POINT (fire points of origin) coordinates and attributes are obtained from fire dispatchoffices or field fire fighters. The dispatch offices or other fire support staff are responsible for inputtingthe coordinates and other required information to WildCAD and WFMI, FireStat or other partner agencydatabases.3.3 UPDATE FREQUENCY AND ARCHIVAL PROTOCOLSData is updated as needed, but at least annually after fire season. Also, it is archived annually at the endof the fiscal year.3.4 STATEWIDE MONITORINGThe State Data Steward, in conjunction with the district Fire Management Officers, is responsible forchecking FIRE POLY and FIRE POINT against corresponding records in national databases forcompleteness and accuracy. In general, it is sufficient to check just the prior year’s fires, butoccasionally, a more thorough review (for example when there is a software or database transition) iswarranted.Fire History, Version 1.0July 26, 2013Page 9
State Data StandardsOR/WA Bureau of Land Management4. FIRE HISTORY SCHEMA (simplified)General Information: Attributes are listed in the order they appear in the geodatabase featureclass. The order is an indication of the importance of the attribute for theme definition and use.There are no aliases unless specifically noted. The domains used in this data standard can befound in Appendix A. These are the domains at the time the data standard was approved.Domains can be changed without a re-issue of the data standard. Many (but not all) of thedomains used in this data standard are available at the following web pFor domains not listed at that site contact:Stanley FrazierOR/WA State Data AdministratorBureau of Land ManagementP.O. Box 2965Portland, OR 97208503-808-60094.1 FIRE POLY (Fire Perimeter Polygons)Attribute NameDataTypeUNIT IDStringFIRE NUMStringFIRE CODEStringFIRE NAMEStringFIRE YEARStringCOMPLEX NAMEStringINC ID*StringWFMI IDIntegerBLM ORG CDStringFIRE DSCRV DATE StringCAUSE CATStringCAUSE DETStringCLASSIFIERStringCOORD SRCStringCOORD DATEStringACCURACY FTIntegerCOMMENTSStringTOT ACRES RPTD IntegerGIS ACRES*DecimalVERSION NAME*String*Automatically generatedFire History, Version 0DefaultValueUNK0InitialLoadJuly 26, oNoYesNoNoNoYesYes*Yes*dom FIRE UNIT IDdom BLM ORG CDdom FIRE CAUSE CATdom COORD SRCPage 10
State Data StandardsOR/WA Bureau of Land Management4.2 FIRE POINT (Fire Points of Origin)Attribute NameDataTypeUNIT IDStringFIRE NUMStringFIRE CODEStringFIRE NAMEStringFIRE YEARStringCOMPLEX NAMEStringWFMI IDIntegerINC ID*StringLOCAL NUMStringBLM ORG CDStringFIRE DSCRV DATE StringDISC TIMEStringCONTROL DTStringOUT DATEStringCAUSE CATStringCAUSE DETStringCLASSIFIERStringCOORD SRCStringCOORD DATEStringACCURACY FTIntegerCOMMENTSStringTOT ACRES RPTD IntegerVERSION NAME*String*Automatically oYesYes*dom FIRE UNIT IDdom BLM ORG CDdom FIRE CAUSE CATdom COORD SRC5. PROJECTION AND SPATIAL EXTENTAll feature classes and feature datasets are in Geographic, North American Datum 83. Units are decimaldegrees. Spatial extent (area of coverage) includes all lands managed by the BLM OR/WA. See themetadata for this data set for more precise description of the extent.Fire History, Version 1.0July 26, 2013Page 11
State Data StandardsOR/WA Bureau of Land Management6. SPATIAL ENTITY CHARACTERISTICSFIRE PERIMETER POLYGONS (FIRE POLY)Description: Instance of Fire group.Geometry: Polygons do not cover the landscape, nor do they cover all BLM lands continuously. Inaddition, there may be islands ("donut holes") of non-burned area surrounded by burned area. Anindividual fire may consist of multiple unattached polygons. Such polygon pieces should be stored asindividual polygon records with common attribute values not as multi-part polygons. There arepotentially many fires covering the same area in different years so there will be overlapping polygons.Topology: No topology enforced.Integration Requirements: None.FIRE ORIGIN POINTS (FIRE POINT)Description: Instance of Fire group.Geometry: Simple, not multi-part points.Topology: No topology enforced.Integration Requirements: Each FIRE POLY perimeter may have zero or one FIRE POINT and thepoint must fall within the polygon.Fire History, Version 1.0July 26, 2013Page 12
State Data StandardsOR/WA Bureau of Land Management7. ATTRIBUTE CHARACTERISTICS AND DEFINITION (In alphabetical order)7.1 ACCURACY FTGeodatabase NameACCURACY FTBLM Structured NameAccuracy Feet MeasureInheritanceInherited from entity WILDFIREFeature Class UseAll feature classesHow close, in feet, the spatial GIS depiction is to the actual location on theground. There are several factors to consider in GIS error: scale andaccuracy of map-based sources, accuracy of GPS equipment, and the skilllevel of the data manipulators. A value of “0” indicates no entry wasmade. This is the correct value when the COORD SRC is another GIStheme (Digital Line Graph, Cadastral National Spatial Data Infrastructureand Digital Elevation Model) because the accuracy is determined by thattheme. However, if COORD SRC is MAP (digitized from a paper map)or GPS, a value of “0” indicates a missing value that should be filled ineither with a non-zero number or “-1.” A value of “-1” indicates that theaccuracy is unknown and no reliable estimate can be made.OptionalNo domain. Examples: 3 (for high accuracy GPS), 40 (best possible forUSGS 24K topo map), 200Short IntegerDefinitionRequired/OptionalDomain (Valid Values)Data Type7.2 BLM ORG CDGeodatabase NameBLM ORG CDBLM Structured Name Administrative Unit Organization CodeInheritanceInherited from Entity WILDFIREFeature Class UseAll feature classesA combination of the BLM administrative state and field office which hasadministrative responsibility for the spatial entity. This includes whichoffice covers the entity for planning purposes and which office is the leadfor GIS edits. Another agency or individual may have the physicalmanagement responsibility for the on-the-ground entity. This field appliesparticularly when a spatial entity crosses resource area or district boundariesand the administrative responsibility is assigned to one or the other ratherthan splitting the spatial unit. Similarly, OR/WA BLM may haveadministrative responsibility over some area that is physically located inNevada, Idaho, and California and vice versa. When appropriate, the officecan be identified only to the district or state level rather than to the resourcearea level.DefinitionFire History, Version 1.0July 26, 2013Page 13
State Data StandardsOR/WA Bureau of Land ManagementRequired/OptionalRequiredDomain (ValidValues)dom BLM ORG CD Domain is a subset of the BLM national domain fororganization codes. Only positions three through seven of the national codeare used (leading LL and trailing zeros are dropped).Data TypeCharacters (5)7.3 CAUSE CATGeodatabase NameCAUSE CATBLM Structured NameFire Cause Category CodeInheritanceInherited from Entity WILDFIREFeature Class UseRequired/OptionalAll feature classesThe general circumstance which caused a fire or set the stage for itsoccurrence (Human vs. Natural).OptionalDomain (Valid Values)dom FIRE CAUSE CATData TypeVariable Characters (10)Definition7.4 CAUSE DETGeodatabase NameCAUSE DETBLM Structured NameFire Cause Detail TextInheritanceInherited from Entity WILDFIREFeature Class UseRequired/OptionalAll feature classesMore detailed description of the cause of a fire than what is provided inCAUSE CAT.OptionalDomain (Valid Values)No domainData TypeVariable Characters (30)Definition7.5 CLASSIFIERGeodatabase NameCLASSIFIERBLM Structured NameClassifier NameInheritanceInherited from Entity WILDFIREFeature Class UseAll feature classesName (mixed case, first and last) of the person or agency who provided thefire perimeter or point coordinates. For FIRE POINT, this may be thename of the national database point coordinates were downloaded from.DefinitionFire History, Version 1.0July 26, 2013Page 14
State Data StandardsOR/WA Bureau of Land ManagementRequired/OptionalOptionalDomain (Valid Values)No domain. Examples: Mary Smith, John Doe, BIFZ, Fire TeamData TypeVariable Characters (30)7.6 COMMENTSGeodatabase NameCOMMENTSBLM Structured NameComments TextInheritanceInherited from Entity WILDFIREFeature Class UseAll feature classesDefinitionFree text for comments about the fire perimeter or fire point.Required/OptionalOptionalDomain (Valid Values)No domain. Example: “Fire perimeter from IR only.”Data TypeVariable Characters (100)7.7 COMPLEX NAMEGeodatabase NameCOMPLEX NAMEBLM Structured NameFire Complex NameInheritanceInherited from Entity WILDFIREFeature Class UseRequired/OptionalAll feature classesName of complex. Applicable only if fire was incorporated into a complexat any point before declared contained. A complex is two or moreincidents located in the same general area which are assigned to a singleincident commander or unified command. Incidents are an occurrence,either human-caused or natural phenomenon, that requires action orsupport by emergency service personnel to prevent or minimize loss of lifeor damage to property and/or natural resources.OptionalDomain (Valid Values)No domain. Examples: South End, Little Bridge Creek, EgleyData TypeVariable Characters (50)Definition7.8 CONTROL DATEGeodatabase NameCONTROL DATEBLM Structured NameFire Control DateInheritanceInherited from Entity WILDFIREFire History, Version 1.0July 26, 2013Page 15
State Data StandardsFeature Class UseOR/WA Bureau of Land ManagementRequired/OptionalFIRE POINTThe date the wildfire is surrounded by fireline or natural features such thatits burning potential is reduced to a point that it no longer threatens furtherspread or resource damage under foreseeable conditions. UNKNOWN isan allowable entry. In YYYYMMDD format.OptionalDomain (Valid Values)No domain. Examples: 20110827, 20120713, UNKNOWNData TypeVariable Characters (8)Definition7.9 COORD DATEGeodatabase NameCOORD DATEBLM Structured NameCoordinate DateInheritanceInherited from Entity WILDFIREFeature Class UseRequired/OptionalAll feature classesDate the coordinates, whose source is listed in COORD SRC, and werecollected. UNKNOWN is an allowable entry.In YYYYMMDD format.OptionalDomain (Valid Values)No domain. Examples: 20110827, 20120713, UNKNOWNData TypeVariable Characters (8)Definition7.10 COORD SRCGeodatabase NameCOORD SRCBLM Structured NameCoordinate Source CodeInheritanceInherited from entity WILDFIREFeature Class UseRequired/OptionalAll feature classesThe actual source of the GIS coordinates for the polylines. If the line iscopied from another theme, and already has COORD SRC, it should bereviewed and may need to be changed for use in this dataset.RequiredDomain (Valid Values)dom COORD SRCData TypeVariable Characters (7)DefinitionFire History, Version 1.0July 26, 2013Page 16
State Data StandardsOR/WA Bureau of Land Management7.11 DISC TIMEGeodatabase NameDISC TIMEBLM Structured NameFire Discovery TimeInheritanceNot inheritedFeature Class UseRequired/OptionalFIRE POINTTime the fire was discovered expressed as Universal Time Coordinatedtime (also referred to as Zulu time). For example, 11:01 a.m. PacificStandard time is 1901 Zulu. See http://navysite.de/what/zulu.htm formore information and a conversion table.OptionalDomain (Valid Values)No domain. Examples: 0945, 1005, 1618, 1742Data TypeVariable Characters (4)Definition7.12 FIRE CODEGeodatabase NameFIRE CODEBLM Structured NameFire Cost Tracking CodeInheritanceInherited from Entity WILDFIREFeature Class UseRequired/OptionalAll feature classesCost accounting tracking number assigned by the FireCode application.For the BLM, pre-Fiscal Year 2004 (prior to the FireCode system), this isthe fire number assigned to the incident by the reporting office.RequiredDomain (Valid Values)No domain. Examples: DNOP, DVU4, P6AVD6, 078Data TypeVariable Characters (8)Definition7.13 FIRE DSCRV DATEGeodatabase NameFIRE DSCRV DATEBLM Structured NameFire Discovery DateInheritanceInherited from entity WILDFIREFeature Class UseRequired/OptionalAll feature classesThe date the fire was confirmed to exist or was reported as discovered. InYYYYMMDD format. UNKNOWN is an allowable entry.OptionalDomain (Valid Values)No domain. Examples: 20110827, 20120713, UNKNOWNData TypeVariable Characters (8)DefinitionFire History, Version 1.0July 26, 2013Page 17
State Data StandardsOR/WA Bureau of Land Management7.14 FIRE NAMEGeodatabase NameFIRE NAMEBLM Structured NameFire Name TextInheritanceInherited from Entity WILDFIREFeature Class UseRequired/OptionalAll feature classesThe name assigned to an incident, assigned by responsible landmanagement unit.RequiredDomain (Valid Values)No domain. Examples: Silver Fire, Coleman Creek, WoodrowData TypeVariable Characters (50)Definition7.15 FIRE NUMGeodatabase NameFIRE NUMBLM Structured NameFire Incident Number TextInheritanceInherited from Entity WILDFIREFeature Class UseAll feature classesOfficial fire incident number assigned at dispatching office. Obtained fromWildcad application.DefinitionRequired/OptionalA four to six digit number assigned to a fire by the reporting unit thatuniquely identifies an incident for a particular local fire managementorganization within a particular calendar year.RequiredDomain (Valid Values)No domain. Examples: 1191, 20013, SO-200, M398Data TypeVariable Characters (8)Domain (Valid Values)dom FIRE UNIT IDData TypeVariable Characters (6)7.16 FIRE YEARGeodatabase NameFIRE YEARBLM Structured NameFire YearInheritanceInherited from Entity WILDFIREFeature Class UseAll feature classesDefinitionThe year in which the fire occurred. In YYYY format.Required/OptionalRequiredFire History, Version 1.0July 26, 2013Page 18
State Data StandardsOR/WA Bureau of Land ManagementDomain (Valid Values)No domainData TypeCharacters (4)7.17 GIS ACRESGeodatabase NameGIS ACRESBLM Structured NameGIS Acres MeasureInheritanceNot InheritedFeature Class UseRequired/OptionalFIRE POLYThe GIS polygon acres. Must be recalculated with every edit submission.The acres will be automatically calculated when the feature class ispublished. The BLM ORG CD will be used to determine the appropriateprojection.Required (automatically generated)Domain (Valid Values)No domainData TypeDecimal (16,6)Definition7.18 INC IDGeodatabase NameINC IDBLM Structured NameUnique Incident Identifier TextInheritanceInherited from Entity WILDFIRE.Feature Class UseRequired/OptionalAll feature classesA unique identifier generated for each wildland fire.Concatenation of fire year, FIRE UNIT ID, and FIRE NUMyyyy-SSUUUU-xxxxxxyyyy calendar yearSSUUUU FIRE UNIT IDxxxxxx local incident identifier (FIRE NUM)Required (automatically generated)Domain (Valid Values)No domain. Examples: 2002-ORUPF-088, 1981-ORBUD-5164Data TypeVariable Characters (22)Definition7.19 LOCAL NUMGeodatabase NameLOCAL NUMBLM Structured NameFire Local IdentifierInheritanceNot InheritedFeature Class UseFIRE POINTFire History, Version 1.0July 26, 2013Page 19
State Data StandardsOR/WA Bureau of Land ManagementRequired/OptionalLocal identifying number (code) for a fire. Legacy number or numberused prior to assignment of official FIRE NUM.OptionalDomain (Valid Values)No domain. Examples: M355, SO-168Data TypeVariable Characters (10)Definition7.20 OUT DATEGeodatabase NameOUT DATEBLM Structured NameFire Out
Center file transfer site (ftp.nifc.gov) by fire team GIS specialists and other fire support entities such as the Northwest Coordination Center. These perimeters are used by the United States Geological Survey (USGS) Geospatial Multi-Agency Coordination
Mystery . Perimeters. Math Content 3.MD.D.8 . Mystery Perimeters . The Mystery Perimeters lesson is a sample from my complete ebook, Exploring Perimeter. All of the lessons in that book follow the same format with a detailed teacher informat
FIRE TOPPER Fire Bowl User Manual Home » FIRE TOPPER » FIRE TOPPER Fire Bowl User Manual Contents [ hide 1 FIRE TOPPER Fire Bowl 2 Setting Up Your Fire Topper Fire Bowl 2.1 Set-Up 3 Placement and Location 3.1 Liquid Propane Tank 4 Using your Fire Topper Fire Bowl - For your safety, read before lighting. 5 Cleaning, Maintenance, Storage 6 .
social or cultural context (livelihoods, festivals, traditional, conflict) and perhaps regulatory framework (permit fires, illegal fires). The terms include fires, wildfires, wildland fire, forest fire, grass fire, scrub fire, brush fire, bush fire, veldt fire, rural fire, vegetation fire and so on (IUFRO 2018). The European Forest Fire
Prefix Origins: ‘audi ’ online test Prefix Origins: ‘trans’ online test Prefix Origins: ‘volve’ online test Look, Cover Write online activity Printable activity sheet Prefix Origins: ‘audi’ online instructional video Printable activity sheet Prefix Origins: ‘trans’ online instructional video Look, Cover Write online activity
Squirrel threw the fire to Chipmunk. The Fire Beings ran after the fire. One Fire Being grabbed Chipmunk’s back. The Fire Being’s hot hand put three stripes on Chipmunk’s back. Chipmunk threw the fire to Frog. The Fire Beings ran after the fire. One Fire Being grabbed Frog’s tail. Frog jumped, and
Fire Exit Legend Basement N Blood Fitness & Dance Center Fire Safety Plans 7.18.13 Annunciator Panel Sprinkler Room AP SR FIRE FIRE SR ELEV. Evacuation Route Stair Evacuation Route Fire Extinguisher Fire Alarm FIRE Pull Station Emergency Fire Exit Legend Level 1 N Blood Fitness & Dance Center Fire Safety Pl
Appendix B: Glossary of Terms A p p e n d i x B-G l o s s a r y o f T e r m s Fire Depletion Area Burned: Fire Impacts: Fire Intensity: Fire Load: Fire Management: Fire Management Zone: Fire Prevention: Fire Protection: Fire Regime: Fire Risk: Area burned that directly impacts wood supply to the forest industry. This could include allocated .
from phytate is very good to enhance animal nutrition (Simons et al., 1990; Adeola et al., 2006; Augspurger et al., 2006; Garcia et al., 2005). Excretion of phosphate can be decrease by as much as .
