Interagency Spatial Fire Planning

We hope to have the Read-Only SFPS available by the first of November.

We will have 3 seperate data views/apps.

1) View Only AGOL dashboard where users can view SFO shapes and associated language.

2) AGOL App where users can go in and associate a category to SFP shapes if they choose to

3) View Only AGOL dashboard for orphan shapes and language that may need remedy actions taken in WFDSS Classic in order to ensure that the dta transitions over to the SFPS once we move into production

We are still working on the set up a data standard and schema, as well as, best management practices to minimize these types of issue/errors moving into the future.

Currently, the Wildland Fire Decision Support System (WFDSS) provides a process for managing fire planning language and spatial data using a combination of processes inside the application, such as the Data Management tab, and external processes involving coordination between field units and agency regional/national staff, and data management team members at the Wildland Fire Management Research, Development & Application Program (WFM RD&A). It is a complex endeavor, after which all of the shape (geospatial) and fire planning language (text information) data are maintained within the WFDSS application. 

This approach has several disadvantages:

Advances in technology, especially the adoption of the ArcGIS Online (AGOL) platform by federal agencies involved in wildland fire management, have opened up opportunities to make a major shift in how Fire Planning Data are stored, managed, and used. This shift has major advantages in terms of efficiency, data usability, and maintenance.

After discussions with WFDSS users, fire planning subject matter experts, and geospatial data subject matter experts, the WFM RD&A, and National Wildfire Coordinating Group Interagency Fire Planning Committee (IFPC), and NWCG Geospatial Subcommittee (GSC) propose that a data service for fire planning shapes and language will be established in the NIFC ArcGIS Online Organization. Processes such as entering and managing fire planning language, which is currently done through the Data Management tab in WFDSS, will be supported instead by an ArcGIS Online Web Application. Agency fire planning and geospatial personnel will own and manage the fire planning language and data in these services, and WFDSS will consume the data needed for wildland fire decision support from the services hosted in ArcGIS Online. The WFM RD&A and WFDSS next-gen contractor will provide technical support for the operation of the ArcGIS online data services and web application.

Advantages include:

WFDSS requires a set of fire planning shapes tied to fire planning language. Four kinds of shapes are currently used in WFDSS to represent fire planning language. These four shape types will be maintained in the services and web application:

Unit Outline: Non-Overlapping Unit-Level – A set of shapes that reflect the administrative boundary of a jurisdictional agency unit such as a National Forest, National Park, or BLM District. Language tied to these shapes is intended to apply everywhere on the unit. WFDSS currently calls this the “Unit Outline” and applies fire planning language entered as “Unit Wide Objectives” to these polygons.

FMU or Strategic Objective shapes: Non-Overlapping, Sub-Unit Shapes – A set of shapes contained within a jurisdictional agency unit boundary, that represent land where fire planning language applies, but does not overlap other sub-units. Examples include situations where one set of language applies to WUI areas, and another set of language applies to backcountry areas. WFDSS currently calls these shapes “FMU” or “Strategic Objective” shapes.

Management Requirements: Overlapping, Sub-Unit Shapes – A set of shapes that are within a jurisdictional agency unit boundary, that can overlap the other types of shapes and each other. Examples include fire planning language that apply to specific pieces of ground, such as a nesting habitat or specific value at risk, but do not change the prevailing fire management language associated with a non-overlapping sub-unit or unit-level shape. WFDSS currently calls these shapes, management requirement shapes.

NEW: Non-Overlapping Multi-Unit Shapes – these shapes represent multi-unit management direction, where the boundaries in which the direction applies cross jurisdictional agency unit boundaries, but do not overlap each other. Examples include statewide fire management agreements like the Alaska Interagency Fire Management Plan, Potential Operation Delineations (PODs) or direction from multi-unit land/resource management plan amendments. WFDSS currently implements this by adding specific layers like the Alaska Fire Management Options and BLM Sage Grouse Management Requirements layers. Rather than managing these as individual layers subject to a WFDSS data refresh plan, a new process will be developed to grant permissions to appropriate personnel who can manage these regional or multi-unit shapes to ensure that data is accurate and current.

A table in the data service will store fire planning language that can be tied to any shape, using what is known in GIS technology as a “one to many” relationship. This will allow a single shape to be related to more than one piece of fire planning language. Rather than force the use of terminology such as “management requirement” and “strategic objective”, fire planning language can be described as directed by the providing agency, or in the manner designated within the policy document from which it originates.

While the changes in terminology described here are small, they would reduce confusion and conflicts regarding “appropriate” content and provide users more flexibility and creativity in the use and application of their management direction. Additional guidance and training to capture succinct, relevant fire management direction that isn’t duplicated may be important, and WFM RD&A will continue to work with the NWCG IFPC and GSC to develop useful help content to support migration to this new approach, and use of the services and application described.

This is placeholder to outline how the Spatial Fire Planning Service will handle shape and language editing and approval. More TBD......

We are pursuing a NWCG Data Standard for the SFPS and its associated shapes/language. This will enabled efficiencies and provide interagency consistency. More to come....