Staging copy. The live site is highearthorbit.com.

Nov 7, 2026 · CrisisCommons

You Don't Have to Be in a CrisisDraft

In February 2012, Government Technology named Heather Blanchard, Noel Dickover and me to its Top 25 Doers, Dreamers and Drivers for starting CrisisCommons. I hadn’t reread Miriam Jones’s profile in years. It’s six short paragraphs, and it gets the arc right, but of course it can’t hold what those three years were actually like (or how much of what I’ve worked on since started there).

GovTech has us meeting at Transparency Camp in 2009. My own post from that May says a group of us finally pulled the idea together at Government 2.0 Camp [TK: which camp it was, or both]. Either way, the question was the same one. People who build software and maps want to help when a disaster hits, but there was no obvious place for them to show up, and no one on the response side asking for them. So on June 13 and 14, 2009, about 200 first responders, technologists, government staff and curious citizens spent a weekend at George Washington University talking through what volunteer technologists could do without getting in the way. At the last CrisisCampDC meeting that summer, on a whim I registered crisiscommons.org, installed MediaWiki, and Mikel Maron provided a logo.

For the next nine months it was side projects and good conversations without much of a center. Then on January 12, 2010, the earthquake struck Haiti. By that Thursday we had decided to host a CrisisCampHaiti in DC, and four other cities quickly did the same. Five days after the quake, more than 400 people in five cities were working on 13 projects. The following week there were fourteen more camps, and within fifteen weeks there were 65 camps in ten countries.

The work was concrete. Volunteers built Tradui so responders could translate between Kreyol and English. Thousands traced roads and buildings into OpenStreetMap from 1990s paper maps and then fresh satellite imagery, until Port-au-Prince had a usable damage map where good maps had barely existed. At FortiusOne we loaded maps and data onto USB drives and sent them down for teams working with little or no connectivity. What struck me then, and still does, is that technology multiplies a contribution. Instead of sending $5 by text message, people gave their time and skill, and a dataset or a piece of code shared openly fed every other project that needed it.

The hardest part was never the code. Traditional responders were rightly wary of a crowd of enthusiastic volunteers arriving with untested tools, and they said so. The real job became translation in both directions: helping response organizations say what they needed, and helping volunteers build that instead of whatever was fun to build. That is what GovTech meant by CrisisCommons becoming “a liaison between response organizations and technical volunteers.” With a grant from the Sloan Foundation through the Wilson Center, we spent the next two years trying to make that bridge last.

In January 2012, Heather and Noel stepped down so the organization could grow beyond its founders, which takes its own kind of leadership. I stayed on while serving as CTO of FortiusOne. Ten months later, during Hurricane Sandy, I spent a Saturday in FEMA’s National Response Coordination Center with people from FEMA, the White House and the Red Cross, working out where people in New Jersey and New York could still find gas. Meanwhile CrisisCamps in more than ten cities worked remotely on gas stations, damage reports and getting kids back to school. Three years earlier, traditional responders had worried aloud that volunteers would only add confusion. That weekend, as Di-Ann Eisnor put it, “it was a given that a solution be crowdsourced.”

Noel had the best line in the GovTech piece: CrisisCommons gave people “the idea that you don’t have to be in a crisis to make a difference.” I’ve thought about that a lot since. A disaster shows you, all at once, whether a community’s information is open, current and usable by whoever needs it, and most days those gaps go unnoticed. So the best preparation turned out to be everyday infrastructure: governments publishing authoritative data openly, and neighbors who already know how to use it. That is the work behind ArcGIS Hub, and why I still think of open data as public infrastructure, as basic as roads.

[TK: a person or moment from those years that stays with you, and what you’d tell someone starting a volunteer tech effort today.]

Thank you to Heather, Noel, Mikel, and the thousands of volunteers who showed up, in person and online, when it mattered. If you were one of them, I’d love to hear what you’ve been building since.

CrisisCommons · CrisisCommons · crisis · open data · civic