release notes flammap version 5.0 - firelab.org · us forest service, ... release notes flammap...

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

Release Notes FlamMap Version 5.0.0 Document version 3.0

Charles W. McHugh 7/17/2012

Documents changes and additions made to the FlamMap (Ver. 5.0.0) fire modeling software program

FlamMap5 Release Notes Version 3.0 7/17/2012

Page 1 of 26

Release Notes FlamMap 5.0.0 July 18, 2012

Table of Contents Summary of Improvements-Additions .......................................................................................................... 2

Details ........................................................................................................................................................... 4

Installation ................................................................................................................................................ 4

Fuel Moisture Conditioning ....................................................................................................................... 4

Projection Files .......................................................................................................................................... 4

GeoTiff Landscape Files ............................................................................................................................. 5

Spotting ..................................................................................................................................................... 7

Landscape Critique .................................................................................................................................... 9

Analysis Areas ......................................................................................................................................... 10

Run Copy Function .................................................................................................................................. 10

Inputs Tab ................................................................................................................................................... 11

Initial Fuel Moisture Files ........................................................................................................................ 12

Wind Options .......................................................................................................................................... 13

Fire Behavior Outputs Tab .......................................................................................................................... 16

Minimum Travel Time Tab .......................................................................................................................... 17

Vertical and Lateral Search Depths ......................................................................................................... 18

Adding Ignitions and Barriers .................................................................................................................. 19

Burn Probability Analysis ........................................................................................................................ 22

Burn Probability Analysis from a Fire List File ......................................................................................... 25

Treatment Optimization Model Tab ........................................................................................................... 26

For questions concerning the program contact: Charles (Chuck) W. McHugh RMRS, Fire Sciences Laboratory Missoula, MT [email protected] 406.829.6953

mailto:[email protected]


Page 2 of 26

Summary of Improvements-Additions

1. 32-bit and 64-bit Operating System (OS) versions are available. FlamMap 5.0 is only useable in a Windows Operating System.

2. Addresses previously identified bugs and operational issues in FlamMap 3.0. 3. Multiple processors can now be used during fuel moisture conditioning. 4. While all geospatial inputs used in FlamMap are STILL REQUIRED to be in the SAME map datum

and coordinate system. The inclusion of a projection file (.prj) with the Landscape file (LCP) will be read by FlamMap.

a. Allows for the creation of LCP files in a GeoTiff format compatible for use in WindNinja (Ver. 2.1.0 and greater) and ArcMap 10.0.

b. All FlamMap 5.0 geospatial outputs will include a projection file when saved. c. FlamMap 5.0 GeoTiff LCP files ARE NOT useable in FARSITE.

5. Spotting is now included in the Minimum Travel Time (MTT), Burn Probability, and Treatment

Optimization (TOM) functions. 6. Landscape Critique has been included allowing the user to generate a report summarizing

landscape characteristics in either a text format (without graphics) or in an Adobe PDF format (with graphics). LCP critiques can be generated for the full LCP or for any sub Analysis Areas within a FlamMap project.

7. Initial Fuel Moisture files (.FMS) can now be created in FlamMap 5.0 based upon existing fuel models in the LCP. Also allows for the setting of default values for live and dead fuels.

8. WindNinja has been incorporated allowing the user to generate wind vectors for use during a FlamMap simulation.

a. Wind information generated outside of FlamMap using stand-alone versions of WindNinja and WindWizard can still be used.

b. The user can now specify the wind blowing in a downhill direction.

9. New Analysis areas created in FlamMap 5.0 can now be saved in standard LCP format or in a GeoTiff format.

10. FlamMap 5.0 Runs within a FlamMap Project Window can now be copied. All simulation settings are maintained in the copied run.

11. Barriers can now be incorporated into MTT analysis. Barriers can be added from existing shapefiles or created interactively in FlamMap and saved as a shapefile. Barriers can be either filled or unfilled.

12. Ignitions used during Burn Probability analysis can either be random ignitions generated by FlamMap or supplied as a text file. Using a text file of ignitions allows the user to conduct burn probability analysis using a defined set of ignitions to test differences in landscape configuration, wind speed and direction, environmental conditions etc. on model outputs. The following additional outputs have also been added:

a. MTT Perimeters – All perimeters of the modeled fires generated by the specified random ignitions. This file can saved in a shapefile format from FlamMap.

b. FLP English – Flame Length Probability (FLP) in English units (feet). Contains an X-Y Coordinate, Overall Burn Probability, and the conditional probability by six categories of Fire Intensity Levels (FIL) expressed as flame lengths in 2 foot categories (FIL1 – FIL5; FIL6 >12 feet) for every raster cell in the Landscape. Can only be saved as a text file from FlamMap.


Page 3 of 26

c. FLP Metric – Flame Length Probability in metric units (meters). Contains an X-Y Coordinate, Overall Burn Probability, and the conditional probability by 20 categories of Fire Intensity Levels (FIL) expressed as flame lengths in 0.5 meter categories (FIL1 – FIL19; FIL20 >9.5 meters) for every raster cell in the Landscape. Can only be saved as a text file from FlamMap.

d. Fire Size List – Includes the Fire number, X-Y coordinate, and the associated fire size. Can only be saved as a text file from FlamMap. The Fire Number listed in this field is the same Fire Number listed in the MTT Perimeter file. This text file can be used within GIS to generate a point shapefile of ignition locations.

13. Basic Fire Behavior Outputs have had additional outputs included:

a. Information regarding the direction and distance of the Max Spot Direction, Max Spot Distance, and a Combined Max Spot Direction and Distance in a raster format, and Max Spot Vectors.

b. 100-hr and 1000-hr dead fuel moistures are now available.


Page 4 of 26

Details

Installation FlamMap 5.0 is a Windows based program and can only be installed on a computer running Windows 2000, Windows XP, Windows Server Enterprise, Vista, or Windows 7. Both 32-bit and 64-bit Operating System (OS) versions are available. Typically, the 64-bit version of the program should only be installed on computers running Windows XP64, Windows Server Enterprise, Vista or Windows 7, while the 32-bit version can be installed on Windows 2000 or Windows XP. Prior to loading the program ensure you are installing the correct version of FlamMap 5.0 for the operating system type running on your computer. The 32-bit installation file is called FlamMap5.msi and the 64-bit version is FlamMap5x64.msi. Once downloaded, double clicking on the appropriate msi file will start the Windows installation wizard. Some users may require administrative rights to install the program. The default installation location for FlamMap 5.0 is C:\WorkSpace\FlamMap5. The installation location can be changed by the user. However, the selected 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. The FlamMap 5.0 install includes sample data as well as a Help File. At this time, the Help File has not been updated to reflect all the changes and enhancements made to FlamMap 5.0. These detailed release notes are an interim solution.

Fuel Moisture Conditioning A major limitation in FlamMap 3.0 was a defect that limited the use of multiple processors when using a fuel moisture conditioning period. This has been addressed and the use of multiple processers should no longer result in inconsistent and erroneous results.

Projection Files FlamMap 5.0 can now read and use projection files (.prj). However, FlamMap 5.0 CANNOT use this information to “project on the fly” or to re-project data . All geospatial data (e.g., LCP) used in FlamMap 5.0, including any Auxiliary Themes are STILL REQUIRED to be in the same map datum and coordinate system. The Following usage and limitations apply:

• Use of projection files is optional and not required. • The projection file must have the same name as the Landscape (LCP) file but with a .prj

extension and be in the standard ESRI Projection file format. Example: pretreat.lcp and pretreat.prj.

• The projection file should be located in the same directory as the LCP file. • All FlamMap 5.0 geospatial outputs when saved will include a projection file when one is

provided.


Page 5 of 26

GeoTiff Landscape Files FlamMap5 allows for the creation of a GeoTiff LCP. This assumes the user has supplied a valid .prj file with the same name as the source LCP and located in the same directory. At this time, a standard LCP file has to be built first and then converted to a GeoTiff. The Following usage and limitations apply:

a. Creates a multi-band (10 Band) GeoTiff. b. Requires a valid LCP and projection file located in the same directory. c. Allows for the creation of LCP files in a GeoTiff format compatible for use in WindNinja

(Ver. 2.1.0) and ArcMap 10.0. d. GeoTiff LCP files are currently not useable in FARSITE.

