FlamMap6 - Release - Notes - June - 28 - 2019

FlamMap6 Release Notes Version 1.
US FOREST SERVICE, ROCKY MOUNTAIN RESEARCH STATION, FIRE SCIENCES LAB
Release Notes FlamMap

Version 6.0.0
Document Version 1.0
Charles W. McHugh
6/28/2019
Documents changes, and additions made to the FlamMap (Ver. 6.0.0) fire modeling software program
Page 1 of 53
FlamMap6 Release Notes Version 1.0
Release Notes FlamMap 6.0.0

July 1, 2019
Table of Contents
Summary of Improvements-Additions.......................................................................................................... 5
Installation .................................................................................................................................................... 6
Redesigned Runs Options ............................................................................................................................. 6
FARSITE Run .............................................................................................................................................. 7
Import ....................................................................................................................................................... 7
Delete All ................................................................................................................................................... 8
Help ........................................................................................................................................................... 8
Farsite............................................................................................................................................................ 8
Farsite Run Settings .................................................................................................................................. 8
Weather Inputs ....................................................................................................................................... 10
Winds ...................................................................................................................................................... 10
Wind Direction Weather Inputs .......................................................................................................... 10
Generate Gridded Winds ........................................................................................................................ 11
Gridded Winds from Weather Inputs ................................................................................................. 11
Gridded Winds from ATM File ............................................................................................................ 11
Generate the ATM File ........................................................................................................................ 12
Fuel Moisture Settings ............................................................................................................................ 15
Farsite Model Settings Tab ..................................................................................................................... 16
Model Settings .................................................................................................................................... 17
Perimeter Resolution .......................................................................................................................... 18
Distance Resolution ............................................................................................................................ 18
Time Step ............................................................................................................................................ 18
Use Acceleration ................................................................................................................................. 18
Farsite Spotting Settings ......................................................................................................................... 18
Ember Spot Probability ....................................................................................................................... 18
Spot Delay ........................................................................................................................................... 19
Page 2 of 53
Minimum Spot Distance...................................................................................................................... 19

Background Spotting Grid Resolution ................................................................................................. 19
Farsite ROS Adjustment File.................................................................................................................... 19
Farsite Burn Periods ................................................................................................................................ 20
Farsite Outputs ....................................................................................................................................... 21
Spot Fire List ........................................................................................................................................ 22
Fire Growth Report ............................................................................................................................. 22
Fire Growth Report Interpretation ..................................................................................................... 25
Farsite Perimeter Display and Export ................................................................................................. 27
Landscape File Editing Function .................................................................................................................. 30
Create Edit Rules ..................................................................................................................................... 31
Apply Rule ............................................................................................................................................... 35
Expressions.............................................................................................................................................. 35
Masks ...................................................................................................................................................... 37
Using a Raster Mask ............................................................................................................................ 37
Using a Vector Mask ........................................................................................................................... 39
Complex Edits.......................................................................................................................................... 40
Combining Filter and Masks ................................................................................................................ 40
Multiply AND Clauses .......................................................................................................................... 41
Saving Edited Landscapes ....................................................................................................................... 43
Saving Landscape Edit Rules ................................................................................................................... 43
Loading Rules .......................................................................................................................................... 44
Refresh the Display ................................................................................................................................. 44
Creation of Shapefiles ................................................................................................................................. 45
Pointer Mode .......................................................................................................................................... 45
Managing Vectors ................................................................................................................................... 45
Saving the Shapefile ................................................................................................................................ 46
Run Logs and WFDSS Inputs Files ............................................................................................................... 46
FlamMap Run Logs .................................................................................................................................. 46
Limitations .............................................................................................................................................. 48
WFDSS Input Text Files ........................................................................................................................... 48
WFDSS Results Tab Files ......................................................................................................................... 49
Page 3 of 53
WFDSS Inputs Text Files .......................................................................................................................... 50

FlamMap Help ............................................................................................................................................. 51
Tutorials .................................................................................................................................................. 52
For Questions Concerning the FlamMap6 Program Contact:

Charles (Chuck) W. McHugh
RMRS, Fire Sciences Laboratory
Missoula, MT
charles.mchugh@usda.gov
406.829.6953
Page 4 of 53
Summary of Improvements-Additions
1. Addresses previously identified bugs and operational issues in FlamMap 5.0.

2. FlamMap 6.0 is only useable in a Windows 64-bit Operating System.
3. Reprojection of Auxiliary Themes
a. FlamMap will automatically transform and reproject auxiliary themes (both grid and
vector) to match the landscape projection if the landscape and auxiliary theme have the
required projection information.
4. FARSITE4 has been added into FlamMap6.
a. Similar to NTFB in WFDSS with added functionality
b. Includes the ability to use WindNinja internally within FARSITE
c. Includes the ability to import external WindNinja derived grids for use within FARSITE
d. Improvements to the spotting module have been made to increase performance
e. Import/Use information from WFDSS NTFB Inputs Files to setup FARSITE run in FlamMap
5. Redesigned Runs Options
a. FlamMap/MTT/TOM Run
b. FARSITE Run
c. Import of FlamMap run logs or WFDSS Inputs files and data (BASIC, STFB, NTFB)
6. Addition of a Landscape File Editing Function.
a. Use masks to control application of rules and can be either Raster or Vector format
b. Save rules as an XML file
c. Import rules XML File
d. Test Rules to see the number of impacted cells on the landscape
e. Apply Rules allows you to see the change on the landscape
f. Reset landscape to clear out the applied rules
g. For rules to take effect all rules need to be applied and a new landscape file saved
h. Saved landscape needs to be loaded into a new FlamMap project to conduct analyses
7. The Creation of Shapefiles and Drawing vectors and saving as shapefiles has been improved to
eliminate the confusion of creating different shapefile types.
8. All runs within FlamMap create a Run Log File specific to that run
a. Can import Run Log Files from Previous FlamMap runs
b. FlamMap generate Run Logs can be used to initialize new runs
c. Can Import WFDSS inputs text files to initialize a FlamMap/MTT or FARSITE run
9. Updated Help File
10. Updated Tutorials
Page 5 of 53
Installation
FlamMap 6.0 is a 64-bit Windows based program and can only be installed on a computer
running a Windows 64-bit Operating System (OS). Once downloaded, double clicking on the
FlamMap6.msi file will start the Windows installation wizard. Some users may require
administrative rights or need to install it elevated to install the program. There is a separate
installation guide that should answer most questions on installing the program.
The default installation location for FlamMap 6.0 is C:\WorkSpace\FlamMap6. The installation
location can be changed by the user. However, the selected install area must have read\write
privileges for the program to operate correctly. DO NOT install it on C:\My Documents as the
spaces inherent in the windows path names may cause issues with the operation of the program.
DO NOT install the program in C:\Program Files or C:\Program Files (x86) as typically these
locations do not allow for the writing of temporary files when programs are running.
The FlamMap 6.0 install includes sample data to be used with Help File tutorials as well as an
updated context sensitive Help File for use within the program as well as a link allowing for
web-based access from outside the program if there is a working internet connection.
Please read the included Installation guide prior to attempting to install the software.
Redesigned Runs Options

