Abstract
At the early phase of the Great East Japan Earthquake a vast number of tweets were made on Twitter. Even though many of them were calling for emergency rescue, they were not found timely due to the vast number of tweets including wellintentioned tweets to support those emergency rescues. In order to deal with the situation, the authors developed and launched a website on March 16, 2011, which automatically extracts rescue requests, categorizes similar statements into several statements and then lists them. This paper covers in detail not only the technology of the system but also how it has already collaborated and been applied to #99japan, a project to support delivering emergency rescue requests. Note that #99japan is an activity to monitor the process of the rescue based on Twitter and coming from the thread started by temporary volunteers who organized on a Japanese textboard 2 “2channel.”
Highlights
In the early stages of the Great East Japan Earthquake, a vast number of tweets were related to high-urgency rescue requests; most of these tweets were buried under many other tweets, including some well-intentioned retweets of the rescue requests
This paper describes the technology of the system and the start of a rescue project #99japan
Note that #99japan originated from a thread of the Japanese textboard 2channel, which was launched by some volunteers within two hours of the disaster’s occurrence
Summary
In the early stages of the Great East Japan Earthquake, a vast number of tweets were related to high-urgency rescue requests; most of these tweets were buried under many other tweets, including some well-intentioned retweets of the rescue requests. に,筆者らは 2011 年 3 月 16 日,Twitter 上の救助要請情報をテキストフィルタリ Rescue Activity for the Great East Japan Earthquake This paper describes the technology of the system and the start of a rescue project #99japan.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.