[Burn-P3+ FireSTARR FR]: Default elevation

[shreeramsenthi]

Contact Details

No response

What is needed?

In pairwise comparisons of BP3+ FireSTARR and BP3+ Prometheus, Prometheus often burns pixels adjacent to NA cells much more readily than FireSTARR, even though FireSTARR generally burns more readily than Prometheus due to vector- / cell-based modeling differences.

This behaviour in FireSTARR is not unexpected since slope can't meaningfully be calculated against adjacent NA pixels in the elevation map. Prometheus probably gets around this using the default elevation parameter, although we are not currently providing an explicit default elevation to Prometheus--it might not even be possible with the current version of Pandora.

It might be worth:

• understanding the default behaviour for the default elevation for Prometheus / Pandora
• providing a new explicit default elevation if the behaviour leads to unrealistically high slopes at edges
• more explicit guidance that all grids should be buffered beyond the area of interest
• providing a default elevation option for all fire models?

How will this improve the project or tool?

No response

Approvals Process

• Testing For Issue
• Merge

[BadgerOnABike]

Wouldn't be terribly difficult to calc the average elevation and use that as the default. Could even take the average elevation outside of aggressive slope zones if we wanted to get really fancy with it.