Developer Updates
This section contains information about the development of the tool, including updates, known issues, and other relevant information. We will make every effort to keep this page up-to-date.
Known bugs:
- None at this time!
Known issues:
⚠️
Especially on first map view, the burn metrics may take several seconds to render properly. This can typically be resolved by refreshing the page, or switching between the
Continious and Categorical burn severity layer, which will trigger a re-render. Additionally, the burn severity layers are not checked by default, you will need to check one of Continious or Categorical to see the burn severity metrics.⚠️
Very large fires suffer some performance limitations, and may not render properly within the tool. If you are having issues with your analysis, please reach out to npg@berkeley.edu for assistance.
Known quirks / limitations:
ℹ️
Pages take a few seconds to load upon changing pages - this is expected
ℹ️
The combinaton of
Fire Event Name and Affiliation must be unique. If you re-submit a request using the same Fire Event Name and Affiliation, you will overwrite the existing products within the server. Please feel free to do so if you’ve made a mistake or if you are experimenting!If something breaks, or otherwise goes awry, we will receive logs of your session and will hopefully be able to resolve your issue - feel free to reach out to mweltman-fahs@berkeley.edu and/or npg@berkeley.edu with any additional context you think may be useful!