日本地球惑星科学連合2016年大会

講演情報

口頭発表

セッション記号 S (固体地球科学) » S-SS 地震学

[S-SS33] 都市の脆弱性が引き起こす激甚災害の軽減化プロジェクト

2016年5月23日(月) 13:45 〜 15:15 105 (1F)

コンビーナ:*酒井 慎一(東京大学地震研究所)、平田 直(東京大学地震研究所)、佐藤 比呂志(東京大学地震研究所地震予知研究センター)、佐竹 健治(東京大学地震研究所)、鶴岡 弘(東京大学地震研究所)、座長:平田 直(東京大学地震研究所)、酒井 慎一(東京大学地震研究所)

14:45 〜 15:00

[SSS33-05] ハザード情報と地形情報を含めたインタラクティブな津波避難経路選定支援ツールの開発

*井ノ口 宗成1関川 貴大2田村 圭子2林 春男3 (1.静岡大学、2.新潟大学、3.京都大学)

キーワード:マイクロメディアサービス、津波災害、避難経路、都市の脆弱性

1. Background and Objectives
Based on lessons learned from 2011 East Japan Earthquake, Cabinet office of Japan has promoted local governments and communities to develop “Community Disaster Management Plan”. Local governments started to develop the plan in the view of the circumstances in their regional characteristics. Niigata city also organized the workshops in order to develop it against tsunami disaster with residents. Only a few residents participated in this workshops and they build their capacity due to workshop schedule and largeness of place. Other residents did not have opportunities to discuss about disaster prevention. Against this issue, we decided to develop an application supporting for individual disaster management plan in analyzing hazard risks and land features around their habitation area.

2. Clarification of Work-flow for Developing Evacuation Plan at Tsunami
We conducted preliminary survey in these workshops in order to design the work-flow for users to develop their own disaster management plan at tsunami. Especially, in this research, we narrowed down a target to evacuation plan because evacuation is most important behavior to save their lives. Through the workshops in Niigata city, we found the processes of developing evacuation plan was consisted of 5 steps. 1) Introduce fear of tsunami disaster and countermeasure at tsunami disaster, 2) Survey the evacuation route from each participant’s house to public tsunami evacuation center, 3) Discuss potential risks behind participants’ community, 4) Design strategic plan for their community and to discover potential evacuation center such as non-pubic high-rise buildings, 5) Report and share the result of their discussion. Furthermore, it is a unique feature in these workshops to set 2 evacuation goal. First goal is near-by their habitation place and it is built in high elevation area. Second one is far from the impacted area by tsunami and it is located in higher elevation area than first one. This was followed by lessons learned from Kamaishi Evacuation Story at East Japan Earthquake in 2011.

3. Development of Prototype of User-Interactive Application
We developed a prototype of application based on the system-design described above. In this application users can detect rational evacuation route considering hazard risks and land features. Because we supposed that users cannot detect it at one time, we decided to develop the application as web-based and user-interactive application. This means our developed application should respond the result of analyzing the risks around their detected evacuation route in conjunction with the modification of users’ evacuation route. Finally we developed the prototype of application following 7 users’ steps: 1) Set start point for evacuation, 2) Set first evacuation goal, 3) Set second evacuation goal, 4) Search shortest evacuation route, 5) Review change of elevation on evacuation route, 6) Judge hazard risks and land feature on evacuation route, 7) Download evacuation route dataset as a local file. From step1 to step5, we utilized Google Map API for searching specific place name or street address, and for evaluating transition of elevation on the detected evacuation route. In step7, users can download the detected evacuation route as GPX file for reviewing it on GIS software they have later.

4. Discussion
We implemented the application and published it for 10 days in order to examine its effect. Through this examination, we gained 1,960 users’ logs. Deciphering those logs, only 223 of rest 851 users detected their rational evacuation route considering hazard risks and land features around the detected evacuation route. We found that the complicated user-interface and system transaction caused this result. Against these issues, we are planning to modify it with higher user-friend interface and to build a story for developing their evacuation route in it.