There are two ways to convert an LCP to a GeoTiff in FlamMap 5.0 Method 1: From the Main Tool Bar: File > Convert LCP to GeoTiff This will open a dialog box and the user will need to supply the Source LCP File, Source Projection File, and the Destination GeoTiff File. This method can be used anytime FlamMap5 is open. This option has the flexibility of being able to navigate to a different location for the projection file if it is not located in the same directory as the LCP file.

If no projection file is available in the same location as the LCP file the following error box will appear

Clicking OK in the above error message box will close it. To load a projection file clicking the open

button to the right of the Source Projection File text box brings up a “Select Source Projection File” dialog box. Navigate to the correct projection file; make sure the file name is displayed in the File Name text box and click Open. Select the Destination GeoTiff File location and file name. Note: Navigating to and selecting a projection file is not the same as projecting (transforming a dataset from one projection to another) this must occur outside FlamMap in a GIS system. The selected projection file MUST represent the map datum and coordinate system of the LCP data.


Page 6 of 26

Method 2: The second method is to load the LCP file then highlight and right-click on the Landscape in the Project Window and select Create Landscape. This will open a dialog box allowing the user to navigate to the location they want the file saved. Select Save as type, GeoTiff files.

If a valid projection file is not included the following error message will occur:

NOTE: This method REQUIRES that the projection file be in the same directory as the LCP file. The user cannot navigate to the projection file location. GeoTiff File Information The GeoTiff LCP file will consist of multiple bands (10 Bands) with the band orders the same as the input order when building an LCP file. Regardless of the number of data themes in the source LCP, the resulting GeoTiff will always have 10 Bands. For any missing LCP data theme the resulting GeoTiff Band will have a value of 0. GeoTiff LCP files can be built from the entire LCP or for any New Analysis Area the user created. Band1: Elevation Band2: Slope Band3: Aspect Band4: Fuel Model Band5: Canopy Cover

Band6: Stand Height Band7: Canopy Base Height Band8: Canopy Bulk Density Band9: Duff Loading Band10: Coarse Woody Fuels

Attempting to load a GeoTiff LCP file with fewer than the required 10 bands will result in the following error message:


Page 7 of 26

NOTE: FlamMap 5.0 GeoTiff files are only useable within FlamMap 5.0, WindNinja (Ver. 2.1.0 and newer), and ArcMap 10. FlamMap5 GeoTiffs are not useable in the current version of FARSITE or earlier versions of ArcMap (9.3 or earlier) or ArcView.

Spotting FlamMap 5.0 FlamMap 5.0 includes spotting and its effect on fire growth. Spotting is functional in Minimum Travel Time (MTT), Burn Probability, and Treatment Optimization (TOM) functions. Spotting as implemented in FlamMap 5.0 is the same as in Short Term Fire Behavior (STFB) in the Wildland Fire Decision Support System (WFDSS). The desired Spot Probability is set in the inputs section of the MTT Tab, this number is a fractional number, i.e., .1(10%), .5(50%), etc. If spotting is not desired then Spot Probability should be set to 0.

• Required Inputs o Canopy characteristics from spatial layers. o User set foliar moisture content. o Spotting tree species/dbh is always Grand Fir/ 20cm (7.9 inches). o User sets “spotting probability” on the MTT Tab in a fractional format. o Wind speed/direction is constant for entire burn period, but can be gridded (WindNinja

or WindWizard). o Weather is static, though fuel moistures can be conditioned.

• Spotting Process Fire behavior is calculated for each landscape cell simultaneously for a single scenario, and MTT is used to calculate the fastest fire travel paths. Embers are produced only with passive and active crown fire. Nodes are on a fixed grid equal to the MTT spatial resolution. FlamMap fire behavior calculations for active or passive crown fire nodes determine the maximum spotting distance and direction. Sixteen (16) incrementally-sized embers are lofted and followed to determine the maximum spotting distance and direction. Maximum spotting distance & azimuth are calculated using canopy cover, crown fraction burned, elevation, and all available wind information. User-set spotting probability determines which predicted crown fire cells (and associated nodes) can produce spots. Those nodes generate a single ember with random distance from zero to the max for that node. Embers landing on unburnable or already burned substrate do not ignite. Embers landing on burnable substrate always ignite (Finney 2002). • Limitations/Assumptions Spotting only occurs when passive or active crown fire is modeled. Finney (1998) and Scott & Reinhardt (2001) crown fire control methods are available. Each method calculates Crown Fraction