With the inclusion of FARSITE in FlamMap6 a redesign of the Run Window was necessary.
This allows for a more efficient method to access the various fire modeling tools within
FlamMap6.
New FlamMap/MTT/TOM Run (just like you could do in FlamMap5). With the release of
FlamMap6 there have been no significant or substantive changes to the Inputs/Outputs Run
Tabs for a FlamMap, MTT or a TOM simulation. These will not be discussed further in the
release notes.
Page 6 of 53
FARSITE Run
• A New FARSITE Run
• Import of log files from
a) Run logs from a previous FlamMap Project Farsite Run or
b) Import BASIC, STFB or NTFB Input Text files from the Wildland Fire Decision
Support System (WFDSS).
Individual runs are created by the

user, they are given the default
name New Run and are
identified by the page icon.
Individual runs can be renamed on
the Inputs tab of the "Run:" dialog
box.
Right-clicking the ♦Runs item in

the "Tree" pane brings up this
shortcut menu. Selecting the run
type; New FlamMap/MTT/TOM
Run or New FARSITE Run will
immediately open the respective
Run Properties dialog and allow
you to start entering information.
Selecting Import will use run

input files from other FlamMap
Projects or Runs or from the
Wildland Fire Decision Support
System (WFDSS).
Import
Run inputs can be imported from other FlamMap Projects or the Wildland Fire Decision
Support System (WFDSS).
Previous FlamMap runs (Basic, MTT, TOM) and Farsite runs can be imported with a Run Log
output item saved from a previously completed run. Additionally, a WFDSS Basic, Short-Term,
Page 7 of 53
or Near-Term analyses are imported using the Analysis Input file downloaded from the Results
tab of a WFDSS analysis.
Selecting the Import command will open a standard Windows Open file dialog where you
navigate and select the appropriate file to import.
NOTE: Importing Run Logs and WFDSS Input files have some caveats. See the Limitations
section of the Run Logs topic in the Help file for more details.
TIP: For sharing or moving FlamMap or Farsite runs the recommend method is to use the File
Archive command. This is accomplished with the File > Save and Archive command. This is
the preferred method of sharing results and a FlamMap project. A Run Log is meant to serve as
documentation, and for initializing a new run. The File Archive will bundle ALL files associated
with a FlamMap project with a FZA file extension name.
Delete All
Selecting the Delete All command from the ♦Runs shortcut menu will remove all runs from the
analysis area.
Help
The selecting the Help command will bring you to the appropriate page in the online help
system.
Farsite
Farsite Run Settings
A Farsite run is initiated by right-clicking the ♦Runs item in the "Tree" pane and selecting the
New Farsite Run command from the short cut menu. Or select the Analysis Area > New
Farsite Run command from the menu bar. The "Farsite Run:" dialog box opens at the Weather
Inputs tab. The other associated Tabs are: Model Settings and Outputs.
Run information is saved when you close the "Run:" dialog box by clicking the OK button,
regardless of the run status. For example, if your Inputs tab is incomplete, just the information
you have entered is saved. If you have a completed run with output grids, then those are saved
with the project.
The Farsite Run Settings is broken down into three separate tabs.
• Weather
• Model Settings
• Outputs
Page 8 of 53
This document will only touch briefly on each Tab. Please see the Help File and associated
Tutorials for more detail on the setup, technical requirements and background.
Page 9 of 53
Weather Inputs
The Weather Inputs tab in the "Farsite Run:" dialog box is where you define the weather
conditions of your Farsite run. Here you provide information for:
• Initial Dead and Live Fuel Moistures

• Custom Fuel Models
• Winds settings and type
• Fuel Moisture Settings. This is the weather information needed to condition fuels prior to
starting the Farsite simulation and the required weather information to cover the Farsite
simulation burn periods.
Information for Fuel Moistures and Custom Fuel Model files are no different than in
FlamMap5. All the same principles and processes previously needed for fuel moistures and
custom fuel models to run a FlamMap/MTT run apply to Farsite as well. These two topics will
not be discussed in this document. Please see the FlamMap Help for more detailed discussion on
fuel moistures and custom fuel model files
Winds
Unlike FlamMap/MTT runs, which use a single fixed wind speed and direction, Farsite varies the
winds for each time step throughout the simulation using the data found in either the Weather
Stream (.WXS) or Wind (.WND) files. Wind information can be provided from these files, used
as inputs to create gridded wind files internally within FlamMap or as gridded winds developed
externally using desktop WindNinja derived gridded wind fields and entered through an
Atmosphere (ATM) file.
Wind Direction Weather Inputs

Selecting the Wind Direction From Weather Inputs Farsite will use the wind information
contained in Weather Stream (.WXS) or Wind (.WND) files for wind speed and direction
throughout the simulation period. Farsite varies the winds for each time step using the data found
in either the Weather Stream (.WXS) or Wind (.WND) files.
Page 10 of 53
Generate Gridded Winds

Modeling fire behavior accounting for complex wind and terrain interactions can also be
incorporated into Farsite runs. As in previous FlamMap releases, the WindNinja modeling
program has been incorporated to support Farsite runs as well. FlamMap only uses the simplified
version of WindNinja which does not account for the full Mass and Momentum solver. This
WindNInja option can only be used in desktop WindNinja. When used in a Farsite run, Wind
Vectors will only be displayed for the Farsite perimeter burn area and not for the entire
Landscape extent.
Gridded Winds from Weather Inputs

In the Winds group selecting Generate Winds From Weather Inputs radio button, FlamMap
will use the hourly wind speed and direction in the Weather Stream (.WXS) file or Wind
(.WND) file to initialize WindNinja. It will create hourly gridded wind fields for each burn
period in the simulation. Farsite will then use this information throughout the simulation. The
benefit of this is you do not need to create a separate Atmosphere (ATM) file.
Gridded Winds from ATM File

In the Winds group selecting Generate Winds From ATM File radio button allows the user to
generate an Atmosphere (ATM) file using gridded winds developed outside of FlamMap. These
winds are generated using the desktop version of WindNinja. Although not required, this option
does allow the user to use WindNinja’s full Mass and Momentum Solver option. In complex
terrain, these wind outputs may do a better job of resolving channeling and recirculation patterns.
For specific information on desktop WindNinja please see this site:
https://www.firelab.org/project/windninja
Tips:
• Use the LCP you plan to use in FlamMap as the data source in WindNinja;
• Develop gridded winds in FlamMap first to get an idea of the spatial resolution of the winds
needed;
• Depending on the desktop WindNinja settings you use and the LCP extent, it may take an hour
or longer for WindNinja to resolve and provide solutions per combination of wind speed and
direction;
• In the ATM file the user assigns the date and time that combinations of wind speed and
direction are used in the FlamMap Farsite simulation;
• Because of the numerous file types and numbers of files created it is easy to assign the
incorrect file type to a speed or direction;
• Desktop WindNinja still produces a Cloud (.CLD) file. This file is not required for use in
FlamMap-Farsite.
• Save the ATM file to the same location that the WindNinja data is stored. It is also
recommended that this be in the location that all the required Farsite input files are stored.
Page 11 of 53
Generate the ATM File

