List view
Development push to update TH datasets, scores and pipeline. ## Expected Results 1. Expanded coverage – ThinkHazard! incorporates both updated administrative boundaries and functional urban boundaries, enabling hazard screening aligned with real urban conditions. 2. Updated hazard classifications – Hazard level classifications are recomputed using the new data layers and boundary types, maintaining transparency and comparability. 3. Improved user interface – The platform presents a cleaner, multilingual user interface with updated branding, consistent navigation, and integration of identified priority fixes. ### Task 1. Update administrative and urban boundaries - Enhance the ThinkHazard! workflow to allow users to screen hazard levels for both official administrative units and real urban areas. - Improve search functions to allow users to search by different city or country names; - Propose and present wireframes to GFDRR for review, ensuring minimal UI disruption and consistent user experience across boundary types while promoting new real urban area hazard levels. - Update official administrative boundaries from World Bank Group official datasets, including the representation of disputed areas. - Integrate real urban areas to be provided by GFDRR (e.g., list extracted from GHS-UCDB R2024A – GHS Urban Centre Database 2025). ### Task 2. Integrate updated hazard data - Remove visible links and dependencies from GFDRR GeoNode including links to hazard layers, web services and any other information. - Support ingestion of updated hazard level classifications for admin boundaries and real urban areas into ThinkHazard! test and production database. Computation of hazard levels to be conducted and provided by the World Bank team for all administrative and urban boundaries. - Ensure both websites and API return updated hazard levels for official admin boundaries and real urban areas; ### Task 3. User interface revision and clean-up - Update logos, pop-ups, and information pages (e.g., About). - Provide translations for new and revised content in English, French, and Spanish. - Address any other priority issue flagged in the GitHub issue tracker (ThinkHazard! 1st priority issues).
Due by February 26, 2026•8/18 issues closed- Overdue by 8 year(s)•Due by August 31, 2017•14/16 issues closed
- No due date•38/38 issues closed
This version handles all hazard types, but does not have all the data ... Admin UI + Logical Framework are done. Due date is end of the year, <!--- @huboard:{"order":2.5} -->
Overdue by 10 year(s)•Due by December 18, 2015•23/23 issues closedDue date is May 2016, this version will be presented publicly at a conference.
Overdue by 9 year(s)•Due by May 2, 2016Expected end of March 2016, handles all hazard types + load.
Overdue by 10 year(s)•Due by March 31, 2016•26/26 issues closedThis milestone includes the processing scripts and updates on the front-office. Due date is mid-december
Overdue by 10 year(s)•Due by December 14, 2015•33/33 issues closedThis is still an alpha version, but it takes into account results from user testings, with a revisited UI. The model should also be stabilized.
Overdue by 10 year(s)•Due by September 15, 2015•62/62 issues closed