Every district page shows what the current run says (or states that the run does not cover the district), the static baseline the map falls back to, and what the numbers cannot mean.
Coverage of the run this deployment ships
Prediction date 2026-09-16. 60 of 64 districts carry at least one horizon row in this run. Coverage of that run: produced 25 units at the 7-day horizon and 49 units at the 15-day horizon, covering 60 of 64 districts (coverage status: partial). A district can appear at one horizon and not the other.
Districts without a row in this run: Jhenaidah · Barisal · Khagrachhari · Bandarban. Those pages say so; nothing is interpolated.
Browse by division
The list below is generated from the app's district table, so the pages and the map agree.
The outlook section is the model output for the run this deployment ships.
The baseline section is a static entry shipped with the app, used when a run does not cover a district. It is not a forecast.
The history section appears only when this deployment has loaded the historical event archive; otherwise the page says that no archive is loaded rather than implying there is no history.
Questions and answers
Why is a district page missing an outlook?
Because the run this deployment ships did not produce a row for that district. Runs are sometimes partial (upstream data gaps); the snapshot carries a coverage stamp that says how partial, and the status page reports it. Those district pages are marked noindex and kept out of the sitemap until a run covers them, so search results never present a baseline as a forecast.
Do these pages cover upazilas?
No. The forecast unit is the district (ADM2); the ADM3 boundaries exist for the event archive and the map, not for the published outlook.
Content reviewed 2026-09-16. HazardNet is decision support, not an official warning service — see the methodology for scope and limitations.