Hello 311 LabsShare This

Code for America fellows work on a wide variety of projects with their city partners, other organizations, community members, and interested civic hackers. The applications that fellows create range from whimsical to serious, and from simply making a point to potentially making a profit. However, in the nascent arena that combines open and transparent data, cloud infrastructure, and your local government as a platform, we don’t often find ourselves tripping over well standardized approaches for delivering and consuming government data.

One emerging standard that does exist in our field is Open311 – an API for writing and reading civic data directly to and from city systems. Like any evolving standard (i.e. W3C), it has inconsistencies that stem from the various cities and organizations doing their best to implement the core API features, yet inevitably realizing the need to change, modify, and adapt the specification to their own unique requirements.

After spending more than six months in this environment, we realized that what these pioneering organizations and citizens need is a platform to experiment with 311 data and communicate with each other about their work. So, we built 311 Labs.


311 Labs aims to encourage collaboration and experimentation and is debuting with two innovative Open311 applications that start to tie together the work that folks have been doing in this space over the last few years. Specifically, we are showcasing:

  • The Daily Brief: Explore and filter 311 service requests by neighborhood, service name, and status. This site is already running against Open311 endpoints in Baltimore, Md., Boston, Mass., and Bloomington, Ind.

  • Open 311 Status: Monitor Open311 APIs to see if they are down or have performance issues, and view statistics about uptime, comprehensiveness, and citizen utilization. This site currently monitors most of the Open311 endpoints in existence today.

Even though this effort has barely begun, we have already received very positive feedback from city officials. The applications we’ve built and the communication they’ve fostered are helping to shore up inconsistencies in API implementations nationwide. What’s more, because the data has been taken out of its native XML and JSON form and visualized, ideas for building even better applications with it are quickly emerging. There is nothing more important than this – the work we do as fellows is really, in many ways, just scaffolding to support the efforts of future fellows and governments who will build truly amazing products.

It’s worth noting that the City of Chicago and the Smart Chicago Collaborative have done much to encourage this national effort. The vision and support of these Code for America city partners are a keystone in our effort. We look forward to bringing you more news about this project as it evolves and we are excited about the launch of many more innovative civic applications on 311 Labs that focus on 311 data.

Stay tuned to 311 Labs and sign up to work with us as we continue to build the civic web!

  • Deborah Bryant

    I’d like to see you reach out to the City of Detroit, who just closed their call center two weeks ago through budget reductions.  They haven’t released many details, but say they plan on pointing citizens to their web site for information.

    Detroit’s official info
    http://www.detroitmi.gov/News/tabid/3196/ctl/ReadDefault/mid/4561/ArticleId/89/Default.aspx
    industry news
    http://www.govtech.com/e-government/Detroit-Pulls-Plug-on-311-Call-Center.html

  • http://citytracking.org/a-couple-more-months-of-maps-stamen-com/ A Couple More Months of maps.stamen.com | CityTracking

    [...] big organizations and government beginning to use the maps, which is super exciting. Last week, Code for America announced a new initiative called 311 Labs, a platform to experiment with 311 data and communicate with each other about their work. One of [...]

  • http://codeforamerica.org/2012/07/27/hard-data-on-the-status-of-open311/ Hard Data on the Status of Open311 | Code for America

    [...] the recent announcement of 311 Labs and Code for America’s recent podcast featuring me talking about my perspective on Open311, [...]

  • http://codeforamerica.org/2012/10/02/a-civic-stack-thought-experiment/ A Civic Stack Thought Experiment | Code for America

    [...] The idea of a civic stack, or how it relates to our work, began to materialize after a recent conversation with a group of fellows about the importance of being a generalist as we approach projects. It fits the broader narrative that we’re trying to change both minds and methods. It is not to create a self-fulfilling prophecy that skeptical readers might think I’ve set up all along. I can assure you that is not my intention. Unlike the internet layers, we’ve seen changes flow in both directions of this model. For example, Prepared.ly (fire and communications), BlightStatus (property and recordkeeping and communications) and ATX Floods (emergency, operations, communications). Others are anchored in a higher layer and can affect any of the others, such as Textizen, LocalData or the 311 projects. [...]

  • http://www.island94.org/2012/07/hard-data-on-the-status-of-open311/ Hard data on the status of Open311 « Island 94

    [...] the recent announcement of 311 Labs and Code for America's recent podcast featuring me talking about my perspective on Open311, this [...]