What is this?

CAPSure lets you find out when and where your next CAPS meeting is, in an effort to get more Chicagoans involved in community policing and make our city safer.

What are CAPS Meetings?

Chicago Alternative Policing Strategy Meetings, or CAPS Meetings, are ongoing sit-down meetings between the Chicago Police Department and Chicago residents.

CAPS meetings are the place to meet the officers that patrol your block, chat about local problems, and work together to fix them. They're held in every one of Chicago's 285 police beats - the local areas that cops work in.

By the late 1980's, Chicago policing had become increasingly isolated from local communities. Former Mayor Richard M. Daley pioneered CAPS meetings in 1993 as an attempt to restore communication between the CPD and local communities. The theory was that chronic neighborhood problems are best address through community problem-solving.

In the wake of last summer's homicide spike, Mayor Rahm Emanuel has been pushing to renew community policing across the city.

Why did you build this?

CAPSure is a demonstration of the power of open data. The Chicago Police Department recently released the ClearPath API, which makes information about Chicago's CAPS meetings available in a machine readable format to anyone.

This data allowed us to make a community meetings calendar app in a couple of days, and we're one small step further to getting more Chicagoans engaged in their local community.

Team and credits

This is an Open City project done as a volunteer effort. We built CAPSure because we think more Chicagoans (including ourselves) should be involved in their local communities.

The team is:

  • Derek Eder - developer and designer
  • Nick Doiron - developer
  • Forest Gregg - advisor
  • Aya O'Connor - advisor


CAPSure was built with calendar and event data from the Chicago Police Department ClearPath API.

The District and Beat boundary data is stored in Google Fusion Tables and are open for anyone to use:


All the code for this site is open source. It was built with Ruby on Rails, Haml, Twiiter Bootstrap, Javascript and Google's Fusion Tables and Maps API. The District and Beat boundary data is stored in Fusion Tables and was pulled from the City of Chicago Data Portal.

Technologies used:

All the code for this project is up on Github.

Contact us

Found a bug? Report it on our issue tracker!

Have a suggestion? Contact us at info@opencityapps.org