Page 8 of 26

Burned (CFB) differently. CFB and canopy cover are used to determine “number of torching trees” (1-10) used in firebrand lofting height. More embers will be lofted at finer landscape resolutions. Faster rate of spread (ROS) will encounter more nodes, but the absolute number of nodes is static. Because only one ember per node is used there is less chance that an ember will travel the maximum distance compared to Near Term Fire Behavior (NTFB) in WFDSS and in FARSITE. NOTE: Users will probably want to set “spotting probability” higher in STFB and in FlamMap 5.0 than for FARSITE/NTFB tools. • Spotting Outputs FlamMap 5.0 In addition to the standard Crown Fire Activity ASCII, several additional outputs are available on the Fire Behavior Outputs Tab.

• Max Spot Vectors – Can be exported as a shapefile and represents the maximum spotting distance from that cell in meters.

• Max Spot Direction – Can be exported in an ASCII format and represents the maximum spot direction in degrees. This is the direction the spot was lofted NOT the direction the spot is coming from.

• Max Spot Distance - Can be exported in an ASCII format and represents the maximum spot distance units can be in meters (default values) or feet.

• Max Spot (Combined) - For each cell Max Spot Direction and Distance are combined into a single floating point class value. Can be exported in an ASCII format and represents the maximum spot distance in meters and the maximum spot direction in radians. For example, a value of 1351.54980 represents a maximum spot distance of 1351 meters and a maximum spot direction of 315.01 degrees.


Page 9 of 26

The following is an example of how spotting may look in FlamMap 5.0. The underlying theme is the MTT Arrival Time (graduated color) with the MTT Flow Paths (black lines) overlayed.

Landscape Critique Landscape Critique has been included allowing the user to generate a report summarizing landscape characteristics in either a text format (without graphics) or in an ADOBE pdf format (with graphics). LCP critiques can be generated for the full LCP or for any sub Analysis Areas.

• This function is available from the main toolbar: Analysis Area then selecting either Critique PDF or Critique TXT.

• Selecting the desired format from one of the shortcut buttons:

• Highlighting the Analysis Area of interest in the FlamMap project Tree Pane, right clicking

and selecting the desired format; PDF or TXT.


Page 10 of 26

Analysis Areas New Analysis Areas can now be saved in standard LCP format or in a GeoTiff format. This feature can be used to clip a smaller landscape area of interest from a larger LCP. Once a New Analysis Area is created the user needs to highlight and right click on the New Analysis Area then select Create Landscape.

This will open a Select Destination File dialog box allowing the user to navigate to the location they want to store the newly created LCP file. The user must designate Save as Type as either an LCP or GeoTiff. The file type of “LCP and GeoTiff Files (*.LCP, *.tif) “is only a filter for listing of previously created LCP types.

Run Copy Function Within a FlamMap Project Window once a Run has been created it can now be copied. The copied run will be associated with the specific Analysis Area and all simulation settings are maintained in the copied run. To Copy a Run, highlight and right click on it and select Copy. Once Copy is selected the Run Properties dialog box will immediately open and the Run will be added as an item in the list


Page 11 of 26

associated with that Analysis Area. Until the user changes the Run Name, it will show as “Copy of the run name” that was copied.

Note: You cannot copy a Run and move it to a different Analysis Area within the working FlamMap project nor can it be copied to a different FlamMap project.

Inputs Tab In FlamMap 5.0 very little has changed in the operation and look to the Inputs tab in the Run Properties dialog box. However, some additional initial fuel moisture file development capabilities have been added. The inclusion of WindNinja to generate gridded winds and the ability to select Wind Blowing Downhill are the major additions. Operationally, FlamMap analyses can no longer be launched from the Input tab. In FlamMap 5.0 all analyses must be launched from the individual analysis tab. The exception is when Basic Fire Behavior Outputs are selected; they will be calculated with every run.


Page 12 of 26

