Skip to main content

PMS 936-1

Edit Event Data

Event data is intended to be edited in the Offline Copy with off the shelf tools available in ArcGIS. Custom tools can be used, but none are required.

The GISS Workflow assumes the user is comfortable with ArcGIS Pro and has a solid understanding of basic GIS concepts and components. Additional training is available directly from Esri with a NIFC Org Account.

Incident and Event Schema specific editing operations and requirements will be presented here, but this is not intended as a GIS training.

Esri has extensive documentation on editing tools and options in ArcGIS Pro.

Job Aids

Job Aid - Editing Event Data (Instructions for common editing tasks on the Event data)

Best Practices for Editing

Be Mindful of the Coordinate Reference System

When working with Event data in ArcGIS Pro, it is recommended that the data’s coordinate reference system (CRS) be a local projected coordinate system.  Event data can be successfully maintained and edited in any CRS; however, the use of a local projection has been determined to be best practice as it provides the most consistency in the workflow.

When working with the NIFS, this means setting the data frame CRS in the map view in the Pro Project Template before creating any other projects, including the Edit Project, and the Offline Copy.

Save Often

There are no edit sessions in ArcGIS Pro.

However, all edits must still be saved. Once edits are made in a map, the Save and Discard buttons will become available on the Edit ribbon tab.

Image
ArcGIS Pro toolbar

 

Because editing is enabled on all available workspaces, it is vitally important to pay close attention to the Feature Template being used when creating features.

Renaming layers in the Table of Contents can help avoid confusion without affecting the underlying data.

Avoid Editing Conflicts

SYNC – Edit – SYNC.  Sync the Offline Copy immediately before and after each editing session. Limit editing sessions to short time periods. Sync can also be performed any time during an editing session.

Only ever download and/or edit an incident you are assigned to. The NIFS is a shared editing environment. Be respectful and conscientious of everyone’s data.

Make edits throughout the day. Don’t put off edits until the end of the day – avoid the rush.

Read the Offline-Editing Conflict Resolution  job aid. The NIFS is a “last in wins” system.

If there are multiple editors, establish clear geographic, feature type (point, line, poly), or temporal boundaries and communicate frequently about who is editing what.

Work with SITL to educate field data collectors on editing conflicts and coordinate their assignments to avoid them. Geographic boundaries work best for field editors.

Extra care and communication should be paid to suppression repair tracking to ensure Resource Advisors (READs) and other field editors do not conflict.

Only edit the records that require edits. Don’t field calculate a whole column when only a few records are necessary. Unnecessary edits can cause conflicts with other editors using Pro or Field Maps. Unnecessary edits also cause issues with the Archiving and backup services.

DO NOT delete ALL data in the Offline Copy and replace with new features from another database. Maintaining a separate database for edits is not best practice and adds to the GISS workload. Do all editing in the Offline Copy.

Editing Order

Edit the Wildfire Daily Fire Perimeter feature in the Event Polygon layer first, then the Perimeter Line to match the Wildfire Daily Fire Perimeter, then Event Line, Event Point, and Accountable Property features in a logical order. Create and update Label Points for assignments (Division, Branch, Zone) and other labels, if needed.

Divisions and Branches

Divisions and Branches divide an incident into geographic areas for the purpose of work assignments and delineating areas of operation. A Division Supervisor (DIVS) supervises the resources assigned to a division. A Branch is the organizational level having functional or geographic responsibility for major parts of incident operations such as divisions. Divisions exist within specific Branches. The Operations Branch Director (OPBD) supervises DIVS on large incident that contain branches.

Characteristics of Divisions

  • Divisions are identified by letters of the alphabet.
  • Usually start with “A” at the fire origin and progress in a clockwise order around the incident.
  • It’s common to skip some division letters to allow for expansion of the incident (e.g., Div A, Div B, Div Y, Div Z).
  • Division map label example: Div A
  • Division assignment labels are placed away from the fire edge, between the break symbols, and should not obstruct key features on the map.
  • As an incident winds down, adjacent divisions may merge into a single division or be combined (e.g., Div M/N/O), usually temporarily.
  • Division break symbols should be rotated so that they are perpendicular to the fire perimeter. Divisions may not occur on the fire perimeter. These are commonly referred to as “floating” divisions.
  • Division labels for divisions that are not on the fire perimeter are placed outside of the imaginary line between the division breaks.

Characteristics of Branches

  • Branches are identified by Roman numeral labels (or by functional name).
  • Geographic branches typically consist of 2 or more divisions. Functional branches oversee a specific function on the incident: Fire Suppression, Air Operations, Law Enforcement, HAZMAT, Structure Protection, etc.
  • Fire Suppression and Air Operations Branches are the most common found on wildland fire incidents.
  • Map label example: Branch IV
  • Branch assignment labels are placed away from the fire edge, between the break symbols, and should not obstruct key features on the map.
  • Branch break symbols should be rotated so that they are perpendicular to the fire perimeter. Branch break symbol may serve as both the break between branches and the break between divisions (i.e., replace a division break).
  • Branches may not occur on the fire perimeter. A branch may be assigned to an isolated area of an incident or another smaller incident within the main response area. These are commonly referred to as “floating” branches. Branch labels for branches that are not on the fire perimeter are placed outside of the imaginary line between the division breaks.
 

Attribution and Labeling of Divisions and Branches