In the Winds group the selecting Generate the ATM file radio button will make the button
and the load from file buttons active. To create an ATM file the following steps are
required.
1. In the Winds group select Generate Winds From ATM File radio button.
2. Click on the button. This will then open a dialog window and allow you to create and save
the ATM file. This should trigger the following Warning Message.
3. Click on the “OK” button. This will open a typical Windows Save File Dialog allowing you
to navigate to the location that the WindNinja files you plan to use are stored. Having the
ATM file in the same folder and location is critical and required for FlamMap Farsite to use
this information. After you name and save the ATM file the Edit Atmosphere Grid File
dialog box should open. Now you can start the process of adding in the respective wind
speed and wind direction files for each time period.
4. Edit Atmosphere Grid File Entry
Notes on Button Functions:
a. Append Row – Will add a Row to the current end of the data list. It will dupliacate
the Month, Day, and Time of the current last row but not the Speed File or Direction
file.
b. Insert Row – Will add a row above the current Row or selected active Row.
c. Copy Row – Will add a Row to the current end of the data list. It will dupliacate the
Month, Day, Time, Speed File, and Direction file.
d. Delete Row – This will delete the current active or selected Row
Page 12 of 53
5. Select Insert Row. It will populate the Month, Day and Time based on the Farsite
Simulation Period. An example is follows.
6. Add the first speed file, click on the Browse button If you saveed the ATM file to the
same location where the WindNinja Grdded wind file outputs are it will open a dialog box
with a list of all the appropriate ascii (.asc) files of wind speed and direction to choose from.
From here you can select the appropriate wind speed files and direction files for each hour
within the month and day. WindNinja produces files that will have a _vel in the file name
while direction files will have _ang in the file name as illustrated below.
Wind speed filenames: BaseLandscape_2_190_9_90m_vel.asc
Page 13 of 53
Direction Filenames: BaseLandscape_2_190_9_90m_ang.asc
Other information in the filename is the source DEM data, input wind speed and input direction,
and the spatial resolution of the data. The following example parses out this information for a
single filename.
BaseLandscape_2: this is the LCP file used in the WindNinja modeling

190: is the direction (190 degrees) the wind is coming from and was used to initialize the
WindNinja modeling.
9: is the wind speed in mph that was used to initialize the WindNinja modeling.
90m: is the spatial resolution of the data, in this case 90 meters (295 feet) and represents the
distance between data values in the output.
NOTE: If the “Select Wind Speed File” or “Select Direction File” box is empty, then you
have saved the ATM file to a location different than where your gridded wind information is
located.
For each Month, Day and Time you will need to load a respective Speed File and Direction
File. The Select dialog box will filter for the expected file types. However, you can see there are
many, many, files listed for speed, direction, and a third type no longer required by FlamMap,
the cloud file. This will have a _cld in the filename.
Caution: Because of the numerous file types and numbers of files it is easy to assign the
incorrect file type to a speed or direction.
Page 14 of 53
When finished entering all the data your window should look similar to this. Be sure to save the
file once you are finished entering data.
Save the file by closing the Edit Atmosphere Grid File or Save the file by clicking on the
in the upper left. You can open the ATM file in any text editor. However, you may need to select
the application required to open it as the .ATM file extension will not be recognized by
Windows. In a basic text editor, such as Word Pad the .ATM file will look like the following.
The previous example is only for a single day, for one burn period. For a Farsite simulation
spanning multiple days and multiple burn periods this process would need to be repeated.
Fuel Moisture Settings
In the Fuel Moisture Settings group, you will select the weather periods for the simulation that
Farsite uses to condition the dead fuels. For use in Farsite runs in FlamMap6 the same
Page 15 of 53
conditions, work flow and principals as in FlamMap5 still apply. No significant changes have
been made.
Select the Use Weather Stream radio button, click the Browse button Browse files button,
an "Open" dialog box appears. This allows you to navigate and load a previously created file.
Once loaded clicking on the button will open a dialog window and allow you to view as well
as edit data in this window.
When you load the weather files the displayed Start Day and Time will be the earliest time and
day in the file and the End Day and Time will be latest date and time in the data file.
In the Fuel Moisture Conditioning Period the full range of weather inputs available for dead
fuel moisture conditioning are displayed. An example of a loaded WXS file could look like the
following. It is recommended to use the hourly Weather Stream (WXS) format
The Start Day, End Day, and Times settings affect and control
• The amount of time the dead fuels will be conditioned prior to starting the Farsite
simulation.
• What weather information is available for use in setting Farsite Burn Periods. Farsite
burn periods cannot be set that will be outside of the period set here.
Farsite Model Settings Tab
Here you enter the non-spatial inputs and control how fire behavior characteristics are calculated
for a specific Farsite run.
The use and development of Ignition and Barrier files in Farsite in FlamMap6 is the same as
used in FlamMap5 for an MTT run. The Canopy Characteristics settings operate the same as in
Page 16 of 53
FlamMap5. You have a choice of Crown Fire Calculation methods (Finney 2004) or Scott &
Reinhardt (2001) and Foliar Moisture Content value is also set here.
Model Settings
There are eight model settings required for any Farsite simulation. Defaulted values based on the
active Landscape file cell resolution will populate the Perimeter Resolution, Distance
Resolution, Time Step, and Minimum Spot Distance while the Background Spotting Grid
Resolution will be half this value. The user can change this information as needed. These model
settings significantly effect the run time and precision of your Farsite simulation.
Page 17 of 53
Perimeter Resolution
The Perimeter Resolution setting controls the spacing of points along the simulated fire
perimeter where fire behavior characteristics are calculated. Increasing this distance will speed
up processing time. This distance should not be set below the native landscape cell resolution as
any points within the same landscape cell will have the same fire behavior. The Perimeter
Resolution is closely related to the Distance Resolution and Time Step settings so all three
should be considered when modifying any one of them.
Distance Resolution
The Distance Resolution setting controls the spacing of calculation points between time steps in
the direction of fire spread. Increasing this distance will speed up processing time. This distance
should not be set below the native landscape cell resolution as any points within the same
landscape cell will have the same fire behavior. The Distance Resolution is closely related to the
Perimeter Resolution and Time Step settings so all three should be considered when modifying
any one of them.
Time Step
The Time Step is the maximum amount of time that the conditions at a given point are assumed
constant so that the position of the fire front can be projected. The Time Step setting also
controls the timestep interval for the Farsite perimeter outputs and the Fire Growth Report.
The Time Step is really of secondary importance compared with the spatial resolution of the
calculations (as determined by the perimeter and distance resolutions above). The internal time
step used by the simulation is constantly changing according to the minimum time required for
the fire to spread the distance equaling the Distance Resolution. The actual Time Step is thus,
only used as a consistent period during which all fires will be projecting to a coincident time
before mergers and spotting are computed.
Use Acceleration
Fire Acceleration can be used in Farsite to "smooth" the transition to different spread rates
caused by changes in fuel, topography. and weather. With Use Acceleration unchecked the rate
of spread will change instantaneously when conditions change.
Farsite Spotting Settings

Many of the spotting settings in FlamMap6 Farsite have been added to improve the
computational efficiency of Farsite. They are focused on eliminating the tracking and modeling
of spots that typically get overwhelmed by the main fire or to control the number of spots
landing in the same cell. The user can still overwhelm the program by setting the Ember Spot
Probability too high. It is recommended that the user review information contained in the Help
file regarding spotting and setting of spotting for a thorough discussion of these topics.
Ember Spot Probability