Initial Fuel Moisture Files An initial fuel moisture file (.FMS) can now be created in FlamMap 5.0 based upon existing fuel models as read from the LCP header file. This capability allows for the setting of default values for live and dead fuels for fuel models in the LCP. Fuel moisture files can still be loaded from existing files or created in FlamMap using a text editor. Clicking on the button in the Fuel Moisture area of the Run > Inputs tab allows the user to create an initial fuel moisture file (.FMS). After clicking the button the Set Default Fuel Moistures dialog box will open allowing the user to set the default fuel moisture values for the fuel models in the LCP. These default values will be applied to the fuel size class and types of every fuel model identified within the LCP. Once set, clicking the OK button will open the fuel moisture file in a text editor. If variable fuel moistures by fuel model and type are required the user can make the necessary adjustments here prior to saving the FMS file. As in previous versions of FlamMap, changes to the saved FMS file can also be made outside FlamMap in a text editor (e.g., Notepad) or

within the FlamMap project by loading the FMS file then clicking on the button. This method also adds a fuel model 0 to the first line of the fuel moisture file. For any fuel model not included the moisture values associated with fuel model 0 will be used in the simulation. While this may allow the user to run a simulation without an error the values here may not be valid for the missing fuel model. The user should ALWAYS check and verify the list of fuel models and their values prior to running a simulation.


Page 13 of 26

FlamMap 5.0 also allows for a single line fuel moisture file (.FMS). This option is useful if the same initial dead and live fuel moisture values are to be applied to every fuel model, size class, and fuel type on the landscape. The required file format is the same, but only 1 line of fuel moisture information is required rather than a line for every fuel model in the LCP, including any custom fuel models. The specified fuel model should be 0, and then followed by the 1-hr, 10-hr, 100-hr, and live herbaceous and live woody as shown below.

Note: The defaulted fuel moistures are not meant to imply a standard set or applicability to specific locations or fuel models; they are only a place holder. It is the responsibility of the user to supply meaningful fuel moisture values for their respective locale and modeling scenario. The initial fuel moisture file (.FMS) is created in FlamMap 5.0 based upon existing fuel models as read from the LCP header file. Because LCP header files may become corrupted the user should verify that the complete set of fuel models in the LCP are listed when creating this file.

In all cases the values provided in the initial fuel moisture files (.FMS) are fixed and will not vary regardless of their elevation, aspect, or shading. It is strongly encouraged to use a fuel moisture conditioning period of 3-5 days for the dead fuels to become spatially variable across the landscape. REMEMBER: foliar moisture content and live fuels are not modified when using a conditioning period. Custom fuel models should also be accounted for in the FMS file.

Wind Options The user can now specify the Wind Blowing Downhill. If the user selects this option only a Wind Speed needs to be specified and the wind direction used in the fire behavior calculations will be based on the aspect theme for each cell in the landscape.


Page 14 of 26

WindNinja (Ver. 2.1.0) has now been incorporated into FlamMap 5.0 allowing the user to generate gridded wind vectors for use during a FlamMap simulation. Gridded winds can be used in all simulations (Basic Fire Behavior, MTT, Burn Probability, and TOM). Users are encouraged to have a full understanding of the WindNinja model prior to use in FlamMap. If not, users should familiarize themselves with the WindNinja model, its limitations and assumptions, and are encouraged to work through its reference materials and tutorials prior to using this function in FlamMap 5.0. Information specific to WindNinja is available at: http://www.firemodels.org/index.php/research-systems/windninja To use WindNinj derived gridded winds select the Generate Wind Vectors radio button, specify the Azimuth (direction) that the winds will be coming from and the wind speed to characterize the wind field for the particular wind scenario. The wind speed and direction values specified here are used as inputs for all WindNinja simulations. This input wind speed and direction can be thought of as roughly an average surface wind at 20 feet above the vegetation over the LCP area.

WindNinja Inputs The user should also click on the Wind Ninja Options button which has other controls for WindNinja simulations.

• Resolution Settings: A default ideal spatial Resolution will be shown and is driven by

computer memory issues, especially when running FlamMap in a 32-bit operating system environment. The user does not have to accept this setting and can change it if desired. However, setting it finer may result in no outputs being generated from the simulation.

