Crowdsourced Emergency Information

587 views

Published on

How crowdsourced data augments Emergency Management information in general, and in the case of Bushfire Connect in particular

Published in: Health & Medicine, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
587
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • This is challenging to the Emergency Services, who have a strong Command & Control Culture,that deals with verified, trusted & accountable information.A process that is slow by necessity
  • Local experts, small amount of information, but high expertise in that nicheThe crowd -immediate, self organising, and self correcting
  • Web 2.0 is only technologyExpert task (thinking, sensing, resources)Responsiveness,ResilienceNot necessarily free (Mechturk), not only amateurs (linux, galaxy zoo), diverse expert knowledge or resources always needed (local, scientific, …)Note social media
  • These two, complimentary, ecosystems connect through two bridgesagency to community: broadcasting alerts through social mediaAnd the other way around: harvesting information from the crowd
  • It’s a really simple concept:You see somethingYou report it, for instance by SMSIt gets mappedI get an alertThat’s it, simple, but effective
  • Crowdsourced Emergency Information

    1. 1. Crowdsourced Emergency Information<br />Martin TomkoMauritsvan der Vlugt, KerenFlavell, <br />Anthony Joseph, Daniela Fernandez, <br />and many others<br />
    2. 2. Emergency<br />“A serious, unexpected, and dangerous situation requiring immediate action.”<br />Life | Health | Property | Environment<br />
    3. 3. Emergency Lifecycle<br />Preparation<br />Warning<br />Impact<br />Response<br />Recovery<br />
    4. 4. Emergency Information<br />Content:<br />Accountable<br />Timely<br />Accurate<br />Unambiguous<br />Relevant<br />Updateable<br />Delivery:<br />Targeted<br />Accessible<br />Robust<br />
    5. 5. The Expert Approach<br />
    6. 6.
    7. 7. Saturday 7/02/2009 bushfires<br />burnt the equivalent of 1 million football fields, displaced 7,500 people across 78 townships, resulting in 173 dead <br />and 2000 houses lost. <br />
    8. 8. Information Breakdown<br />000 overloaded<br />Slow and overwhelmed response<br />No trustworthy alternative information<br />Misdirected and late evacuations<br />
    9. 9. From VicAlerts RHOK 2011<br />
    10. 10. Authoritative Information Channels<br />Content:<br />Accountable +<br />Timely -<br />Accurate +<br />Unambiguous +<br />Relevant -<br />Updateable -<br />Delivery:<br />Targeted -<br />Accessible -<br />Robust -<br />
    11. 11. Missing Information Stream<br />From people to agencies<br />Supportive information (not incidents, but context)<br />Responsiveness (change happens)<br />Resilience (self-help)<br />Impact reduction vs hazard mitigation<br />
    12. 12. ”<br />There is a need for change […] <br />Empower communities with Timely, Relevant and Tailored information<br />Craig Lapsley, VIC FSC<br />”<br />
    13. 13. Crowdsouring<br />“Crowdsourcing is the act of outsourcing tasks, traditionally performed by an employee or contractor, to an undefined, large group of people or community (a "crowd"), through an open call.”<br />http://en.wikipedia.org/wiki/Crowdsourcing<br />
    14. 14. Crowdsouring<br />Johann Wolfgang Ritter von Kempelen de Pázmánd, cca 1770<br />
    15. 15. Crowdsouring<br />
    16. 16. Crowdsourced Emergency Information<br />
    17. 17. Bridging the Ecosystems<br />
    18. 18.
    19. 19. Stats<br />QLD Flood crisis<br />1 month<br />100,784 reports<br />213021 unique visitors over 2 weeks, 50% over 2 days (11-12th Jan)<br />~500,000 pageviews<br />
    20. 20. Stats<br />Sinsai.info Japan)<br />10K/30K users/day (Avg/Peak)<br />30K/200K requests/day (Avg/Peak)<br />3000 user reports in first week, 7000 in first month<br />
    21. 21. Crowdsourced Information Channels<br />Content:<br />Accountable -<br />Timely +<br />Accurate +/-<br />Unambiguous -<br />Relevant +<br />Updateable +<br />Delivery:<br />Targeted +<br />Accessible +<br />Robust +<br />
    22. 22. Crowdsourced Project Characteristics<br />Short-term Operation <br />Disaster-specific<br />Ad-hoc core team of volounteers<br />Short-term active moderators<br />Information flow and tools established during emergency<br />Platform development in bursts<br />
    23. 23. Crowdsourced Emergency Information<br />
    24. 24. Social Media Data Deluge<br />Starbirdand Stamberger(2010) Tweak the Tweet<br />Example Tweets:<br />#irene [#your primary tag] information for primary tag #locgps coordinates #src where the information came from<br />
    25. 25. Social Media Data Deluge<br />
    26. 26.
    27. 27. Helping neighbours help their neighbours<br />
    28. 28. Characteristics<br />Most projects<br />Short-term Operation <br />Disaster-specific<br />Ad-hoc core team of volounteers<br />Short-term active moderators<br />BushfireConnect.org<br />Ongoing operation<br />National coverage<br />Stable core team + volounteers<br />Long term but latent moderators <br />
    29. 29. Bushfire Connect<br />Community Powered<br />Community Resilience<br />Integrate Crowd Sourced and Official Information<br />
    30. 30. Citizen Reports<br />SMS<br />Web form<br />Emails<br />Twitter<br />Smartphone<br />
    31. 31.
    32. 32. Incident Alerts – OPT IN<br />SMS<br />Email<br />RSS…<br />APP<br />
    33. 33.
    34. 34.
    35. 35. Crowdsourced Emergency Systems Challenges<br />Data Mining and (Geo)Information Retrieval<br />Information synthesis, Mood detection<br />Usability<br />De-centralised dissemination<br />Load balancing<br />Social dynamics and motivation<br />Team organisation<br />Vandalism<br />
    36. 36. http://bushfireconnect.org/feed/<br />www.bushfireconnect.org<br />ushahidi<br />
    37. 37. @bushfireconnect<br />https://www.facebook.com/bushfireconnect<br />
    38. 38. 0429 883 485<br />info@bushfireconnect.org<br />#bushfireconnect<br />ushahidi<br />
    39. 39. Volounteer Coordinator Position<br />Technical Implementation Coordinator<br />System Administrator<br />Moderators<br />
    40. 40. martin.tomko@gmail.com<br />

    ×