So you’ve got a great idea for a user-contributed map you need to launch RIGHT NOW. Ushahidi’s Crowdmap makes it pretty easy, and hopefully this post makes it even easier. All examples shown are from TBD’s Crowdmap for D.C.’s election.
Also, check and see if anyone else has done your map idea with a Google Search. If someone else has already built a map of what you want to do in the same area, maybe you should just help them out instead of replicating the work.
2. On the deployment setup page, pick a url, name and tagline for your map. Keep SEO in mind here to make it easier to find. (You can edit this later, so don’t sweat it too much). Click Finish.
3. Click on admin dashboard for your map or go to http://yourmapname.crowdmap.com/admin
This is your map’s Dashboard. Bookmark it. Your map is now live and activated. If you need to launch it right now, you can – though there’s further additions and customizations you can do. Note: With the default settings, people will only be able to submit reports on the site.
Every election since I started my professional career has led the news organization I was working for at the time to say, “We really should have a map of election problems.” Then we’d build some UGC map held together by virtual duct tape. Sound familiar?
User-populated maps have come a long way in the past few years thanks to lots of free technology available on the web. Google Maps, for instance, was a early precursor that still has a lot of utility today. See my [very impressive] map for free donuts as a good (and yes, silly) example of a quick Google collaborative map.
In 2008, Ushahidi (which is Swahili for “testimony” – the more you know) made its debut in mapping post-eletion violence in Kenya . The mapping tool allowed for user to add reports to the map using SMS, email and on-site forms. They’ve since added support for reports via Twitter hashtag.
While they’ve had great success in mapping international crises (like the Haiti Rescue Efforts) and domestic trends (like the Atlanta Crime Map), the main problem with Ushahidi is that it isn’t altogether quick or easy to get a map set up. The software is free and open source, but you need to have a server and programming know-how to get it going.
Thankfully, Ushahidi recently launched a stripped-down, hosted version of it’s mapping tool called Crowdmap. In about 10 minutes, you can have a user-contributed map up and running with no programming know-how and no server.
WMATA Problem Map
Reports submitted on-site flow in to a back-end queue that’s easy to publish as verified or unverified reports. Messages sent via email or Twitter can be converted to full map reports by an admin in a matter of a couple of minutes. All reports have an option to add photos, videos or news links to more info. You can schedule reports to publish and certain times, plus designate specific submitters (like your staff) to have their reports be auto-approved.
Crowdmap does have a couple of downsides. For one, it isn’t embeddable on your site. It has to be used on Crowdmap, though you can use a Google analytics tracking code to track traffic. It also isn’t particularly customizable, so you can’t brand it or add significant new features as you can with Ushahidi. Still, though, it’s a heckuva lot better than some of the cobbled-together maps I’ve had to put together before.
I recently built a couple of these maps for TBD.com, one for mapping Washington-area transit issues and another for monitoring polling problems on the day of D.C.’s primary elections. Neither took much time to set up and both had/have decent participation, given that we promote it on our site. We got far more Twitter reports than anything else, which is likely because we put the most effort into promoting it there. At some point, I’d like to expand our reports to include SMS contributions.
I’ll have a post soon that will walk though setting up a Crowdmap, but for now, check out the site and tinker around. It’s super easy.
How many news organizations can identify with today’s Dilbert strip? In recent years, we’ve seen a lot of corporate media companies that want to reap the benefits of social media without allowing employees to appropriately use the tools. Funny, but all to close to home for some. (Strip is after jump due to stupid blog formatting)
It was my first real breaking news situation since starting at TBD – and the first I’ve ever experienced in a TV newsroom. Within minutes of hearing from a TV reporter’s wife (who works at the Discovery site) about the situation, we had a helicopter and live reporting on-scene. You don’t get helicopters at the Cincinnati Enquirer, so that was pretty mind-blowing.
Within minutes we were getting in photos and eyewitnessreports from Twitter. We were streaming video online before anyone else – heck, it was even used on other news sites in our area. As things were confirmed, I was able to tweet them out ASAP. I had a lot of back-and-forth communication going on with our staff, some of our blogger partners on-scene and other eyewitnesses on Twitter (a few we even got to talk live on-air). In short, it was an amazing time to be behind the Tweetdeck.
@TBD is having their CNN/Gulf War moment right now. They’re dominating coverage right now. Kudos.
All that praise and warm fuzzies aside – it proved once again that monitoring and using Twitter in breaking news is increasingly important for any news operation. Twitter “broke the story”, we all know that – and for better or worse it owned the coverage in a lot of ways. We in the news media can only engage the best and stream the rest when something like this happens in such rapid-fire succession. It was a day of lessons for us and every media outlet, I’m sure.