http://www.firemodels.org/index.php/research-systems/windninja

http://www.firemodels.org/index.php/research-systems/windninja


Page 15 of 26

• Diurnal Settings: Selecting the Use Diurnal Simulation box will use WindNinja’s model to simulate the effects of diurnal slope winds. It is designed to compute small scale slope winds, but not larger scale valley winds. The slope winds will have some effect of producing valley winds, but it will be slight. Also, the model will not simulate other buoyancy driven flows such as sea or land breezes.

During the wind computation, the wind speed and direction values specified previously on the Inputs Tab will be combined with the diurnal winds to produce a final wind field. Output of simulations done with a light LCP average wind speed may show a significant effect of the diurnal winds. However, a strong LCP average wind speed will not show much diurnal affect because the diurnal winds are overpowered by the stronger input wind speeds.

Diurnal simulations also require the additional input fields of Day, Time, Time Zone, Cloud Cover, Air Temp., and Longitude. While initial Longitude and Time Zone will be displayed they will need to be adjusted by the user for their specific area. The same is true for the initial displayed Air Temp and Cloud Cover values as they are really only place holders and may not be relevant to the current simulation. The Calculation Day and Time values are based upon current system settings from your computer. The user will likely need to adjust all these values (Day, Time, Air Temp, and Cloud Cover, Longitude, and Time Zone) as needed for the specific simulation. The user can also decide to select the Use Conditioning Period End. To use this setting valid wind and weather files and a conditioning period must first be specified on the Inputs tab. The WindNinja model will then use the conditioning period End Day and Time ONLY for the Calculation Date/Time. The user will still need to enter representative Air Temp and Cloud Cover values for the simulation.


Page 16 of 26

WindNinja Outputs Whenever WindNinja is used in FlamMap 5.0 three outputs are automatically generated. Wind Vectors, Wind Direction, and Wind Speed. These outputs will be listed with the specific run.

• Wind Vectors: Can be saved as a shapefile which can be used in ArcMap. This shapefile can also be added as an Auxiliary Theme > Wind Vectors in FlamMap 5.0.

• Wind Direction: Can be saved as an ASCII Grid File in degrees and represents the direction

the wind flow is coming from. • Wind Speed: Can be saved as an ASCII Grid File and represents the wind speed in miles per

hour.

Fire Behavior Outputs Tab In FlamMap 5.0 very little has changed in the operation and look to the Fire Behavior Outputs tab in the Run Properties dialog box. Some additional Non-fixed Fuel Moisture (100-hr and 1000-hr) outputs have been added and additional outputs associated with spotting as discussed previously. FlamMap 5.0 will detect and use the maximum Number of Processors available. However, the user can adjust this using the spin box to reduce the Number of Processers or adjust as needed. In FlamMap 5.0 you are no longer constrained to using a single processor when fuel moisture conditioning is used. When Fire Behavior Outputs are selected; they will be calculated with every run.


Page 17 of 26

Minimum Travel Time Tab

While very little has changed in the operation and look In FlamMap 5.0 to the MTT tab some significant features have been added. These include the ability to provide ignitions from a text file as well as select additional outputs from the burn probability analysis. Settings controlling the Spot Probability used during MTT, Burn Probability Analysis, and Treatment Optimization Model (TOM) are set here. Spot Probability values must be between 0 and 1, where 1 equals 100% and 0 will turn spotting off. A value of 0.50 is a 50% probability. Technical details of how spotting is implemented in FlamMap 5.0 were covered in-depth previously. The ability to use barrier files has been included and can be used in MTT only.


Page 18 of 26

Vertical and Lateral Search Depths Two new settings have been added which control the MTT algorithm. Search depths are distances (number of cells) that the MTT algorithm uses to determine when to terminate searching in the vertical and horizontal directions. They are actually thresholds for sequentially failing to find the soonest arrival time. For example, if the lateral search depth is set to the number 3, MTT will keep searching farther and farther to the right or left from the starting point, as long as it succeeds in finding the fastest path, until it fails 3 times in sequence. Larger values will cause longer computation times because it will require more sequential failures before it gives up in a given direction. The way the algorithm is structured, the lateral search depth is better set higher than the vertical search depth (require more rows before failure than columns).

