Document and review of ThinkHazard data changes
Open
@matamadio is already working on this.
Since Oct 28, 2025.
- Dominant language
- Python
- Stars
- 47
- Forks
- 22
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Before publishing changes to ThinkHazard on the tool, we need to complete the following:
- Document change made and the reasons supporting the change to each hazard - whether dataset or approach.
- Document impact of change in terms of hazard class distribution, capturing key hotspots of most change
- Get review of changes (need ot identify internal / external reviewers
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.