Highlights: 2,200 reports | ICTs for Disaster
Problem and Context
Nepal was hit by a massive 7.8 Mg earthquake on April 25. The total count of deaths and injuries were in the thousands. In the confusion and chaos that followed the quake, some people were looking for help while others were looking for ways to help. However, those who were seeking help did not know where to find it and those who were trying to help did not necessarily know where exactly their help was needed. Essentially, what everyone was looking for in that period was information. Crucially, it was the information that was missing.
On April 26, Kathmandu Living Labs deployed QuakeMap.org with the aim of bridging this information gap so that rescue and relief efforts can be informed and expedited by reports from the ground
What information does QuakeMap.org seek?
Problems: What is needed and where?
Solutions: Who is able to provide it and what other help has reached there already?
From whom does it seek the information?
These information were fed into QuakeMap.org directly by people and organizations on the ground. Based on the positively reinforcing experiences with crowdsourced information in Nepal and abroad, we selected crowdsourcing as the way of getting direct, primary and disaggregated source of information onto Quakemap.org.
How does it get the information?
Despite the massive quake, services like the internet, telephones and SMS were still functional in many quake-hit areas. We opted to use these still functional and easily available means of communication to facilitate two-way flow of information between the earthquake survivors and relief providers.
How does it work?
To get an idea of how QuakeMap responds on its reports, please read this blog for a walkthrough of a typical QuakeMap report.
To understand how QuakeMap.org operated during the crisis, please read our daily KLL Situation Room updates here.
[QuakeMap volunteers working on reports - bridging the information gap in crisis response]
Over the response period, we were supported by many partners. The Yellow House and Professional Development and Research Center provided us with numbers of volunteers, who became the core of QuakeMap manpower. CloudFactory provided us with resources to host QuakeMap.org. NepalMonitor.org and Himalayan Techies helped us immensely with their prior experiences in Ushahidi deployment.
QuakeMap entered a "Less Active" phase starting from July 13, 2015. The site was officially online till October 2015 and served as an online archive of the needs on the ground as reported by the citizens. View the entire life of Quakemap.org on this visual timeline.
Output and Impact
Nepal Army used over 300 QuakeMap reports marked as 'critical for prioritizing and planning its emergency rescue operations. Reports on QuakeMap.org were instrumental along a continuum of use-cases. Individual reports were picked by groups and organizations and were directly responded to as in this case. On the other hand, aggregation of QuakeMap reports were used by the UN and other organizations to plan their operations and create informative visualizations (view an example here).