For homogeneous landscapes, larger values will increase the chance that fastest paths are found between cells (nodes) with farther separation. In other words, MTT will be more accurate. For very heterogeneous landscapes (e.g. every cell has different spread rates or maximum spread directions) then the settings for search depths will matter much less.

Default values for normal use are: Vertical=4 and lateral =6. To increase speed or for very heterogeneous landscapes, settings might be reduced to Vertical=2 and Lateral=3.


Page 19 of 26

Adding Ignitions and Barriers In FlamMap 5.0, ignitions and barriers are handled as generic shapefiles. Where and how they are loaded determines their use in FlamMap. Because of this approach to create ignitions and define barriers the driptorch icon is nothing more than a mouse pointer. The user can create ignitions for use in MTT and TOM following the same methods as in FlamMap3, while barriers are only useable in MTT. Barriers are added at the Minimum Travel Time (MTT) Tab and can be added from an existing shapefile or created interactively in FlamMap and saved as a shapefile, and then added to the run as a barrier. Barriers can be points, lines or polygons depending on the pattern of mouse button clicks used and either filled or unfilled. Only closed polygons can be filled with an unburnable interior.

Method 1: Adding existing shapefile barriers After opening the Runs dialog box open the MTT tab. Clicking on the in the Barriers section will open a dialog box allowing you to navigate and select the appropriate shapefile. Make sure the file name is displayed in the File Name text box and click Open.

Clicking in the Fill Barriers check box will fill the barrier (makes it non-burnable), unchecking the box will leave the interior of the polygon unfilled and burnable. Only closed polygons can be filled and made non-burnable. Once a barrier is loaded the Clear Barriers button will no longer be grayed out and clicking this Button will clear any loaded barrier from the Run Properties.


Page 20 of 26

Method 2: Adding barriers interactively Barriers can be drawn and added within a FlamMap project. The process for creating a barrier shapefile is the same as for creating an ignition within FlamMap.

To define barriers on the display pane you must use the button. At this point consider the driptorch icon as nothing more than a mouse pointer. Barrier files can be points, lines or polygons depending on the pattern of mouse clicks. Only closed polygons can be filled and their interiors made unburnable.

• Point Barrier - One left mouse click followed by one right mouse click without moving the cursor.

• Area Barrier - A series of left mouse clicks ending the polygon with a right mouse click. This will create a closed polygon. You should not try to close the polygon; this is done automatically after the right button click. Only closed polygons can be filled and their interiors made unburnable.

• Line Barrier - 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. Any unclosed line polygon cannot be filled and fire can burn within the area regardless of whether the Fill Barriers check box is selected or not.


Page 21 of 26

After you have defined the barrier; from the Main Toolbar select: Options > Shape > Save to File. This will open a Save As dialog box where you can navigate to the location you want to save the barrier shapefile. Prior to saving the barrier file you can erase it from the display pane by selecting Options > Shape > Clear.

MTT Barrier Examples:

The first example illustrates a filled barrier. The background graduated color is the MTT Arrival Time with the MTT Flow Paths Overlaid, closed polygon barrier (grey outline) with a line ignition (solid black). In this example, the fire spotted over the filled barrier and continued on the lee side spotting again.

The second example illustrates an unfilled barrier. The background graduated color is the MTT Arrival Time with the MTT Flow Paths Overlaid, closed polygon barrier (grey outline) with a line ignition (solid black). In this example the fire spotted into the unfilled barrier and then spotted out of the area and continued on the lee side. Note that the surface fire did not burn through the polygon perimeter, but only entered the interior of the polygon through spotting.


Page 22 of 26

Burn Probability Analysis Ignitions used during Burn Probability analysis can either be random ignitions generated by FlamMap or supplied as a text file. Using a text file of ignitions allows the user to conduct burn probability analysis using a defined set of ignitions to test differences in landscape configuration, wind speed and direction, environmental conditions etc. on model outputs. The following additional outputs have also been added: MTT Perimeters, Flame Length Probabilities (FLP) in both metric and English units and in two different groupings, FLP – 6 Bin English, FLP – 20 Bin Metric, and Fire Size List.

