Recently we began conducting research into the use of our various products around the world, assessing impact and use, apparent successes, perceived and critical failures, as well as qualitative and quantitative evaluations of the data collected from each platform. What’s perhaps, different about this particular document is that it also looks at non-crisis deployments like Vacant NYC.
We’re trying to come up with other ways of visualizing Ushahidi data. Using the Ushahidi API, Emmanuel whipped up a heatmap of the Japan deployment (http://sinsai.info/ushahidi).
Welcome to the ICTworks bi-weekly ICT4D Retrospective, where we condense the last two weeks of news into a succinct list of links for your perusal. If you want your news to be featured, email them to ritse [at] ritseonline [dot] com. To get these links faster, follow me on Twitter: @RitseOnline
The iHub is Ushahidi’s base in East Africa. It’s an open co-working and community space that we built out last year, and that we share with the rest of Nairobi’s vibrant tech community. It’ one year old now, and we’re having a little celebration to appreciate the community who makes it all happen.
It goes without saying that we rely upon location pretty heavily here at Ushahidi. SwiftRiver’s mandate is to help users process and validate data. For Ushahidi users, applying geospatial context to content that doesn’t carry it (like SMS, news articles, blog posts, in some cases Tweets) has proved tedious, with questionable results.
Ushahidi was born as a group of ad hoc Kenyans who came together to build a tool for crowdsourcing information 3 years ago. The organization was formed a few months later, so both are almost 3 years old.
SMSsync v1.0.3
