Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

Download the whole TRG as a PDF

...

  1. Introduction
  2. Development philosophy of PHOENIX
  3. The Fire Grid
  4. Inputs
  5. Fire Behaviour
  6. Fire Perimeter Propagation
  7. Asset Impact
  8. Outputs

8. Outputs

worddav9009a5c28d675b76b90db0f61ae2dc65.png


PHOENIX produces a wide range of outputs. Vector perimeter isochrones are a standard output, produced both as ESRI Shapefiles and Google Earth KMZ files. In addition, a wide range of gridded cell values about fire characteristics can be outputted in various formats. A sample is provided in Table 10. These can be presented as means, maximums or ranges for each Fire Grid cell. This information is provided over a range of file formats including:

  • Shapefiles containing ignition points and incremental fire perimeter isochrones as well as StaticGrid;
  • Image formats (PNG and PGW files) of fire perimeter;
  • ASCII text files viewable in text editors and in GIS;
  • XML files containing state-wide summary data viewable in MS-Excel or MS-Access; and
  • CSV files containing gridded data viewable in MS-Excel or MS-Access.


Table 10. Gridded PHOENIX RapidFire outputs


Attribute

Definition

Time Burnt (hours since the fire started)

Time of first impact

Effective Rate of Spread

Rate of spread perpendicular to the fire perimeter

Effective Intensity (kW/m)

Intensity based on the Effective Rate of Spread

FDI

Fire Danger Index

Spotting Distance (m)

Spotting distance travelled

Spotting Time (hours since the fire started)

Time that spot fire was initiated

Time Suppressed (hours since the fire started)

Time the fire in the cell was suppressed

Suppression Rate (m/h)

Suppression rate

Suppression Efficiency (%)

Suppression efficiency achieved

Went Out (hours since the fire started)

Time the fire in the cell went out

The input variables relating to each grid cell (i.e. fuel load, weather at the time of burning, slope, aspect) are also provided as standard gridded outputs. KMZ files are time-stamped, providing for progression animation within Google Earth. In addition, an animated visualisation of the fire plume is generated in KMZ format, with values derived from the ember convection module. All outputs are spatially referenced and can be displayed in standards software packages. Alternative run modes of PHOENIX produce additional outputs not described here.

...


There are five (5) simulation types (Figure 37): General, Batch, Grid Analysis, Batch All Cells and Batch Ascii Grids. There is also a Static Grid mode where every cell is assumed to burn simultaneously, but this does not include aspects of dynamic fire behaviour, such as ember density and convective strength, included in the simulations. The outputs from each simulation type differ.

Image RemovedImage Added

Figure 37. Simulation types

  • General: run a single fire or multiple fires at the same time
  • Batch: is designed to run combinations of a set of fires, under a set of fire histories, with a set of fire suppression scenarios and a set of road and firebreak scenarios. These conditions are specified in the 'Advanced' > 'Batch Parameters' table.
  • Grid Analysis: is used to do an asset impact analysis of a single or grid of fires in the landscape. Only cells with an asset impact are saved for further analysis outside PHOENIX and only summary statistics are saved.
  • Batch_All Cells: is similar to the Grid Analysis process except all cells from all fires are saved in CSV files for further analysis (can be massive amounts of data).
  • Batch_AsciiGrids: as for Grid Analysis except ASCII grids for flame height and intensity are produced for each fire (can be massive amounts of data).
  • Static Grid: fire, fuel, weather and terrain characteristics for each cell within a specified area are calculated without including the dynamic aspects of fire behaviour. This mode is similar to a lot of older bushfire risk analyses undertaken with GIS analysis.

...