An Ember Spot Probability of zero will prevent any spot fires from occurring, effectively
disabling the spotting feature. In Farsite it is recommended to not set the ember spot probability
Page 18 of 53
higher than 0.05. An Ember Spot Probability of 0.10 will result in an effective spotting
percentage of 82% and produce numerous spots that will contribute to much longer processing
times. It is recommended the user start with a spot probability of 0 and gradually increase the
value. This will allow the user to see the impacts on fire growth more easily.
Spot Delay
Spots typically do not begin spreading the moment a live ember lands on receptive fuel. They
tend to take time to ignite the surface fuels and smolder a bit before flaming and spreading, the
Spot Delay setting is an attempt to simulate this typical behavior. A Spot Delay greater than
zero will reduce the effect spotting has on the overall perimeter growth.
Minimum Spot Distance

Most lofted embers will land close to the current perimeter. Many of these spot fires will be
quickly overtaken by the main fire, especially if a Spot Delay and/or Fire Acceleration are
used.
Setting the Minimum Spot Distance greater than zero will prevent live embers from igniting
spot fires within that distance of the current perimeter. This will speed up the simulation as
Farsite does not then spend computational effort tracking and merging these insignificant spot
fires.
Background Spotting Grid Resolution

Even spot fires beyond the Minimum Spotting Distance can be clustered in a small area. The
Background Spotting Grid Resolution setting is used to minimize the number of spot fires near
each other by creating a grid of the specified resolution and only allowing one live ember to
ignite a spot fire in each cell. This will speed up the simulation as Farsite does not then spend
computational effort tracking and merging these insignificant spot fires.
Farsite ROS Adjustment File
The ROS Adjustment (.ADJ) File is an optional ASCII text file for a Farsite simulation. It is
NOT Required to run a Farsite simulation. The assumption is that all spread rates by fuel model
are at the original calculated surface rate of spread. Rate of Spread Adjustment Factors only
need to be provided for the specific fuel models to be adjusted.
Rate of spread adjustment factors allow the user to use experienced judgment or local data to
tune the simulation to observed or actual fire spread patterns. These factors have the same
purpose as adjustments for BehavePlus predictions (Rothermel and Rinehart 1983). Factors are
fuel model specific and are multiplied by the rate of spread to achieve the specified adjustment.
For example, spread rate for a given fuel type would be reduced by half with an adjustment
factor of 0.5, and a quarter with a factor of 0.25. Similarly, spread rate would be doubled using a
factor of 2.0. Keeping the adjustment factors at 1.0 maintains the original spread rate.
Page 19 of 53
Adjustment factors only modify the Surface Rates of Spread for a simulation. To affect other
fire behavior characteristics such as flame length, heat per unit area, fire intensity, etc. you will
need to change fuel models or even develop Custom Fuel Models.
If a ROS Adjustment (.ADJ) File has already been created you can select and load it by
clicking the button to display the "Open" dialog box, navigate to the file location and then
load the file.
To create a ROS Adjustment (.ADJ) File click the button to open the FlamMap Editor and
follow the format as shown below. Fuel Model Number a space and then the Adjustment
Factor.
If you currently have a ROS Adjustments (.ADJ) File loaded, clicking the button will allow
you to edit the contents of that file.
Note: Using an ROS adjustment can really mask other issues related to landscape level data
themes, model settings or weather information. It is recommended that other potential issues be
investigated and addressed prior to relying on the use of ROS adjustment factors.
Farsite Burn Periods
The Burn Period (.BPD) File is a required setting for Farsite and is a file of dates and times that
specify daily burning periods.
Burn Periods are very important and need to be set for each day of the simulation. They can be
set for 24 hours a day or any period during a day. Some knowledge of how the fire is burning is
necessary to set burn periods accurately. Typically fires spread during the daytime dry hours and
stop during the nighttime hours. But unless the nighttime period exceeds the moisture of
extinction the simulation continues to spread but at a slower rate. While significantly slower this
nighttime spread will often over predict what a real fire would do.
Burn Periods can only occur between date and times listed at the top of the dialog box. The
available period is based on data contained in the appropriate weather settings files what is set in
the Fuel Moisture Conditioning Period. In this example the Start time was set on 4/12 at 8:00
AM. As set up here dead fuels will be conditioned from this time till the Farsite simulation starts
on 4/14 at 12:00 PM. Then dead fuels will continue to be conditioned throughout the simulation
based on the hourly weather data.
Page 20 of 53
NOTE: The Start Hour and End Hour are actual times, not burn period or perimeter labels.
More information is available in the Farsite Model Settings topic in the Help File on all these
settings.
Farsite Outputs
A variety of vector and raster outputs can be generated for a Farsite run. The available raster
outputs are very similar to those produced in FARSITE4. Outputs are only generated within the
Farsite perimeters. Fire behavior characteristics can be quite different for each cell as they are
calculated at different landscape and weather conditions depending on the time and place
"burned" during the simulation.
The FlamMap Help discusses in detail the available outputs. Several additional optional outputs
have been added in FlamMap6:
• Spot Fire Locations: This is a point shapefile of the ember landing locations where new
fires were ignited during the Farsite simulation.
• Spot Fire List: This is a text file containing more information about the spot fire ignited
during the Farsite simulation.
Page 21 of 53
• Wind Vectors: Wind vector outputs for a Farsite run are a compilation of all the different
wind grids used in the run. Only the individual wind cells used for each timestep
perimeter are shown as vectors. So wind vectors in different timesteps are likely from
different wind grids
• Spread Vectors: A Spread Vector is a combination of the Spread Direction and Rate of
Spread grids displayed as an arrow.
• Fire Growth Report: Additional output is included with every completed Farsite run in
FlamMap as a text output. This is a text file containing information on fire growth by
burn period throughout the simulation.
Spot Fire List
The fields are,

• launchTime - simulation time when the ember which started a fire was lofted from a
torching tree,
• launchX - X coordinate of the ember launch which started a fire,
• launchY - Y coordinate of the ember launch which started a fire,
• landTime - simulation time when the ember landed, ignition time of the spot fire is
controlled by the Spot Delay setting in the Model Settings tab,
• landX - X coordinate of the ember landing which started a fire,
• landY - Y coordinate of the ember landing which started a fire,
• FlightTime - flight time (in minutes) of the ember,
• Distance - flight distance (in landscape units) of the ember.
Times are cumulative minutes of simulated time from the beginning of the Farsite simulation.
Non-burn periods are included in times, but no embers are lofted outside the burn periods.
Fire Growth Report

The Fire Growth Report is an additional output included with every completed Farsite run as a
text output. It is generated at the end of the run and will show up in the run Tree.
Page 22 of 53
The file contains information on fire growth for each timestep and Burn Period throughout the
simulation. Time intervals and periods of reported growth are determined by the Farsite Time
Step and the Burn Periods in the Model Settings tab.
The following example is for a Farsite simulation with two Burn Periods and a Farsite Time
Step of 60 minutes.
Page 23 of 53
The Rows/Columns are,