Setting up a burn probability analysis using Random ignitions in FlamMap 5.0 is the same as in FlamMap3, with the exception of defining the Spot Probability and selecting any additional outputs.


Page 23 of 26

Once the run is completed all of the selected outputs will be available in the analysis area. Below is an output where the MTT perimeters are shown. In this example, only 100 Random Ignitions were selected with the MTT perimeters in red and with Burn Probability as the visible landscape theme.


Page 24 of 26

Burn Probability Outputs As with all FlamMap outputs right-clicking any of the associated burn probability outputs will open a short cut menu from which you can use the Save As option to save the files. Double-clicking on any of the text outputs (FLP English, FLP Metric, or FireSizeList) in FlamMap will open these files in a text editor. Use caution when opening the FLP files as these file sizes can be quite large and may take some time to open.

a. MTT Perimeters – All perimeters of the modeled fires generated by the specified random ignitions. The number listed in the Fire Number (Fire_Num) field is the same Fire Number listed in the Fire Size List File. Fire Numbering starts with 0 and ends with the number of specified ignitions minus 1. For example, if 100 random ignitions are specified the range of fire numbers will be 0-99. This file can ONLY be saved in a shapefile format from FlamMap. It can be used in GIS or loaded into FlamMap as an Auxiliary Vector Theme.

b. FLP – 6 Bin English – Flame Length Probability (FLP) in English units (feet). Contains an X-Y

Coordinate, Overall Burn Probability, and the conditional probability by six categories of Fire Intensity Levels (FIL) expressed as flame lengths in 2 foot categories (FIL1 – FIL5; FIL6 >12 feet). This output contains an X-Y for every raster cell in the Landscape. It can only be saved as a text file from FlamMap.

c. FLP – 20 Bin Metric – Flame Length Probability in metric units (meters). Contains an X-Y

Coordinate, Overall Burn Probability, and the conditional probability by 20 categories of Fire Intensity Levels (FIL) expressed as flame lengths in 0.5 meter categories (FIL1 – FIL19; FIL20 >9.5 meters) for every raster cell in the Landscape. Can only be saved as a text file from FlamMap. Its appearance is similar to the English unit version shown above, except 20 separate categories are visible.

d. FireSizeList – Includes the Fire number, X-Y coordinate, and the associated fire size (acres).

It can only be saved as a text file from FlamMap. The number listed in the Fire Number field (Fire_Num) is the same Fire Number listed in the MTT Perimeter file. Fire Numbering starts with 0 and ends with the number of specified ignitions minus 1. For example, if 100 random ignitions are specified the range of fire numbers will be 0-99. This file can be saved and used in additional burn probability analyses as a Fire List File on the same landscape or used within a GIS to generate a point shapefile of ignition locations.


Page 25 of 26

Burn Probability Analysis from a Fire List File To use a fire list file the user needs to check the Radio button for From Fire List File. Clicking on the

will open a dialog box allowing you to navigate and select the appropriate Fire List File. Make sure the file name is displayed in the File Name text box and click Open. Clicking on the Clear Fire List File will remove the loaded fire list file from the run. The Fire List File can be a Fire Size List file from a previously saved burn probability analysis in FlamMap 5.0 or from a text file created by the user. If the fire list is created outside of FlamMap 5.0 by the user it needs to be a comma or space delimited text file following the example format below. The fire number needs to start at 0 and is inclusive in the total number of ignition points, with an XStart (Latitude) and YStart (Longitude). Column headers are not required in the text file; however, the input order must follow the specified format.

Note: The provided X-Y start values need to be in the same datum and coordinate system as the landscape. A successfully loaded Fire Size List File will return the following message:

An unsuccessfully loaded Fire Size List File will return the following message:

Causes for this message are related to incorrect formatting or X-Y coordinates that are not spatially coincident with the landscape due to differing extents, the map datum or the coordinate system.


Page 26 of 26

Treatment Optimization Model Tab In FlamMap 5.0 very little has changed in the operation and look to the Treatment Optimization (TOM) tab in the Run Properties dialog box. However it is important for the user to remember that some settings on the MTT tab control and affect TOM modeling runs. These are Spot Probability and the Vertical and Lateral Search Depths. Maximum Simulation Time has no effect on TOM as the entire landscape is always evaluated.