Data Standards
NWCG data standards (data element and geospatial data layer) provide specifications that enable the common usage of data across wildland fire information systems. For more information click on one of the following lists:
Comment on a proposed data standard
When a new or revised data standard is ready for review and comment, it will be posted under Proposed Data Standards.
Request for a new or revised standard
Requests for the development of a new data standard, or for changes to a current standard, may be submitted on a Request worksheet.
Requests should be emailed to the Data Standards and Terminology Subcommittee at BLM_FA_NWCG_Data@blm.gov.
Download the User Guide and other reference materials
The User Guide for Development and Maintenance of NWCG Data Standards (PMS 938) explains the processes for developing and maintaining both NWCG data element and geospatial data layer standards.
Proposed Data Standards
This list identifies data standards that have been proposed as a new NWCG data standard,or proposed revisions to an existing data standard. Click on the data standard name to review the standard. Email comments to BLM_FA_NWCG_DATA@blm.gov
Currently, there are no data standards out for review.
Approved Data Standards
The NWCG Data Standards and Terminology Subcommittee has approved the following data standards. Detailed information regarding each standard is available by clicking on the data standard name.
| Data Standard | Description | Approved Date | Version | Data Standard Type |
|---|---|---|---|---|
| Aviation Hazards (Point, Line, Polygon) | These 5 geospatial data layers capture physical features that may present a hazard to pilots during aviation operations. | 04/12/2017 | 2 | Geospatial Data Layer |
| Country Code | This standard adopts the International Organization for Standardization (ISO) standard for two-letter country codes. | 10/10/2002 | 1 | Data Element |
| Country Subdivision Code | This standard adopts the International Organization for Standardization (ISO) standard for country subdivision codes of up to three alpha-numeric characters. This standard replaces the NWCG State Code standard. [validated: 6/10/2010] | 6/10/2010 | 1 | Data Element |
| County Code | This standard adopts the Federal Information Process Standards (FIPS) publication 6-4 for representation of counties and equivalent entities as a three-digit code. [validated: 4/20/2009] | 4/10/2008 | 1 | Data Element |
| Date | This data standard specifies a standard format for calendar date. [validated: 7/30/2002] | 7/30/2002 | 1 | Data Element |
| Employment Category | The type of employment appointment or agreement under which a person is hired. [validated: 5/6/2004] | 5/6/2004 | 1 | Data Element |
| Event Kind & Category | This data standard specifies general, high-level codes and descriptions to be used in categorizing the types of incidents and planned events to which the interagency wildland fire community responds. [validated: 6/15/2004] | 6/15/2004 | 1 | Data Element |
| Final Fire Acre Quantity | This data standard provides a standard format and definition for the measure of acres within the final perimeter of a fire. [validated: 7/11/2008] | 7/11/2008 | 1 | Data Element |
| Fire Initial Action Date & Time | This data standard provides a standard format and definition for the date and time that initial action was taken by the first resources to arrive at a fire. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Fire Report Approver Name | This data standard provides a standard format and definition for the name of the person that approved the fire report. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Fire Report Provider Name | This data standard provides a standard format and definition for the name of the person that provided the data for the fire report. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Fire Reporting Agency Unit Identifier | This data standard adopts the NWCG Unit Identifier data standard to identify the agency preparing a fire report. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Fire Resource Kind, Category & Type | This data standard provides standard formats and definitions for a three-tier classification (kind and type) of operational resources available to respond to a fire. [validated: 8/15/2008] | 8/18/2008 | 1 | Data Element |
| Fire Size Class | This data standard provides a standard code and definition for classifying a fire into one of several ranges of fire size based on the number of acres within the final fire perimeter. [validated: 12/17/2012] | 12/17/2012 | 1 | Data Element |
| FireCode | This data standard specifies the standard format and rules for FireCode, a code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures. [validated: 5/18/2005] | 5/18/2005 | 1 | Data Element |
| Frequency Use Designator | This data standard provides a standard list of designators for the kind of communications that will occur on an assigned radio frequency. [validated: 3/8/2004] | 3/8/2004 | 1 | Data Element |
| Fuels Treatments (polygon) | The Fuels Treatments (polygon) data layer represents the area(s) of unique fuels treatments during a single timeframe. each treatment may be made up of multiple polgons. [Validated 9/9/2014] | 9/9/2014 | 1 | Geospatial Data Layer |
| Geographic Area (GA) Code & Name | This data standard provides a code and name for each of the wildland fire geographic areas. [validated: 2/16/2006] | 2/16/2006 | 1 | Data Element |
| Geographic Area Coordination Center (GACC) Code & Name | This data standard provides a code and name for each of the wildland fire geographic area coordination centers. [validated: 5/21/2015] | 5/21/2015 | 2 | Data Element |
| Geographic Coordinating Area (GCA) Code & Name | This data standard provides a code and name for each of the wildland fire geographic coordinating areas. [validated: 5/21/2015] | 5/21/2015 | 2 | Data Element |
| Horizontal Datum Code | This data standard provides a code and name for each of the point coordinate reference systems used within the interagency wildland fire community. [validated: 12/17/2012] | 12/17/2012 | 1 | Data Element |
| Incident Name | This data standard provides a standard format for storing the name of an incident. [validated: 8/15/2008] | 8/18/2008 | 1 | Data Element |
| Incident Personnel Fatality Quantity | This data standard provides a standard definition and format for the total number of deaths of personnel assigned to an incident. [validated: 12/17/2012] | 12/17/2012 | 1 | Data Element |
| Incident Personnel Injury & Illness Quantity | This data standard provides a standard definition and format for the total number of reportable occupational injuries and illnesses that occurred in conjunction with an incident. [validated: 12/17/2012] | 12/17/2012 | 1 | Data Element |
| Initial Fire Strategy Met Indicator | This data standard provides a standard format for indicating whether the objectives of the initial fire strategy used on a fire were attained. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Initial Response Resource Quantity | This data standard provides a standard format and definition for reporting the total number of fire resources (by kind, category, and type) used during initial response. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Latitude | This data standard specifies a standard format for latitude. [validated: 12/15/2006] | 12/15/2006 | 1 | Data Element |
| Local Fire Report Identifier | This data standard specifies the standard format and rules for a number or code that uniquely identifies an incident report for a particular reporting unit and a particular calendar year. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Local Incident Identifier | This data standard specifies the standard format and rules for a number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Longitude | This data standard specifies a standard format for longitude. [validated: 12/15/2006] | 12/15/2006 | 1 | Data Element |
| Management Complexity Level Designator | This data standard provides a standard code and definition for identifying the highest management level utilized to manage a wildland fire event. [validated: 8/15/2008] | 8/18/2008 | 1 | Data Element |
| National Fire Danger Adjective Class Rating | This data standard provides a standard code and definition for describing the potential initiation, spread, and difficulty of control of wildfires in an area. [validated: 7/6/2009] | 7/2/2009 | 1 | Data Element |
| National Fire Danger Rating System Fuel Model | This data standard provides a standard code and definition for identifying the NFDRS Fuel Model representing the predominant fuel bed across a fire area. [validated: 7/6/2009] | 7/2/2009 | 1 | Data Element |
| Other Structures Destroyed Quantity | This data standard provides a standard format and definition for reporting the total number of structures, other than residences, destroyed as a result of a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Other Structures Threatened Quantity | This data standard provides a standard format and definition for reporting the total number of structures, other than residences, threatened by a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Point of Origin Accuracy Descriptor | This data standard provides a standard format and definition for describing the methods used to determine the certainty and precision of the fire location at the point of origin. [validated: 8/15/2008] | 8/18/2008 | 1 | Data Element |
| Point of Origin Aspect Code | This data standard provides a standard code and definition for describing the direction toward which the predominate slope faces at the point of origin of a fire. [validated: 12/17/2012] | 12/17/2012 | 1 | Data Element |
| Point of Origin County Code | This data standard adopts the NWCG County Code data standard for identifying the county or equivalent entity at the point of origin of a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Point of Origin Datum | This data standard adopts the proposed NWCG Horizontal Datum data standard for identifying the datum associated with the coordinates of the point of origin of a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Point of Origin Fire Intensity Level | This data standard provides a standard code and definition for expressing the fire intensity during the initial response. [validated: 7/6/2009] | 7/2/2009 | 1 | Data Element |
| Point of Origin Land Owner Kind & Category | This data standard adopts the NWCG Land Owner Kind & Category data standard for identifying the owner at the point of origin at the time of an incident. [validated: 8/15/2008] | 8/18/2008 | 1 | Data Element |
| Point of Origin Latitude | This data standard adopts the NWCG Latitude data standard for identifying the latitude location of the point of origin of a fire. [validated: 7/21/2008] | 7/21/2008 | 1 | Data Element |
| Point of Origin Longitude | This data standard adopts the NWCG Longitude data standard for identifying the longitude location of the point of origin of a fire. [validated: 7/21/2008] | 7/21/2008 | 1 | Data Element |
| Point of Origin Responsible Agency Unit Identifier | This data standard adopts the NWCG Unit Identifier data standard to identify the agency with primary fire protection responsibility at the point of origin of a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Point of Origin Slope | This data standard provides a standard format and definition for reporting the typical slope in the immediate vicinity of the point of origin of a fire. [validated: 12/17/2012] | 12/17/2012 | 1 | Data Element |
| Point of Origin State Code | This data standard adopts the NWCG State Code data standard to identify the state or equivalent entity at the point of origin of a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Position Code & Position Title | This data standard provides a code (mnemonic) and title for each position used in incident management response. [validated: 2/15/2005] | 2/15/2005 | 1 | Data Element |
| Prescribed Fire Escape Indicator | This data standard provides a standard format and definition for indicating whether a wildfire resulted from an escaped prescribed fire. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Primary Weather Station Identifier | This data standard adopts the NWCG NFDRS Weather Station Standards six-digit identifiers for identifying the NFDRS weather station best representing weather and climate conditions for an incident site at the time of initial response. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Residences Destroyed Quantity | This data standard provides a standard format and definition for reporting the total number of residences destroyed, or damaged to an extent requiring rebuilding, as a result of a fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Residences Threatened Quantity | This data standard provides a standard format and definition for reporting the total number of residences threatened by the fire. [validated: 7/21/2008] | 7/21/2008 | 1 | Data Element |
| Special Land Designator | This data standard provides a standard format and definitions for identifying officially designated special land types within a fire perimeter. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| State and Land Owner Final Fire Acre Quantity | This data standard provides a standard format and definition for the measure of acres of land belonging to a specified owner within a fire perimeter within a state. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Time Point (Time of Day) | This data standard adopts the International Organization for Standardization (ISO) standard for representing time of day. [validated: 4/15/2008] | 4/11/2008 | 1 | Data Element |
| Unique Fire Identifier | This data standard provides a standard format and rules for a unique identifier assigned to each wildland fire. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Unique Fire Report Identifier | This data standard provides a standard format and rules for a code that uniquely identifies a particular fire report. [validated: 6/16/2008; next validation: 12/31/2013] | 6/16/2008 | 1 | Data Element |
| Unit Identifier | This data standard specifies the standard format and rules for Unit Identifier, a code used within the wildland fire community to uniquely identify a particular government organizational unit. [validated: 12/18/2012] | 1/15/2005 | 1 | Data Element |
| Wildland Fire Locations (point) | Wildland Fire Location Points represent the final spatial locations of the fire occurrences. Fire occurrences represent the ignition points (preferred), the polygon centroids, or more generalized locations (least desirable) when the ignition points are not known or not available. [Validated 9/9/2014] | 9/9/2014 | 1 | Geospatial Data Layer |
| Wildland Fire Perimeters (polygon) | Wildland Fire Perimeter Polygons geospatial data layer standard provides the standard template for exchange/transfer of wildland fire perimeter polygons, representing the daily and final perimeters for wildfires and prescribed fires. Replaces the Fire History (polygons) geospatial data layer standard (archived) and incorporates the Daily Fire Perimeter geospatial data layer standard (archived). [Validated 9/9/2014] | 9/9/2014 | 1 | Geospatial Data Layer |
| Wildland Urban Interface Indicator | This data standard provides a standard format and definition for indicating if the presence of Wildland Urban Interface (WUI) influenced the cost, strategy, or management of a wildfire. [validated: 12/1/2009] | 12/1/2009 | 1 | Data Element |
| Geographic Area Coordination Center Boundaries (polygon) | Geographic boundary polygons depicting the administrative area of the Geographic Area Coordination Centers | 2/21/2017 | 1 | Geospatial Data Layer |
| Wildland Fire Event Line | The Wildland Fire Event Line data standard will define the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting GIS Standard Operating Procedures on Incidents (GSTOP) guidance. | 2/21/2017 | 1 | Geospatial Data Layer |
| Predictive Services Area Boundaries (polygon) | Geographic boundary polygons depicting the extent of the Predictive Services Area Boundary | 2/21/2017 | 1 | Geospatial Data Layer |
| Wildland Fire Dispatch Area Boundaries (polygon) | Geographic boundary polygons depicting the administrative area of the Wildland fire Dispatch Areas | 2/21/2017 | 1 | Geospatial Data Layer |
| Wildland Fire Dispatch Office Location (point) | Geographic location point depicting the administrative location of the Dispatch Centers | 2/21/2017 | 1 | Geospatial Data Layer |
| Wildland Urban Interface (polygon) | The wildland urban interface (WUI) geospatial data standard defines minimum attribution for interagency collaboration and data sharing. | 2/21/2017 | 1.1 | Geospatial Data Layer |
| Fire Containment Date & Time | This standard provides a standard format and definition for the date and time a wildfire was declared contained. | 7/21/2008 | 1 | Data Element |
| Fire Control Date & Time | This standard provides a standard format and definition for the date and time a wildfire was declared under control. [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Fire Discovery Date & Time | This data standard provides a standard format and definition for the date and time a fire was discovered or confirmed to exist. [validated: 4/10/2008] | 4/10/2008 | 1 | Data Element |
| Fire Out Date & Time | This data standard provides a standard format and definition for the date and time when a fire is declared "out". [validated: 6/16/2008] | 6/16/2008 | 1 | Data Element |
| Initial Fire Strategy Designator | This data standard provides a standard format and definition of the fire strategy initially used on a wildland fire. [validated: 8/15/2008] | 8/18/2008 | 1 | Data Element |
| Landowner Kind & Category | This data standard provides a two-tier classification (kind and category) of landownership. [validated: 8/25/2016] | 08/25/2016 | 1 | Data Element |
| State Code | This data standard has been superseded by the Country Subdivision Code standard. | 7/30/2002 | 1 | Data Element |
| Wildland Fire Event Point | The Wildland Fire Event Point data standard will define the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting GIS Standard Operating Procedures on Incidents (GSTOP) guidance. | 2/21/2017 | 1 | Geospatial Data Layer |
| Wildland Fire Event Polygon | The Wildland Fire Event Polygon data standard will define the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting GIS Standard Operating Procedures on Incidents (GSTOP). | 2/21/2017 | 1 | Geospatial Data Layer |
Assigned Data Standards
The following data standards have been assigned to stewardship groups for development of new standards or modifications of current standards. When draft versions are ready for review, they are moved to the “Proposed Data Standards” list.
| Data Standard | Date Assigned | Request / Proposal | Stewardship Group |
|---|---|---|---|
| ABCD Misc (New) | 6/18/2015 | Create a data standard to describe the pre-established incident job code for fires less than 300 acres. | Data Management Committee, Incident Business Committee |
| Calculated Acres (New) | 6/18/2015 | Create a data standard to measure of acres calculated (i.e., infrared) within the fire perimeter of a fire. More specifically, the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. The minimum size must be 0.1. | Fire Reporting Subcommittee, Geospatial Subcommittee |
| Complex Parent Indicator (New) | 6/18/2015 | Create a data standard that indicates that this incident has been designated as a complex (an existing incident was promoted to complex status, or a new record was created for a complex) | Data Management Committee |
| Complex Parent Irwin ID (New) | 6/18/2015 | Create a data standard to define the IRWIN ID of the complex to which this incident is a member. | Data Management Committee |
| Daily Fire Acre Quantity (New) | 1/24/2014 | Create a new data standard for the measure of acres within the daily fire perimeter of a fire. | Fire Reporting Subcommittee |
| Daily Resource Quantity (New) | 12/19/2013 | Create a data standard to describe the data element for tracking the total number of fire resources (by agency, provider, kind, category, and type) currently being utilized by an incident. | Fire Reporting Subcommittee |
| DateTime (New) | 2/20/2014 | Develop a data standard for the combination of date and time elements so that elements that use date and time are submitted in a standard format of date/time combination for data exchange of YYYY-MM-DDThh:mm:ssZ Adopt ISO8601 Standard. | Data Standards and Terminology Subcommittee |
| Discovery Acres (New) | 12/19/2013 | Create a new data standard for the estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. | Fire Reporting Subcommittee |
| Estimated Containment Date (New) | 12/19/2013 | Create a data standard to describe the data element for estimated date a wildfire will be contained. | Fire Reporting Subcommittee |
| Estimated Costs to Date (New) | 12/19/2013 | Create a data standard to describe the data element for tracking the estimated total incident costs to date for the entire incident based on currently available information. | Incident Business Committee |
| Fire Cause Kind & Category (New) | 11/17/2009 | Development requested as part of the fire occurance data standards (Fire Cause) needed for the elements identified as critical in the FORS Study Report. | Communication, Education, and Prevention Committee |
| Fire Cause Responsible Person Age (New) | 11/17/2009 | Development requested as part of the fire occurance data standards (Fire Cause) needed for the elements identified as critical in the FORS Study Report. | Communication, Education, and Prevention Committee |
| Fire Cause Responsible Person Gender (New) | 11/17/2009 | Development requested as part of the fire occurance data standards (Fire Cause) needed for the elements identified as critical in the FORS Study Report. | Communication, Education, and Prevention Committee |
| Fire Containment Date & Time (Revision) | 1/24/2014 | Change request: Combine date and time attributes to standard format for data exchange of YYYY-MM-DDThh:mm:ssZ | Fire Reporting Subcommittee |
| Fire Control Date & Time (Revision) | 1/24/2014 | Change request: Combine date and time attributes to standard format for data exchange of YYYY-MM-DDThh:mm:ssZ | Fire Reporting Subcommittee |
| Fire Discovery Date & Time (Revision) | 1/24/2014 | Change request: Combine date and time attributes to standard format for data exchange of YYYY-MM-DDThh:mm:ssZ | Fire Reporting Subcommittee |
| Fire Initial Response Resource Agency (New) | 12/19/2013 | Create a data standard to describe the data element that provides a general classification of the agency providing fire resources to an incident when initial response resource summary information is reported. This data element is the top level hierarchy of initial response resource quantity which is the total number of fire resources (by agency, provider, kind, category, and type) used during initial response of an incident. | Incident Business Committee, Fire Reporting Subcommittee |
| Fire Initial Response Resource Provider (New) | 12/19/2013 | Create a standard to describe the data element that identifies the organizational unit providing fire resources to an incident when initial response resource summary information is reported. This data element is the second level hierarchy of initial response resource quantity which is the total number of fire resources (by agency, provider, kind, category, and type) used during initial response of an incident. | Incident Business Committee, Fire Reporting Subcommittee |
| Fire Management Unit (New) | 4/18/2015 | Create a data standard to represent fire management strategic direction spatially. This must consist of non-overlapping Fire Management Unit (FMU) data or Strategic Objective Shape data. FMU data are used to depict a land management area definable by objectives, management constraints, topographic features, access, values to be protected, political boundaries, fuel types, major fire regime groups, etc. that set it apart from the characteristics of an adjacent FMU. The FMU may have dominant management objectives and pre-selected strategies assigned to accomplish these objectives. Strategic Objective Shape data are intended to spatially represent the strategic objectives of the landscape and the unit boundary shape; it allows you to utilize shapes other than FMUs to visually depict their fire management direction. A Strategic Objective is a broad statement, specified in land/resource management or fire management plan that identifies change in water, soil, air, or vegetation from the present to proposed conditions, or describes an existing resource condition that should be maintained. | Geospatial Subcommittee, Interagency Fire Planning Committee |
| Fire Out Date & Time (Revision) | 3/20/2013 | Change request: Combine date and time attributes to standard format for data exchange of YYYY-MM-DDThh:mm:ssZ | Fire Reporting Subcommittee |
| Fire Perimeter Contained Percentage (New) | 1/24/2014 | Create a data standard that defines Fire Percent Contained. The value indicates the percent of incident area that is no longer active. | Fire Reporting Subcommittee |
| Fire Perimeter To Be Contained Percentage (New) | 1/24/2014 | Create a data standard that defines Fire Percent Perimeter to be Contained. Indicates the percent of perimeter left to be completed. This entry is appropriate for full suppression, point/zone protection, and confine fires, or any combination of these strategies. This entry is not used for wildfires managed entirely under a monitor strategy. | Fire Reporting Subcommittee |
| Fire Resource Agency (New) | 12/19/2013 | Create a standard to describe the data element that provides a general classification of the agency providing fire resources to an incident when daily resource summary information is reported. This data element is the top level hierarchy of resource quantity which is the total number of fire resources (by agency, provider, kind, category, and type) currently being utilized by an incident. | Incident Business Committee, Fire Reporting Subcommittee |
| Fire Resource Provider (New) | 12/19/2013 | Create a standard to describe the data element that identifies the organizational unit providing fire resources to an incident when resource summary information is reported. This data element is the second level hierarchy of resource quantity which is the total number of fire resources (by agency, provider, kind, category, and type) currently being utilized by an incident. | Incident Business Committee, Fire Reporting Subcommittee |
| Forest Service Job Code, Forest Service Override Code (New) | 12/19/2013 | Create a data standard to describe the code used to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode. Create a data standard to describe the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix to the fire code. For example, if the FS is assisting DOI, an override of 1502 will be used. | Incident Business Committee |
| FS Assisted Indicator (New) | 6/18/2015 | Create a data standard that indicates if the FS is assisting on an incident in which the responsible unit is not Forest Service. | Incident Business Committee |
| Helispot (New) | 6/18/2015 | Create a data standard for Helispot to permit the sharing of helispot data for wildland fire and search and rescue incidents. | Geospatial Subcommittee, National Interagency Aviation Committee |
| ICS 209 Remarks (New) | 6/18/2015 | Create a data standard that describes additional information pertinent to the incident management. (ICS Block 47) | Data Management Committee |
| ICS 209 Report Date Time (New) | 6/18/2015 | Create a data standard that describes the date and time of the latest approved ICS-209 report. | Fire Reporting Subcommittee |
| ICS 209 Report For Time Period From (New) | 6/18/2015 | Create a data standard that describes the date and time of the beginning of the time period for the current ICS209 submission. (ICS Block 11) | Fire Reporting Subcommittee |
| ICS 209 Report For Time Period To (New) | 6/18/2015 | Create a data standard that describes the date and time of the end of the time period for the current ICS209 submission. (ICS Block 11) | Fire Reporting Subcommittee |
| Ignition Source Heat Form (New) | 11/17/2009 | Create a data standard for codes and descriptions of the primary sources of energy that results in a human caused fire. | Communication, Education, and Prevention Committee |
| Ignition Source Kind & Category (New) | 11/17/2009 | Create a data standard that describes the kind and category of causative agents that identify the conditions, actions, or sequence of events that result in a human caused fire. | Communication, Education, and Prevention Committee |
| Incident Dispatch Center ID (New) | 12/19/2013 | Create a standard to describe a unique identifier for a dispatch center responsible for supporting the incident. | Unit Identifier Unit |
| Incident Suppression Estimated Expenditure (New) | 10/28/2009 | Create a data standard to track the cumulative-to-date, estimated suppression expenditures (in dollars) for a specific incident. | Fire Reporting Subcommittee |
| Initial Fire Strategy Designator (Revision) | 1/24/2014 | Replace the current list of standard values with the following: Full Suppression, Point Zone Protection, Confine, Monitor | Fire Reporting Subcommittee |
| Initial Point of Origin Latitude & Longitude (New) | 1/24/2014 | Create a data standard that defines the initial location reported for an incident. The latitude/longitude location of the initial reported point of origin specified in decimal degrees | Fire Reporting Subcommittee |
| Initial Response Acres (New) | 12/19/2013 | Create a new data standard for an estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. | Fire Reporting Subcommittee |
| Mitigation Plan Boundary (New) | 6/18/2015 | Create a data standard to analyze mitigation plans area effectiveness. This standard should include mitigation plan name, type, completion date, url to plan (if available), Communities at Risk (if available), communities at risk federal (if available), and fire wise communities. | Geospatial Subcommittee, Wildland Urban Interface Mitigation Committee |
| MultiJurisdictional Indicator (New) | 6/18/2015 | Create a data standard that indicates if the incident covers multiple jurisdictions. | Incident Business Committee |
| Point of Origin City (New) | 6/18/2015 | Create a data standard that describes the closest city to the incident point of origin. (ICS Block 18) | Fire Reporting Subcommittee |
| Point of Origin Fuel Model (New) | 3/10/2009 | Create a data standard for a standard code and definition for describing the fire behavior prediction system fuel model at the point of origin of a fire. | Fire Reporting Subcommittee |
| Point of Origin Incident Jurisdictional Agency (New) | 6/18/2015 | Create a data standard that identifies the jurisdictional agency at an incidents point of origin. | Fire Reporting Subcommittee |
| Point of Origin Legal Description Principal Meridian (New) | 6/18/2015 | Create a data standard that describes the principal meridian of the legal description (section, township, range) of the incident at point of origin. (ICS Block 24) | Fire Reporting Subcommittee |
| Point of Origin Legal Description Quarter (New) | 6/18/2015 | Create a data standard that describes the quarter section of the legal description (section, township, range) of the incident at point of origin. (ICS Block 24) | Fire Reporting Subcommittee |
| Point of Origin Legal Description Quarter Quarter (New) | 6/18/2015 | Create a data standard that describes the quarter/quarter section of the legal description (section, township, range) of the incident at point of origin. (ICS Block 24) | Fire Reporting Subcommittee |
| Point of Origin Legal Description Range (New) | 6/18/2015 | Create a data standard that describes the range of the legal description (section, township, range) of the incident at point of origin. (ICS Block 24) | Fire Reporting Subcommittee |
| Point of Origin Legal Description Section (New) | 6/18/2015 | Create a data standard that describes the section of the legal description (section, township, range) of the incident at point of origin. (ICS Block 24) | Fire Reporting Subcommittee |
| Point of Origin Legal Description Township (New) | 6/18/2015 | Create a data standard that describes the township of the legal description (section, township, range) of the incident at point of origin. (ICS Block 24) | Fire Reporting Subcommittee |
| Point of Origin Owner Unit Identifier (New) | 1/24/2014 | Create a data standard that defines the NWCG Unit Identifier which identifies who owns the land at the point of origin of a fire. | Fire Reporting Subcommittee |
| Point of Origin Protecting Unit (New) | 6/18/2015 | Create a data standard that describes the NWCG Unit Identifier data standard to identify the agency with primary fire protection responsibility at the point of origin of a fire. | Fire Reporting Subcommittee |
| Protection Unit (polygon) (New) | 6/18/2015 | Create a geospatial data layer standard to identify agencies responsible for protection, suppression, financial, and rehabilitation in a given area. This standard should include attributes containing protecting unit agency and group, agreements, cost apportionment, most recent change, agreement contact, and acres. | Geospatial Subcommittee, Fire Reporting Subcommittee |
| Reimbursable Indicator (New) | 6/18/2015 | Create a data standard that indicates the fire code can be utilized by other agencies through agreements. | Incident Business Committee |
| Resource Location (point) (New) | 6/18/2015 | Create a geospatial data layer standard is needed for resource origination (i.e. base) locations. The feature class would give the origination location for interagency incident resources (i.e. tanker bases, hotshot bases, rappel bases, etc) dispatched within ROSS (Resource Ordering and Status System). Domain values should be developed through a review of ROSS data and existing agency data sets. | Geospatial Subcommittee |
| Total Incident Personnel (New) | 12/19/2013 | Create a new data standard for total number of personnel assigned. Includes overhead, crew members, helicopter crew member, engine crew members, camp crew people, etc. | Incident Business Committee |
| Trespass Indicator (New) | 6/18/2015 | Create a data standard that indicates if the fire is trespass or a bill will be issued. A tort or trespass claim for the Government results when a person or legal entity, acting negligently or otherwise wrongfully, causes damages to Forest Service resources or property. | Fire Reporting Subcommittee, Wildland Fire Investigation Subcommittee |
| Water Sources (New) | 6/18/2015 | Create a data standard that tracks the location and relevant information about capabilities of water sources for wildland and structure fire response. | Geospatial Subcommittee |
| Fire Resource Personnel Quantity (New) | 09/15/2016 | Create a data standard that describes the total number of personnel assigned to the fire resource being reported (by agency, provider, kind, category, and type). | National Coordination System Committee |
| Fire Resource Status (New) | 09/15/2016 | Create a data standard that indicates whether the resource record being submitted or updated is an initial response resource or daily resource record. | National Coordination System Committee |
| ICS 209 Report Status (New) | 09/15/2016 | Create a data standard that describes the version of the 209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules). | National Coordination System Committee |
| Incident Commander Name (New) | 09/15/2016 | Create a data standard that describes the first (optional) and last name of the incident commander currently assigned to the incident. | National Coordination System Committee |
| Incident Management Organization (New) | 09/15/2016 | Create a data standard that describes the incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, NIMO, etc. This field is null if no team is assigned. | National Coordination System Committee |
| Incident Short Description (New) | 09/15/2016 | Create a data standard that describes the general descriptive location of the incident such as the number of miles from an identifiable town. (ICS Block 25) | National Coordination System Committee |
| Event Kind & Category (Revise) | 09/15/2016 | 1) Include the valid value FA - False Alarm; 2) add a note to the value "WU - Wildland Fire Use" to indicate that it should only be used for archived domains; and 3) include "CX" under the Event Kind: Fire (FI) to identify incident complexes. | National Coordination System Committee |
| Land Owner Kind & Category (Revision 1) | 6/16/2008 | NWCG has a data element standard for the name of the 'Land Owner Kind', which should be called 'Land Owner Kind Name'. NWCG has a data element standard for the name of the 'Land Owner Category’, which should be called 'Land Owner Category Name’. Create a data element standard for ‘Land Owner Category Description’. | Fire Reporting Subcommittee |
| Planned Actions (New) | 09/15/2016 | Create a data standard that describes a short summary of the actions planned for the next operational period. | National Coordination System Committee |
| Significant Events (New) | 09/15/2016 | Create a data standard that describes the observed fire behavior or significant incident events for the current reporting period. (ICS Block 28) | National Coordination System Committee |
| Weather Concerns (New) | 09/15/2016 | Create a data standard that describes a brief summary of how the current weather is affecting the incident and how the anticipated weather will affect the incident. (ICS Block 35) | National Coordination System Committee |
| Fuels Treatment (point) (New) | 12/02/2016 | A data standard is needed for point data of fuels treatments to facilitate interagency data sharing on fuels treatment projects. | Geospatial Subcommittee, Fuels Management Committee |
Requested Data Standards
The following requests have been received for proposed development or modification of data standards. Requests are continually reviewed by the Data Standards and Terminology Subcommittee. As workloads and priorities allow, requests will be assigned to appropriate stewardship groups. When requests are assigned, they are moved to the “Assigned Data Standards” list.
| Data Standard | Date Requested | Request / Proposal |
|---|---|---|
| Country Code & Name (Revision) | 07/15/2015 | NWCG has a data element standard for 'Country Code'. Create a data element standard for 'Country Name'. The data element 'Country Name' should be added to the current 'Country Code' standard, and the name of the standard should change to 'Country Code & Name'. |
| Country Subdivision Code & Name (Revision) | 7/15/2015 | NWCG has a data element standard for 'Country Subdivision Code'. Create a data element standard for 'Country Subdivision Name'. The data element 'Country Subdivision Name' should be added to the current 'Country Subdivision Code' standard, and the name of the standard should change to 'Country Subdivision Code & Name'. |
| County Code & Name (New) | 7/15/2015 | NWCG has a data element standard for 'County Code'. Create a data element standard for 'County Name'. The data element 'County Name' should be added to the current 'County Code' standard, and the name of the standard should change to 'County Code & Name'. |
| Employment Category Code, Name & Description (Revision) | 7/27/2015 | NWCG has a data element standard for 'Employment Category Code'. Create a data element standard for 'Employment Category Name' and 'Employment Category Description'. The data elements 'Employment Category Name' and 'Employment Category Description' should be added to the current 'Employment Category' standard, and the name of the standard should changed to 'Employment Category Code, Name & Description'. Revisit the definition of 'Employment Category Code' to ensure it is still valid and accurate. |
| Fire Resource Kind, Category & Type (Revision) | 7/27/2015 | NWCG has a data element standard for 'Fire Resource Kind', which should be called 'Fire Resource Kind Name'. Create a data element standard for 'Fire Resource Kind Description'. NWCG has a data element standard for 'Fire Resource Category’, which should be called 'Fire Resource Category Name’. Create a data element standard for ‘Fire Resource Category Description’. NWCG has a data element standard for 'Fire Resource Type’, which should be called 'Fire Resource Type Name’. Create a data element standard for ‘Fire Resource Type Description’. |
| Fire Size Class Code & Description (Revision) | 7/27/2015 | NWCG has a data element standard for 'Fire Size Class', which should be called ''Fire Size Class Code''. Create a data element standard for 'Fire Size Class Description'. The data element 'Fire Size Class Description' should be added to the current 'Fire Size Class' standard, and the name of the standard should change to 'Fire Size Class Code & Description'. |
| Frequency Use Name & Description (Revision) | 7/27/2015 | NWCG has a data element standard for the name of the 'Frequency Use Designator', which should be called 'Frequency Use Designator Name'. Create a data element standard for 'Frequency Use Designator Description'. Consider doing away with the word 'Designator', and instead call these two data elements 'Frequency Use Name' and Frequency Use Description'. |
| Initial Fire Strategy Code & Name (Revision) | 7/27/2015 | NWCG has a data element standard for the name of the 'Initial Fire Strategy Designator', which should be called 'Initial Fire Strategy Designator Code'. Create a data element standard for 'Initial Fire Strategy Designator Name'. The data element 'Initial Fire Strategy Designator Name' should be added to the current 'Initial Fire Strategy Designator' standard, and the name of the standard should change to 'Initial Fire Strategy Code & Name. Consider doing away with the word 'Designator', and instead call these two data elements 'Initial Fire Strategy Code' and 'Initial Fire Strategy Name'. |
| Planned Actions (New) | 3/20/2015 | Create a data standard that describes a short summary of the actions planned for the next operational period. |
| Point of Origin Time Zone (New) | 5/28/2015 | Create a new NWCG Data Standard for Time Zone at Point of Origin that says all times reported for a wildland fire incident will be based on the time zone at the fire's point of origin. This would include Containment, Control, Discovery, Initial Response, Out, etc.. |
| Projected Incident Activity (New) | 3/20/2015 | Create a data standard that describes an estimate of the direction in which the incident is expected to spread, migrate or expand in the next 12, 49, and 72 hour time frames. |
| Significant Events (New) | 3/20/2015 | Create a data standard that describes the observed fire behavior or significant incident events for the current reporting period. (ICS Block 28) |
| Weather Concerns (New) | 3/20/2015 | Create a data standard that describes a brief summary of how the current weather is affecting the incident and how the anticipated weather will affect the incident. (ICS Block 35) |
| Agreement Status | 06/10/2016 | Agreement Status Name is needed for ROSS/IROC agreement management. |
| Agreement Type Name | 06/10/2016 | Agreement Type Name is needed for ROSS/IROC agreement management. |
| Airport Code and Name | 06/10/2016 | Airport Code and Name is needed for ROSS/IROC airport and location management. |
| Airport Reload Base Indicator | 06/10/2016 | Airport Reload Base Indicator is needed for ROSS/IROC airport and location management. |
| Airport Tower Indicator | 06/10/2016 | Airport Tower Indicator is needed for ROSS/IROC airport and location management. |
| Airport Use Name | 06/10/2016 | Airport Use Name is needed for ROSS/IROC airport and location management. |
| Available For Multiple Incidents Indicator | 06/10/2016 | Available For Multiple Incidents Indicator is needed for ROSS/IROC resource management. |
| Aviation Hazard Description | 06/10/2016 | Aviation Hazard Description is needed for ROSS/IROC incident management. |
| Aviation Hazard Is Fixed Indicator | 06/10/2016 | Aviation Hazard Is Fixed Indicator is needed for ROSS/IROC incident management. |
| Aviation Hazard Type Name | 06/10/2016 | Aviation Hazard Type Name is needed for ROSS/IROC incident management. |
| Bearing Number | 06/10/2016 | Bearing Number is needed for ROSS/IROC airport and location management. |
| Catalog Item Long Name | 06/10/2016 | Catalog Item Long Name is needed for ROSS/IROC catalog management. |
| Catalog Item Short Name | 06/10/2016 | Catalog Item Short Name is needed for ROSS/IROC catalog management. |
| Catalog Item Trackable Indicator | 06/10/2016 | Catalog Item Trackable Indicator is needed for ROSS/IROC catalog management. |
| Contact Method Name | 06/10/2016 | Contact Method Name is needed for ROSS/IROC incident management. |
| Contact Name | 06/10/2016 | Contact Name is needed for ROSS/IROC incident management. |
| Contract Number | 06/10/2016 | Contract Number is needed for ROSS/IROC contract management. |
| Contract Status Name | 06/10/2016 | Contract Status Name is needed for ROSS/IROC contract management. |
| Contract Type Name | 06/10/2016 | Contract Type Name is needed for ROSS/IROC contract management. |
| Contractor Type Name | 06/10/2016 | Contractor Type Name is needed for ROSS/IROC contract management. |
| Geospatial Data Layer Standard: Country Subdivision Boundary | 06/10/2016 | Country Subdivision Boundary (polygon) is needed for ROSS/IROC incident management. |
| Geospatial Data Layer Standard: County Boundary | 06/10/2016 | County Boundary (polygon) is needed for ROSS/IROC incident management. |
| Default Financial Code for Ordering Indicator | 06/10/2016 | Default Financial Code For Ordering Indicator is needed for ROSS/IROC incident management. |
| Distance Number | 06/10/2016 | Distance Number is needed for ROSS/IROC airport and location management. |
| DUNS Number | 06/10/2016 | DUNS Number is needed for ROSS/IROC vendor management. |
| Encrypted Tax ID | 06/10/2016 | Encrypted Tax ID is needed for ROSS/IROC vendor management. |
| Financial Code | 06/10/2016 | Financial Code is needed for ROSS/IROC incident management. |
| Incident Description | 06/10/2016 | Incident Description is needed for ROSS/IROC incident management. |
| Incident Maximum Elevation Number | 06/10/2016 | Incident Maximum Elevation Number is needed for ROSS/IROC incident management. |
| Incident Minimum Elevation Number | 06/10/2016 | Incident Minimum Elevation Number is needed for ROSS/IROC incident management. |
| Incident Status Name | 06/10/2016 | Incident Status Name is needed for ROSS/IROC incident management. |
| Incident Type Name | 06/10/2016 | Incident Type Name is needed for ROSS/IROC incident management. |
| Incident-Project Order Number | 06/10/2016 | Incident-Project Order Number is needed for ROSS/IROC incident management. |
| Location Bearing Number | 06/10/2016 | Location Bearing Number is needed for ROSS/IROC incident management. |
| Location City Name | 06/10/2016 | Location City Name is needed for ROSS/IROC location management. |
| Location Distance Number | 06/10/2016 | Location Distance Number is needed for ROSS/IROC incident management. |
| Location Line 1 Address | 06/10/2016 | Location Line 1 Address is needed for ROSS/IROC location management. |
| Location Line 2 Address | 06/10/2016 | Location Line 2 Address is needed for ROSS/IROC location management. |
| Location Name | 06/10/2016 | Location Name is needed for ROSS/IROC location management. |
| Location TRS Principal Meridian | 06/10/2016 | Location TRS Principal Meridian is needed for ROSS/IROC location management. |
| Location TRS Range | 06/10/2016 | Location TRS Range is needed for ROSS/IROC location management. |
| Location TRS Section | 06/10/2016 | Location TRS Section is needed for ROSS/IROC location management. |
| Location TRS Township | 06/10/2016 | Location TRS Township is needed for ROSS/IROC location management. |
| Location Use Name | 06/10/2016 | Location Use Name is needed for ROSS/IROC location management. |
| Location UTM Easting | 06/10/2016 | Location UTM Easting is needed for ROSS/IROC location management. |
| Location UTM Northing | 06/10/2016 | Location UTM Northing is needed for ROSS/IROC location management. |
| Location UTM Zone | 06/10/2016 | Location UTM Zone is needed for ROSS/IROC location management. |
| Location Zip Code | 06/10/2016 | Location Zip Code is needed for ROSS/IROC location management. |
| Resource Item Name | 06/10/2016 | Resource Item Name is needed for ROSS/IROC resource management. |
| Vendor Name | 06/10/2016 | Vendor Name is needed for ROSS/IROC vendor management. |
| VOR Code and Name | 06/10/2016 | VOR Code and VOR Name are needed for ROSS/IROC airport and location management. |
| Additional Fuel Model (New) | 08/23/2016 | The fuel model which best represents an additional carrier of the fire. |
| Final Fire Report Approved By (New) | 08/23/2016 | The name of the person that approved the final fire report for the incident. |
| Final Fire Report Approved By Title (New) | 08/23/2016 | The title of the person that approved the final fire report for the incident. |
| Final Fire Report Approved By Unit (New) | 08/23/2016 | NWCG Unit ID associated with the individual who approved the final report |
| Final Fire Report Approved Date (New) | 08/23/2016 | The date that the final fire report was approved for the incident. |
| Final Fire Report Narrative (New) | 08/23/2016 | A summary of the comments in narrative form as entered on the final fire report to describe important aspects of the incident. |
| Final Strategy Attained Date Time (New) | 08/23/2016 | The date/time the final fire strategy was accomplished on the incident. |
| Fire Behavior Description (New) | 08/23/2016 | A description of the observed fire behavior for the current ICS-209 reporting period. |
| Fire Behavior General (New) | 08/23/2016 | A general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. |
| Fire Behavior General 1 (New) | 08/23/2016 | A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). |
| Fire Behavior General 2 (New) | 08/23/2016 | A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). |
| Fire Behavior General 3 (New) | 08/23/2016 | A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). |
| Fire Cause General (New) | 08/23/2016 | Agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. |
| Fire Cause Investigated Indicator (New) | 08/23/2016 | Indicates if an investigation is underway or was completed to determine the cause of a fire. |
| Fire Cause Specific (New) | 08/23/2016 | A further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. |
| Fire Growth Cessation Date Time (New) | 08/23/2016 | The date/time that the fire perimeter stopped growing in size. |
| Fire Ignition Date Time (New) | 08/23/2016 | The actual date/time that the fire began ignition. This date may be different from the fire discovery date. |
| Fiscally Responsible Unit (New) | 08/23/2016 | NWCG Unit who has fiscal responsibility for the incident. |
| Point of Origin Jurisdictional Unit (New) | 08/23/2016 | NWCG Unit Identifier to identify the unit with jurisdiction for the land where the point of origin of a fire falls. |
| Point of Origin Jurisdictional Unit Parent Unit (New) | 08/23/2016 | The unit ID for the parent entity, such as a BLM State Office or USFS Regional Office, that resides over the Jurisdictional Unit. |
| Predominant Fuel Model (New) | 08/23/2016 | Describes the type of fuels found within the majority of the incident area. |
| Primary Fuel Model (New) | 08/23/2016 | The fuel model which best represents the primary carrier of the fire for the reporting period. |
| Projected Incident Activity 24 (New) | 08/23/2016 | An estimate of the direction in which the incident is expected to spread, migrate or expand in the next 24 hours. |
| Projected Incident Activity 48 (New) | 08/23/2016 | An estimate of the direction in which the incident is expected to spread, migrate or expand in the next 48 hours. |
| Projected Incident Activity 72 (New) | 08/23/2016 | An estimate of the direction in which the incident is expected to spread, migrate or expand in the next 72 hours. |
| Projected Incident Activity 72 Plus (New) | 08/23/2016 | An estimate of the direction in which the incident is expected to spread, migrate or expand in beyond the next 72 hours. |
| Secondary Fuel Model (New) | 08/23/2016 | The fuel model which best represents the secondary carrier of the fire for the reporting period. |
| Unified Command (New) | 08/23/2016 | Indicates whether the incident is being managed under Unified Command. Unified Command is an application of the Incident Command System used when there is more than one agency with incident jurisdiction or when incidents cross political jurisdictions. Under Unified Command, agencies work together through their designated Incident Commanders at a single incident command post to establish common objectives and issue a single Incident Action Plan. |
| WFDSS Decision Status (New) | 08/23/2016 | Indicates the state of the WFDSS decision and/or if a WFDSS decision has been approved for the incident. This information is helpful in resolving conflicts between incident records. |