Next #geowebchat: Crowdsourcing and Ushahidi: beyond the hype, beyond temporary solutions

[Guest hosted by Ana Brandusescu]

This Tuesday, November 20 at 12pm PST/3pm EST/8pm UTC, join the #geowebchat to discuss crowdsourcing! Muki Haklay’s interview in SDI Magazine is a great way to become familiar with the term crowdsourcing as applied to geospatial data. Even though there are several crowdsourcing platforms available, in this chat we will focus primarily on Ushahidi. In 2008, the Ushahidi platform was created to collect citizen reports on the post-election violence incidents in Kenya. Ever since, it has become the ubiquitous platform for crisis mapping, and has been applied to critical events and natural disasters (e.g., the 2010 Haiti earthquake and Hurricane Sandy this year) (Zook et al., 2012).

We will discuss variables such as: technology accessibility, motivation, cause, consistency, adaptability, cost, and uncertainty. Questions include: How has crowdsourcing evolved from crisis mapping? How are participant anonymity and report content managed? Is Ushahidi successful as a platform that connects digital and physical spaces? What are the motivations for participation (e.g., “Let’s talk about our neighborhood; what we like about it; what we’d like to improve in it”)? How do we maintain participation when natural disasters have long term, dire social impacts? How can Crowdmaps avoid ending up in the Dead Ushahidi graveyard?

The #geowebchat is open to everyone, but people who have experience with crowdsourcing and crisis mapping are particularly encouraged to join.

We look forward to chatting with you!

This entry was posted in geowebchat, Mapping, Networks. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

Post a Comment

Your email is never published nor shared. Required fields are marked *


You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>