Maladaptation, fragmentation, and other secondary effects of centralized post-disaster urban planning: The case of the 2011 “cascading” disaster in Japan
This report details how previous studies have documented the negative impacts and unexpected secondary effects of post-disaster housing development. Here, it builds on this tradition to explore how post-disaster urban planning and risk mitigation measures affect internal migrations after a major disaster.
In the aftermath of the 2011 Great East Japan Earthquake and Tsunami, the Japanese government put forward significant efforts to provide safe housing and land in more than 20 cities. The report used GIS spatial analysis to identify urban footprint changes, which proved to be reliable indicators of internal migration. Our results reveal the secondary effects of planning interventions, and more specifically, how the maladaptation measures triggered rapid urban sprawl and increased risks of landslides and vulnerabilities in mountainous areas.
It also finds increased urban fragmentation, both socially and spatially. Maladaptation, urban fragmentation, and rapid changes in urban footprints emerged as the consequences of centralized government-mandated planning and housing development. It concludes that the uncertainty surrounding dynamic recovery processes requires incremental adaptive action. Planners and local authorities must recognize and remain attentive to the cascading effects of centralized planning decisions.
Download
Editors' recommendations
- Learning from megadisasters: A decade of lessons from the Great East Japan Earthquake
- Stories from the frontline: Japanese staff of the UN reflect on the 2011 Great East Japan Earthquake
- Japan’s disaster lessons aren’t just about expensive hardware
- Efforts made to archive 2011 Japan disaster data to pass on lessons
- What Japan’s disaster-proofing strategies can teach the world
- The Great East Japan Earthquake: lessons learned, 10 years on
Explore further
Also featured on
Is this page useful?
Yes No Report an issue on this pageThank you. If you have 2 minutes, we would benefit from additional feedback (link opens in a new window).