TH scores update: TSUNAMI
Open
@stufraser1 is already working on this.
Since Oct 30, 2025.
- Dominant language
- Python
- Stars
- 47
- Forks
- 22
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Hazard Processing Method
- Data Source: 3 return periods (RP100, RP500, RP2500) - inundation depth rasters
- Unit: m (meters)
- Default RP-Specific Thresholds:
- RP100: 2.0 m
- RP500: 1.0 m
- RP2500: 0.5 m
- Default Area Threshold: 0%
Workflow: Different from Earthquake/Cyclone - uses MAJORITY values
- Extract all pixel values for each RP raster within each admin unit
- For each RP, calculate:
- MAJORITY inundation depth = most common positive value (ignoring zero/nodata)
- Area percentage = % of pixels above RP-specific threshold > using 0% due to sparse data format
- Check if unit has ANY inundation data (majority > 0 in any RP)
- Check if majority value meets RP-specific threshold AND area threshold % is met for each RP
- Score = count of RPs meeting both thresholds (0-3)
Scoring Logic (different from earthquake/cyclone):
- No inundation data in any RP → Score -1 (not affected)
- Has inundation but 0 RPs meet thresholds → Score 0 (below threshold)
- 1 RP meets thresholds → Score 1
- 2 RPs meet thresholds → Score 2
- 3 RPs meet thresholds → Score 3
Comparison
New score distribution: ADM2
New score distribution: URBAN
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.