Image
Labeling points for Branch II

The Event Point feature class contains the Division and Branch Break features. The Comment field is used for reference (metadata) to indicate which divisions are separated by a break. This is especially important on larger incidents with potentially dozens of divisions and several branches. Maintaining Comments in the Event Point feature class helps identify those point features. When branches exist on the incident, also indicate in the Comment field which branch the division is in. 

Image
Event Point window with X acroos label column and Comments column highlighted.

The Label Point feature class is an invisible point feature that is labeled directly on top of the point and is used to place Division and Branch Assignment labels in between Division and Branch Breaks. Labels should be in a clear area and not cover any incident or map features. 

Image
Label Point window with Label column highlighted.

Use the Attributes Pane

The Attributes pane is the preferred method for both single and bulk attribute updates because domains are set for many of the fields. Field Calculate, custom tools, and scripts will overwrite a domain, introducing typos and breaking queries. To bulk update with the Attributes pane, click the layer heading in the top section after selecting the desired features and edit the table below as normal.

When all features are properly attributed, it is easy to change the Display Field setting under layer properties to leverage the Attributes pane for efficient features updates.

Setting it to a field that best differentiates data for the task at hand (for example Feature Category or Label) allows features to be quickly selected and updated.

Image
Attributes window with Event Line (2) highlighted, and emphasized as Feature Category.

One Drive

If storing the GeoOps Incident Directory Structure in FireNet SharePoint and syncing  with OneDrive, pick a folder that is not syncing in OneDrive to store your Edit Project (.aprx) and Offline Copy. This has been shown to reduce Sync errors.

Follow the guidance provided in the Sharing GISS Data Using FireNet365 job aid in the \tools folder of the GeoOps incident directory structure.

Editing for Public Data Sharing

Editing the NIFS affects systems and services beyond IMT and local operations. Care must always be taken to follow best practices and ensure proper attribution.

NIFC Open Data Public Perimeter Services

The WFIGS Wildland Fire Perimeter Services shared publicly on the NIFC Open Data site pull features from Event Polygon in the NIFS and are used by individuals and popular applications such as InciWeb. Proper data attribution is essential to ensuring the data is visible where it is needed.

The key in this relationship is the IRWIN ID. The perimeter for each incident must have the correct IRWINID attribute in Event Polygon. Perimeters must also be a single feature. If a perimeter consists of multiple shapes, they must be merged after editing.

NIFS Perimeters will only display in the Public Service with the Attributes FeatureStatus = Approved, FeatureAccess = Public, and IsVisible = Yes. These are the default values for Event Polygon. Any of these values can be changed to remove a perimeter from public view should it be necessary.

View Only Web Maps and EGP Viewers (Situation Analyst)

While only Event Polygon is used in the public services, the other Event Features are available in applications such as Situation Analyst in EGP and web maps based off the View Only Incident Web Map Template. These automatically exclude features with FeatureStatus = Archive and DeleteThis = Yes, so their proper attribution is required as well.

 

Page Last Modified / Reviewed:

Print PDF

NWCG Latest Announcements

2024 Week of Remembrance

Date: June 27, 2024
Contact: 6 Minutes for Safety Subcommittee 

As we approach the 2024 Week of Remembrance (WOR), June 30 to July 6, we dedicate this time to thoughtfully reviewing and recognizing the events of the 2018 Mendocino Complex. As such, this year’s theme of “Learning From the Mendocino Complex” embodies a longstanding hallmark of WOR, honoring through learning.

Throughout the week, our energy will be directed toward fostering generative conversations in briefing rooms and at tailgates.

References:

6 Minutes for Safety - 2024 Week of Remembrance

Wildland Fire Lessons Learned Center

Updated NWCG Wildland Fire Risk and Complexity Assessment, PMS 236

Date: June 24, 2024
Contact: Incident and Position Standards Committee 

The June 2024 update of the NWCG Wildland Fire Risk and Complexity Assessment, PMS 236, is now available to meet the current needs for incident management typing.

The NWCG Wildland Fire Risk and Complexity Assessment should be used to evaluate firefighter safety issues, assess risk, and identify the appropriate incident management organization based on incident complexity. Assessing risk, determining incident complexity, and identifying an appropriate incident management organization is a subjective process based on examining a combination of indicators or factors, which can change over time.

References:

NWCG Wildland Fire Risk and Complexity Assessment, PMS 236

Operations Branch Director (OPBD) Next Gen PTB Available

Date: June 10, 2024
Contact: NWCG Feedback 

The NWCG Position Task Book for Operations Branch Director (OPBD), PMS 311-109 is now available for use within the OPBD position qualification pathway. As part of the transition to Complex Incident Management (CIM), the OPBD Next Gen PTB was developed and the position qualification pathway updated.

More information about the Next Gen PTB format can be found on the NWCG Position Task Book webpage.

References:

Operations Branch Director Position Page

Operations Branch Director Next Gen PTB

NWCG Position Task Books

Updated NWCG Standards for Interagency Incident Business Management, PMS 902

Date: June 5, 2024
Contact: NWCG Incident Business Committee 

The 2024 revision of the NWCG Standards for Interagency Incident Business Management, PMS 902 is now available. The uniform application of interagency incident business management standards is critical to interagency fire operations. PMS 902 assists NWCG agencies in constructively working together to provide effective execution of each agency's incident business management program.

References:

PMS 902