• Run: Identifies the specific Farsite Run Name as entered in the Farsite Run Properties
• Ignition Acres: Area represented by a polygon ignition. As noted, this acreage is included
in the Total Acres column. Point or line ignitions will have no reported ignition acres.
• Elapsed Time (Military Time 24-hours): Total Running simulation time in hours
including periods of No Growth. Time increment is based on the Farsite Time Step
value in the Model settings tab. After 24-hours it includes day number plus hours and
minutes.
• Current: Is the current simulation date and time based on the Burn Period settings. Time
increment is based on the Farsite Time Step value in the Model settings tab.
• Fires: The number of individual fires being tracked in each Timestep
• Enclaves: The number of non-burning areas being tracked within each Timestep. Acres
are not reported.
• Total Acres: Cumulative Total Acres reported by Farsite Timestep. The reported value
includes the ignition acreage if a polygon ignition is used.
Page 24 of 53
• Timestep Acres: Actual acres of fire growth by each specific timestep does not include
the ignition acreage.
• No Growth: No fire growth is reported as it is outside the Burn Periods specified in the
Model Settings tab
Fire Growth Report Interpretation

In the previous Fire Growth Report (FGR) example. A polygon ignition file was used and was
39.19 acres, the Farsite Time Step was at 60 minutes, and only 2 Burn Periods were used as
defined below for a total elapsed simulation time of 37-hours.
In this example the ignition time was 0800 on 7/20.
The first elapsed time of 00:00 shows the Ignition and no other information is reported.
The second elapsed time of 01:00 (1-hour since ignition) shows the current simulation date and
time of 07/20 0900 hours. This is the first reported perimeter Timestep. The Total Acres is 69.24
which includes the acres of the ignition perimeter (39.19). The Timestep Acres is the Total
Acres minus the Ignition Acres, equaling 30.06 acres.
The third elapsed time at 02:00 (2-hours since ignition) shows the current simulation date and
time of 07/20 at 1000 hours. This is the second reported perimeter Timestep. The current Total
Acres is 91.70 which includes the acres of the ignition perimeter (39.19). The Timestep Acres is
the current Total Acres (91.70) minus the previous time step Total Acres (69.24) equaling
22.46 acres.
The last reported elapsed timestep in the first burn period is at 11:00 (11-hours total) and shows
the current simulation date and time of 7/20 1900-hours which corresponds to the End Hour in
the first Burn Period settings. The reported cumulative Total Acres at this timestep is 1157.08
Page 25 of 53
acres (includes the ignition polygon acres). The actual fire growth during the timestep was
160.21 acres.
The actual total fire size at the end of the first Burn Period (7/20 19:00) can be calculated in two
ways.
• The reported Total Acres 1157.08 – 39.19 acres (Ignition Acres) = 1117.89 acres or
• Summing each of the individual Timestep Acres 1117.90
The No Growth timesteps are outside of the set Burn Periods days and times. During these time
frames active fire growth does not occur.
The second Burn Period starts on 7/21 at 0800-hours. The Elapsed time is now 01 00:00, 1-day
[24-hours plus 1-hour = 25-hours]. The reported Total Acres at the first timestep in the second
burn period is 1172.33. This is the previously reported timestep Total Acres plus the current
reported Timestep Acres (1157.08 + 15.25 = 1172.33 acres). The current reported Timestep
Acres of growth was 15.25.
The reported acres for each specific timestep is determined for the second Burn Period as
described previously. At the end of the second Burn Period (07/21 20:00) the Total Acres is
4377.90 acres. Because Total Acres is cumulative this represents the final fire size at the end of
the simulation (both Burn Periods). Remember, this total includes the Ignition polygon acres
(39.19 acres). To get the final fire size without the ignition polygon acres you need to subtract
the ignition acres (4377.90 - 39.19 = 4338.71 acres).
The final simulated fire size and total acres by Burn Period can also be obtained by summing
each Burn Period’s Timestep Acres. For example:
• First Burn Period summed Timestep Acres is 1117.90 acres
• Second Burn Period summed Timestep Acres is 3220.82 acres
• The total fire Size is 1117.90 + 3220.82 = 4338.71 acres
Page 26 of 53
Farsite Perimeter Display and Export
Farsite Perimeter output will display multiple perimeters from a single ignition file (polygon,
point or line). The perimeters can be saved in a shapefile format and used in a GIS or loaded into
FlamMap as an Auxiliary Vector Theme.
The initial Farsite display of perimeters is at the end of each timestep as set in the Model
Settings tab for the entire simulation period defined by the Burn Periods. As shown below the
perimeters are displayed at 60-minute intervals and shows 24 sperate perimeters. This may be
too busy or too many perimeters for display or use. In FlamMap6 you can change the number of
perimeters to display and export in the Farsite Perimeters > Properties.
Page 27 of 53
Farsite Perimeter Properties
To change the display of Farsite Perimeters, in the Run Tree highlight and right-click on the
Farsite Perimeters and select Properties.
This will open the Farsite Perimeters Display Properties dialog. Display Properties such as,
line color, line thickness, and line style can be changed and set. There are multiple options for
display of Visible Perimeters. The Display Properties and Visible Perimeter settings made
here will be used when the run outputs are exported as a KMZ. The Visible Perimeters settings
will define the attributes and number of perimeters used when exporting the Farsite Perimeters
as a shapefile.
Visible Perimeters
• All Perimeters: Will display and export every perimeter based on the Farsite Timestep
value in the Farsite Model settings tab.
• By Farsite Timestep Multiple: Allows for displaying perimeters based on some multiple
of the total available Farsite timesteps. The default value is 1 which is the equivalent of
All Perimeters. The user can define this on multiples of the available timesteps, such as
Page 28 of 53
6, 12, 24. Exceeding the total number of available timesteps will show only the last and
final perimeter for the simulation. (A) is set at multiples of 6.
• By Burn Period: Will display the perimeters at the end of each specified Burn Period as
set in the Burn Periods in the Model Settings tab. (B) shows two Burn Periods.
• Final Perimeter Only: Will display only the last perimeter from the last specified Burn
Period. (C) shows only the last and final perimeter.
Once the desired number of Visible Perimeters is set the Farsite Perimeters can be saved as
shapefile for use in a GIS or added to the FlamMap Project as an Auxiliary Vector Theme.
Page 29 of 53
Landscape File Editing Function
Even the most recently updated landscape from LANDFIRE (https://landfire.gov/) may not
reflect wildfires, fuel treatments, or other disturbances within the past five years. Or you may
want to model a landscape with planned fuel treatments to understand the implications on future
fire behavior. FlamMap now includes a feature to easily edit all the landscape themes in an
existing Landscape (.LCP) or GeoTIFF (.TIF) format file.
TIP: For very large landscapes, for edits on multiple data themes or very complex edits the user
should consider making these in GIS. The LCP edit function is best used for quick simple edits.
Edit a landscape with the Landscape > Edit Landscape menu command or right-clicking on the
landscape tree item and selecting Edit Landscape from the shortcut menu as shown below:
This opens the "Landscape Editor" dialog box which will look like this if no rules have been
created for the project.
Page 30 of 53
Create Edit Rules
To edit a landscape you will need to create "rules", which describe how to change a landscape
theme. A rule can only modify one landscape theme, but multiple rules can be used together. Just
be careful and think ahead - many rules or multiple rules for a theme may give unexpected
results. To create a rule click Create Rule in the "Landscape Editor" dialog box. This opens the
"Create/Edit Landscape Rule" dialog box.
Page 31 of 53
The "Create/Edit Landscape Rule" dialog box looks complex at first but simply start at the top.
Replacing a discrete value with a constant is the easiest kind of rule to create.
1. In the Target Theme to Modify: A list box to select an available landscape theme to modify
with this rule.
Note: You can only perform edits on the fuel model, canopy cover, stand height, canopy
base height, and canopy bulk density data themes.
2. Select the Constant radio button from the Value Assignment group.
3. In the Fuel Model Filter group select the fuel models to change in the left hand list and move
them to the right hand list with the Move button. (This filter can be used even if the
Target Theme to Modify: is not a Fuel Model)
4. The Additional AND Clauses group is optional and discussed in the Masks topic.
Page 32 of 53
A simple rule to change fuel model 188 to 183 will look like this.
The complete logic of the rule is shown in the Rule Text box at the bottom of the dialog box.
Always review this text to make sure your rule is as intended. Click OK to close the "Create/Edit
Landscape Rule" dialog box and return to the "Landscape Editor" dialog box where the new rule
is listed.
Page 33 of 53
There are four commands in the Landscape Editor to Edit, Test, Apply, and Delete rules.
Edit Rule - The Edit command displays the "Create/Edit Landscape Rule" dialog box where you
can modify the selected rule.
Test Rule - The Test command allows you to see the rule without changing the landscape.
The Test command first displays this dialog

asking if you want to Test the selected rule
set.
Clicking Yes, will then display this dialog

informing you of the number of cells
modified by this rule. It will not change or
alter the landscape.
Page 34 of 53
Apply Rule
The Apply command first displays this dialog

asking if you want to apply the selected rule set.
Clicking Yes, will then display this dialog

informing you of the number of cells that would
be modified and asks if the edits should be saved
to a new landscape.
When multiple rules exist, each rule must be

applied separately to take effect.
WARNING: The edits are displayed but the project landscape file (.LCP or .TIF) is not
changed. Thus edits will not be reflected in any run. For edits to be utilized in a run the
landscape needs to be saved and loaded in a new project.
The four commands for a rule, Edit, Test, Apply, and Delete can then be used on any rule in the
list.
Clear Rules – The Clear command will clear all the current rules in the landscape Editor. If
they have been applied, you will need to Reload the Landscape to reset the landscape in the
current project back to its original state. Remember any edits not saved to a new landscape will
be lost when you Reload the Landscape.
Expressions
When editing continuous landscape variables, like canopy cover or canopy bulk density, usually
all different values of the theme will need to be changed, not just one. Expressions can be used to
edit all values of a landscape theme by adding, subtracting, multiplying, or dividing all the values
for a landscape theme by a set amount.
The following example will illustrate how to raise the Canopy Base Height by 30%.
Page 35 of 53
1. In the Target Theme to Modify: list box to select the landscape theme to modify with
this rule.
2. Select the Expression radio button from the Value Assignment group.
3. From the Theme list box select the landscape theme with the values to be modified. Most
often this will be the same theme as the Target Theme to Modify: selection.
4. Select an operator from the Operator list box and enter a value for the operator to apply.
5. The Fuel Model Filter group is optional and discussed in the Create or Edit Rules
topic. (this filter can be used even if the Target Theme to Modify: is not Fuel Model)
6. The Additional AND Clauses group is optional and discussed in the Masks topic.
An expression to raise the canopy base height by 30% will look like this.
The Rule Text at the bottom of the "Create/Edit Landscape Rule" dialog box will look like this.
Click OK to close the "Create/Edit Landscape Rule" dialog box and return to the "Landscape
Editor" dialog box where the new rule is listed along with any other previously created rules.
Page 36 of 53
Masks
Edit rules can utilize geospatial masks, either polygon vector or raster themes. Masks can be
landscape, output, or auxiliary themes. Since FlamMap utilizes automatic reprojection any
theme which displays correctly can be used as an edit mask.
Masks can be used to spatially control either a Constant or Expression Value

Assignment. Masks are added via an AND clause, AND clauses are individual atomic pieces of
a rule. Multiply AND clauses can be included in a rule, can be added or deleted individually, and
can also be added to existing rules.
Using a Raster Mask
this rule.
2. Select either the Constant or Expression radio button from the Value Assignment group
and enter the appropriate values.
topic. Also using a Fuel Model Filter with a mask can be confusing. See the Complex
Edits topic.
4. In the Additional AND Clauses/Raster Mask Filter group select the raster theme to use
as a mask from the Existing Theme: drop down list. Only Landscape or Auxiliary
raster themes loaded in the current FlamMap project are shown.
Page 37 of 53
5. Enter values from the raster into the Minimum: and Maximum: text boxes. For a single
value the minimum and maximum can be the same.
6. Click the button.
TIP: When using the Minimum and Maximum Values the following logic applies.
• A single Minimum value will operate on that value and above
• A single Maximum value will operate on that value and below
• The same value for both Minimum and Maximum will operate only on that value.
Each AND clause is listed in the AND clauses group and can be removed from the rule with the
Delete command listed to the right of the AND clause text.
The complete logic of the rule (including AND clauses) is shown in the Rule Text box at the
bottom of the dialog box. Always review this text to make sure your rule is as intended. Click
Page 38 of 53
OK to close the "Create/Edit Landscape Rule" dialog box and return to the "Landscape Editor"
dialog box where the new rule is listed.
Using a Vector Mask
Polygon shapefiles loaded as Auxiliary Vector Themes into the current project can be used as
masks in edit rules. Point and line shapefiles cannot be used as masks.
WARNING: Rules using large or complex polygon masks can take a long time (even hours) to
complete. Creating a raster from a polygon shapefile to use as a mask will significantly reduce
the time to Test or Apply rules.
this rule.
2. Select either the Constant or Expression radio button from the Value Assignment group
and enter the appropriate values.
topic. Also using a Fuel Model Filter with a mask can be confusing. See the Complex
Edits topic.
4. In the Additional AND Clauses/Vector Intersection Filter group select the vector
theme to use as a mask from the Existing Theme: drop down list. Only Auxiliary vector
themes loaded in the current FlamMap project are shown.
5. Click the button.
Page 39 of 53
Each AND clause is listed in the AND clauses group and can be removed from the rule with the
Delete command listed to the right of the AND clause text.
The complete logic of the rule (including AND clauses) is shown in the Rule Text box at the
bottom of the dialog box. Always review this text to make sure your rule is as intended. Click
OK to close the "Create
NOTE: Saving edited landscapes and saving edit rules are two separate operations when using
the landscape editor.
Complex Edits
The FlamMap landscape editor is a powerful tool but be careful. Unexpected results can occur
when creating complex single rules or applying many simple rules to a landscape.
Combining Filter and Masks
The Fuel Model Filter can be used even if the Target Theme to Modify: is not Fuel Model and
combined with a mask as shown in the following rule.
Page 40 of 53
Multiply AND Clauses
Multiple masks and filters can be combined in one rule as seen in the following example.
Page 41 of 53
Note that there is no OR operator, only AND, available for landscape rules so all the conditions
have to be met for edits to occur. In this case four conditions have to be met before any cell is
changed to fuel model 163,
1. Must be fuel model 165,

2. Must have a value of 3043 for the landfireEVT auxiliary grid theme,
3. Must be within the 2017_CLEAR polygon,
4. Must be within the Perimeter1 polygon.
Page 42 of 53
Saving Edited Landscapes
Edit rules that are applied to the project landscape (with the Apply command) and viewed in the
display pane are not permanent and will disappear if not saved. The edited landscape can be
saved two ways.
NOTE: When multiple rules exist each rule must be applied separately to take effect. In this
example with four separate rules each one would need to be applied first, in order for them to
edit the landscape. Then you can save the new landscape and use in a new project for analysis.
In conjunction with the Apply command when asked if a new landscape file (.LCP or .TIF)
should be created,
or by selecting Landscape > Save Landscape from the menu bar.
Saving Landscape Edit Rules
The Landscape Editor Rules can be saved to use with the project they were created in or any
other project. The rules are saved in a user defined .XML file but are not included in the
FlamMap Project (.FMP) or FlamMap Archive (.FZA).
WARNING: Saving rules DOES NOT apply them to the project landscape. Rules need to be
applied and the resultant landscape saved before the changes can be used in a project.
All of the rules listed in the "Landscape Editor" dialog are saved to one file with the
button.
Page 43 of 53
All of the rules listed in the "Landscape Editor" dialog are saved regardless of whether they
have been applied to the landscape or not.
A good practice is to always save the edit rules before closing the "Landscape Editor" dialog.
Saving the FlamMap project after closing the "Landscape Editor" dialog will also keep the rules
active for the current project session only. The rules will disappear if the FlamMap project is
closed or FlamMap crashes and they are not saved in an .XML file.
Loading Rules
A saved rules .XML file can be loaded into any project with the button.
Saved rules are appended to any existing rules present in the "Landscape Editor" dialog.
NOTE: When loading edit rules containing masks, the mask AND clauses are removed if the
Auxiliary Themes used for the masks are not present in the open FlamMap project. All Masks
(vector or raster) in this instance need to be spatially coincident with the LCP you plan to apply
the Edit Rules to.
Refresh the Display
To remove the edits and restore the display pane to the original landscape select the Reload
Landscape menu item. Remember any edits not saved in a new landscape will be lost.
Page 44 of 53
Creation of Shapefiles
In FlamMap you can draw points, lines or polygons depending on the Pointer Mode or toolbar
button you select. How each type of shapefile is used is dependent on how they are loaded into
the Runs type. They can be ignitions, barriers (filled or unfilled) or masks for use in landscape
editing. It all depends on how they are loaded and designated. Hovering over the respective
toolbar button will tell you what each one is for.
Pointer Mode
Use one of the three Create toolbar buttons or change the pointer mode with the Option >
Pointer Mode > Create... to create points, lines, or polygon shapefiles. Make sure to create your
shapefiles before you open the "Run:", "Farsite Run:", “FlamMap/MTT/TOM Run”or
"Landscape Editor" dialog boxes. Point, line, and polygon shapefiles can be created on the
landscape depending on the toolbar button or pointer mode command selected.
o Points - The general purpose of points is to create point ignitions. You can have multiple
point ignitions within a single shapefile.
Select the toolbar button or Option > Pointer Mode > Create Points. Each left
mouse click on the landscape creates a separate point. All point ignitions have a starting
rate of spread (ROS) of 0.0.
o Polygon – Polygons are typically used for area ignitions, as landscape masks for
landscape edit changes, and for use as an area barrier (Be sure to check Fill Barriers
when using a polygon in this manner).
Select the toolbar button or Option > Pointer Mode > Create Polygon. A series of
left mouse clicks ending the polygon with a right mouse click. You should not try to
close the polygon; this is done automatically after the right mouse click. When used as an
ignition this closed polygon depicts an active outward burning fire perimeter. Multiple
polygons can be created in one session.
o Line – Line polygons are typically used as line ignitions or barriers.
Select the toolbar button or Option > Pointer Mode > Create Lines. A series of left mouse
clicks ending with a left double click. The number of left mouse clicks determines the number of
segments of the line ignition. Multiple lines can be created in one session.
Managing Vectors
While drawing the various vectors if you make mistakes there are several options to backup or
clear the data. One method is to double right click in the map view. This will open the following
Page 45 of 53
sub-menu and provides tools to help manage the vectors you draw. This same sub-menu can be
accessed from the Menu bar from the Option >Shape
If you make a mistake there are several options to back-up.
o Select Option > Shape > Delete Current to remove an unfinished vector.
o Select Option > Shape > Delete Last to remove the last finished vector drawn.
o Select Option > Shape > Clear to remove all finished vectors drawn in the current create
session.
Saving the Shapefile

Select the Options > Shape > Save to File command to save the drawn vector(s) as a shapefile
for future uses and repeated runs. One multi-part shapefile will be created when several shapes
have been drawn on the display.
NOTE: All the drawn shapes should be of the same type (point, line, or polygon). You cannot
mix feature types in a single shapefile. Before drawing a different feature type you must either
Clear your current feature type or Save to File. If you attempt to draw or combine feature types
you will get a Warning Message.
Run Logs and WFDSS Inputs Files

Run Logs are text files containing run information, input parameters, and requested outputs for
an individual FlamMap or Farsite run. WFDSS Input files are similar but do not contain run
information (duration, completion time, etc.) or reference other files such as ignitions or barriers.
The Run Logs primary purpose is to document input parameters for a simulation and easily
incorporate this information into documents. These files can also be used to create a new
FlamMap or Farsite run with the Analysis Area > Import command.
FlamMap Run Logs

The following example is a Run Log for a FlamMap BASIC run. Lines beginning with the #
character are comment lines and ignored by FlamMap when importing a run. Comment lines
include run information and lines to improve readability.
Page 46 of 53
Page 47 of 53
Limitations
When importing a WFDSS input file vector inputs and outputs are not included and will need to
be added to your FlamMap or Farsite run using the Run Properties dialog.
Some file paths (ignitions, barriers, atmosphere, gridded wind files, and ideal landscape files) are
specific to the computer where the Run Log was created. If the Run Log is imported to a
different computer these file paths will need to be edited.
Other file paths (initial fuel moisture, weather stream, weather, wind files) are included in the
Run Log as comment lines only for information. The data from these files is included and read
from the Run Log when importing.
Auxiliary Themes are not included in a Run Log or WFDSS Input file.
WFDSS Input Text Files

WFDSS Analysis Inputs text files are formatted a little differently but contain similar
information. Any WFDSS BASIC, STFB (FlamMap MTT) or NTFB (FlamMap Farsite) run can
be imported into FlamMap6. This is done using the Analysis Area > Runs > Import option. Some
additional information from WFDSS will need to be downloaded separately for use in
FlamMap6. These include; the Landscape file, Ignition files, Barrier Files, and Landscape
Masks,
FlamMap6 Run Logs are text files containing run information, input parameters, and requested
outputs for an individual FlamMap (MTT or BASIC) or Farsite runs. WFDSS Analysis Input
files are similar but do not contain run information (duration, completion time, etc.). It also does
not reference other required files such as ignitions or barriers used during the simulation in
WFDSS. These need to be downloaded separately from the appropriate WFDSS Analysis.
From a Current Incident within (WFDSS) you will need to download the following files,
typically from the Results for a run that is either in Review or Completed Status.
• Completed Run Analysis Inputs file

o In FlamMap6 all WFDSS Analysis Inputs files are supported (BASIC, STFB, &
NTFB)
o Can be imported directly into FlamMap6 to initialize model settings
• Required Spatial Data - LCP, Ignitions, Barriers, LCP Masks

o Need to be downloaded separately & Loaded into the Specific FlamMap Run
o The Landscape File from WFDSS needs to be loaded in the FlamMap project
o Ignition Files and Barrier Files need to be Loaded into the Run Properties
Page 48 of 53
• Outputs will need to be selected in FlamMap
• Winds – need to decide on method and data. In WFDSS for NTFB (FARSITE
FlamMap6) you cannot use gridded winds, in FlamMap6 you can.
• Other Information that may be useful

o Screen Capture of LCP edits made in WFDSS. This file cannot be saved or
exported as a text file from WFDSS.
o Any LCP Masks used to in the analysis to edit the LCP
o Consider downloading a separate LCP without edits that can be adjusted within
FlamMap6 if required.
o Screen Capture WFDSS Simulation General Information. Useful to verify against
the Inputs Text file.
In this example information from a NTFB run will be used to import into FlamMap6 to run
FARSITE. BASIC and STFB runs can also be used in FlamMap6 and the steps illustrated here
for acquiring the information from WFDSS are similar.
From a selected Run in WFDSS click on the Results tab.
WFDSS Results Tab Files

From the Completed Run
• Download items associated with the actual run

• Ignition & Barrier
• Download (meters) versions
• All are Shapefile format except where noted
• LCP Masks & Fire Perimeters
• Can only downloaded from the Analysis Map view
• Are Shapefile format
• Projection is degrees
 FlamMap can deal with projections if there is a Projection
file (.prj)
• All WFDSS data includes a .prj file. When extracting zip

file be sure to include the .prj files. If you do not KMZ files
cannot be created and data with mixes of map projections cannot
be projected for use in FlamMap.
Page 49 of 53
WFDSS Inputs Text Files

The WFDSS Inputs Text File is also downloaded from the results tab. Select the Radio button
next to Analysis Input, then the Download button which will provide the opportunity to save
this file. An example of a WFDSS NTFB Analysis Input text file is shown below. Notice it
includes no information on Ignition or barrier filenames. This text file when imported into a
FlamMap6 Farsite run will only populate the Weather Inputs [fuel moistures, Weather Stream
files, Conditioning period] and Model Settings [Model settings, Canopy Characteristics, Burn
Periods]
The user needs to load the appropriate LCP, Ignition file, barrier file and select the desired
outputs.
WFDSS LANDSCPE File
Download the LCP from WFDSS for the specific analysis
• If the LCP has existing edit rules grab a screen capture of the rules as you cannot export
out the rule sets from WFDSS.
Page 50 of 53
• If the existing rules are using LCP masks be sure to download those as well. These files
CAN ONLY be downloaded from the respective incident Analysis Map Page.
• When extracting the LCP be sure to include the .prj file
FlamMap Help
The Help in FlamMap exists in the program as an embedded and content linked Help that can be
opened separately or accessed by clicking on any of the Help buttons in the dialog boxes or from
the Main Menu Bar Help > Contents which will open the embedded Help within the
application. This version of the Help is more static and an updated version is only included with
a new formal program release. When you access the Help file in this manner it will look like
below. The Version of the Help File and the Date will always be displayed. In this example it is,
Version 63 with a July 26, 2018 date.
If you have an active internet connection, you can access the Online Help. This version of the
Help is a living document that is continually being updated with new information being added.
It will also have the Help File Version and Date. This date and version number will likely be
different than the embedded Help. It can be accessed from the Main Menu Bar Help > Online
Help or from the About FlamMap > Online Help. Selecting the online Help should open the
Page 51 of 53
Help System in whatever your default browser is. While we cannot keep up with all manner of
browsers FireFox or IE10 or newer will work.
The online help can be accessed from here: http://flammaphelp.s3-website-us-west-

2.amazonaws.com/
Tutorials
A feature within the Help File is a series of Tutorials. These are accessed from the Navigation
tree on the left-hand side of the Help. The FlamMap software install includes a corresponding
dataset referenced in the Tutorials. The datasets are installed in the location that the FlamMap
software is installed. Typically this will be C:Workspace\FlamMap6\Tutorial
Page 52 of 53
Page 53 of 53

FlamMap6 - Release - Notes - June - 28 - 2019

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FlamMap6 - Release - Notes - June - 28 - 2019

Uploaded by

Copyright:

Available Formats

FlamMap6 Release Notes Version 1.

US FOREST SERVICE, ROCKY MOUNTAIN RESEARCH STATION, FIRE SCIENCES LAB

Release Notes FlamMap

Release Notes FlamMap 6.0.0

Minimum Spot Distance...................................................................................................................... 19

WFDSS Inputs Text Files .......................................................................................................................... 50

For Questions Concerning the FlamMap6 Program Contact:

1. Addresses previously identified bugs and operational issues in FlamMap 5.0.

Redesigned Runs Options

Individual runs are created by the

Right-clicking the ♦Runs item in

Selecting Import will use run

• Initial Dead and Live Fuel Moistures

Wind Direction Weather Inputs

Generate Gridded Winds

Gridded Winds from Weather Inputs

Gridded Winds from ATM File

Generate the ATM File

Wind speed filenames: BaseLandscape_2_190_9_90m_vel.asc

Direction Filenames: BaseLandscape_2_190_9_90m_ang.asc

BaseLandscape_2: this is the LCP file used in the WindNinja modeling

Fuel Moisture Settings

Farsite Model Settings Tab

Farsite Spotting Settings

Ember Spot Probability

Minimum Spot Distance

Background Spotting Grid Resolution

Farsite ROS Adjustment File

Farsite Burn Periods

Spot Fire List

The fields are,

Fire Growth Report

The Rows/Columns are,

Fire Growth Report Interpretation

In this example the ignition time was 0800 on 7/20.

Farsite Perimeter Display and Export

Farsite Perimeter Properties

Landscape File Editing Function

Create Edit Rules

The Test command first displays this dialog

Clicking Yes, will then display this dialog

The Apply command first displays this dialog

Clicking Yes, will then display this dialog

When multiple rules exist, each rule must be

Masks can be used to spatially control either a Constant or Expression Value

Using a Raster Mask

Using a Vector Mask

Combining Filter and Masks

Multiply AND Clauses

1. Must be fuel model 165,

Saving Edited Landscapes

or by selecting Landscape > Save Landscape from the menu bar.

Saving Landscape Edit Rules

Refresh the Display

o Line – Line polygons are typically used as line ignitions or barriers.

If you make a mistake there are several options to back-up.

Saving the Shapefile

Run Logs and WFDSS Inputs Files

FlamMap Run Logs

WFDSS Input Text Files

• Completed Run Analysis Inputs file

• Required Spatial Data - LCP, Ignitions, Barriers, LCP Masks