# Treatment Interactions and Buffering in FTEM

Within FTEM, there exist both wildfire points and perimeters:

- A wildfire point consists of a geographic location (latitude and longitude of the approximate point of origin) as well as a size in acres but contains no other information to define where the fire burned.
- A wildfire perimeter consists of one or more polygons representing its outer burned edge, or perimeter, in addition to a point representing is approximate point of origin.

The same is true for treatments. That is, some treatments only contain a point location and size while other treatments also include a multi-polygon shape to define their extent. The purpose of this topic is two-fold. That is, it discusses how wildfire treatment interactions are initially determined by a utility program as well as how they can be updated by FTEM users within the application.

## Wildfire Points

In all cases, a circle with its center at the wildfireâ€™s point of origin is used to determine the potential treatment interactions for a wildfire point. For the utility program, the radius of the circle is based upon calculating the length of an ellipse whose length is 1.5 times its width and whose area is equal to the size of the wildfire. The radius of the circle equals the length of the ellipse. While the exact length of the ellipse varies by acreage, the distances below provide an indication of typical buffering distances given fire size:

- 0.1 acre fire = 28 meter buffer
- 1 acre fire = 88 meter buffer
- 3 acre fire = 152 meter buffer
- 10 acre fire = 278 meter (0.17 mile) buffer
- 100 acre fire = 879 meter (0.55 mile) buffer
- 640 acre fire = 2224 meter (1.38 mile) buffer
- 5000 acre fire = 6216 meter (3.86 mile) buffer
- 10,000 acre fire = 8791 meter (5.46 mile) buffer

While the above buffers are the default, users may choose to specify a larger buffer radius around points, up to 10,000 meters for wildfire points, if needed.

## Wildfire Perimeter Polygons

In all cases, a buffered perimeter is used to determine the treatment interactions for a wildfire with an associated perimeter. For the utility program, the perimeter is buffered by one meter. Within the FTEM application, users may choose to specify a buffer size up to 1,500 meters to buffer around the wildfire polygon perimeter. For point treatments, the treatment is included if the point falls within the buffered perimeter. For polygon treatments, the treatment is included if the polygon intersects the buffered perimeter.

The area of intersection for polygon treatments is the area of intersection between the actual fire perimeter (as opposed to the buffered perimeter) and the polygon treatment. The area of intersection must be set manually for point treatments.

## Automated Setting of Treatment Interactions

Potential treatment interactions are only added when a fire is first added to FTEM. When a new fire is added, a flag is set within the record for the wildfire indicating that treatment interactions have not been initialized for the wildfire. A separate utility is run that uses this flag to determine that treatment interactions need to be set for a given wildfire. During normal processing, wildfires (and updates to existing wildfires) are first pulled from IRWIN. Next, perimeters (new as well as updates) are pulled from NIFS. After this step is completed, point treatments are updated followed by polygon treatments. The last utility to run is the utility that adds the potential treatment interactions.

For fire polygons, treatment interactions are defined by real spatial intersection between the perimeter and treatment points and polygons. If the fire has a perimeter (polygon) the treatment interaction is defined by real spatial interaction between the fire perimeter and the treatment point or polygons.

For fire points, treatment interaction is defined by real spatial interaction between the treatment point or polygons and a buffer created around the fire point. The buffer is created around the fire point using the following formula:

Buffer in meters = math.sqrt(1.5 * 4046.85642 * dailyAcres / math.pi) * 2

If no dailyAcres is specified a default value of 10 is used.