Blog
The city data portal: where Chicago publishes its numbers
How to use data.cityofchicago.org, the city's open data site, to find service requests, inspections, FOIA logs and more, and how to read what you download.
Every pothole report, every restaurant inspection and every building permit in Chicago ends up as a row in a table somewhere. Most cities keep those tables locked in the basement. Chicago, since 2010, has put a large share of them on the web, where anybody can search, sort, map and download. The site is the Chicago Data Portal, at data.cityofchicago.org, and it is the closest thing a resident has to the city's own filing cabinet. You do not need an account to browse or download, you do not need anything beyond a browser, and it covers everything from public health to transportation to the city payroll.
Here is how it works and how to find an answer on it, using a question residents ask all the time: how long does the city take to fix a pothole, and how many were reported in my neighborhood?
How it started
The portal's earliest form appeared in May 2010, when the city began posting FOIA request logs, statements of financial interest and other public records on its website, steps that were part of a wider push for transparency in city government. Over the next few years the city built the data site on a commercial open data platform and added data from more departments, and today the portal holds hundreds of datasets about city departments, services, facilities and performance. The platform supports downloads in common formats and an application programming interface, which lets programmers pull data straight into their own tools. Civic technology groups, journalists, researchers and plain curious residents all use it, and the city encourages that.
What is on it
The portal is organized by dataset: each one is a table with a title, a description, a list of columns and a "last updated" date. Some of the kinds of data residents use most:
| Kind of data | What it can answer | A typical dataset title |
|---|---|---|
| Service requests | What residents have reported through 311, and how requests were handled | 311 Service Requests |
| Food inspections | The results of restaurant and food business inspections | Food Inspections |
| Building permits | What has been permitted to be built or renovated | Building Permits |
| Crime and public safety | Reported incidents, by type and by block | Crimes, 2001 to Present |
| Traffic crashes | Where and when crashes happened | Traffic Crashes |
| Licenses | Which businesses hold city licenses | Business Licenses |
| City employees | Job titles and pay for city staff | Current Employee Names, Salaries and Position Titles |
| Boundaries | Maps of wards, community areas and police districts | Boundaries |
| FOIA logs | What public-records requests each department has received | FOIA request logs by department |
Dataset titles change now and then, so use the portal's search box rather than copying a title from a guide.
A walk-through: finding pothole requests
Say you want to know how many potholes were reported on your block and how quickly they got handled. The steps:
- Go to the portal at data.cityofchicago.org and type "311 service requests" into the search box.
- Open the dataset. The page shows the first rows of the table, a description and a link to the "data dictionary" that explains each column.
- Read the description first. It says what the data covers, how often it updates and how the city defines each field. This one step prevents most misreadings.
- Filter. Use the filter controls to limit the table to the request type for potholes, which is usually named something like "Pothole in Street," and to a date range. You can also filter by ward, community area or ZIP code if those columns are in the table.
- Look at the dates. Service request records generally include the date a request was created and the date it was closed. The gap between them is how long the city took.
- Export or chart. Use the export option to download the filtered table as a spreadsheet file, or use the portal's charting and map tools to view it.
An illustration
The numbers here are hypothetical, to show the arithmetic. Say that after filtering you have 1,200 pothole requests for your ward in a year, and that 900 of them show a closed date. The share closed is 900 divided by 1,200, which is 75 percent. If the 900 closed requests took a total of 4,500 days from request to closure, the average is 4,500 divided by 900, or 5 days, though averages can hide long delays, so a spreadsheet user would also look at the longest waits. The real figures for any ward and year are in the portal, and they will differ.
Reading the data carefully
Open data is a record of what was reported and logged, which is not the same as what is happening on the street. A few cautions fit nearly every dataset.
- Reports are not conditions. A 311 dataset shows what residents reported. Neighborhoods differ in how often residents call, so more requests may reflect more reporting, not worse conditions. A block with a lot of requests could be a block whose residents know how to work the system. Using 311 and the CHI311 app explains how requests are filed.
- Locations are sometimes generalized. For privacy, some datasets, such as crime data, show locations at the level of a block and not an exact address.
- Counts depend on definitions. A "closed" request may mean the work was done, or that it was merged with another request. Read the data dictionary.
- Data are updated on a schedule. Some datasets update daily, others monthly or yearly, and the "last updated" line tells you which.
- Records can change. A later update may correct or add to a row. If you are publishing a number, write down the date you downloaded it.
- Names of people are mostly absent, but be careful. Some datasets, such as the employee listing, contain names and pay by design. Others strip personal details. Do not try to re-identify people from data that was anonymized.
A second walk-through: boundaries and joining data
Many questions need two datasets at once. Say you want to compare requests across the city's 77 community areas or its 50 wards. The service request table may list a ward or a community area number, and the portal's boundaries datasets provide the shapes and names that go with those numbers. A mapping tool can then color each area by the number of requests. When you combine tables this way, make sure the geography matches: a table that uses ward numbers is only comparable with another table that uses ward numbers from the same period, because the ward map is redrawn from time to time and a record from an earlier map may fall in a different ward today. The same caution holds for population: raw counts run higher in larger areas, so a fair comparison divides by the number of residents or households, and population figures come from the Census Bureau and not from the portal.
Mapping is a good way to find a question, and careful reading is how you answer it. The portal's own map tool shows where records cluster, and a spreadsheet lets you count them. If a pattern surprises you, check the data dictionary and the department's own explanation before you draw a conclusion.
FOIA logs and financial interest statements
Two of the portal's oldest categories speak to the government's own accountability. The first is a set of logs of public-records requests under the Freedom of Information Act, listed by department. A log shows what has been requested, which can hint at what residents and reporters are curious about. A request you want to make may already have been answered, in which case the earlier response may be public. The second is the statements of financial interest that officials file, which disclose some of their income sources and holdings. Both fall under the portal's transparency purpose. filing a public records request with the city and A public-records request in Chicago, start to finish explain how to file a request for a record that is not already posted, and Public Records and Open Meetings describes the offices involved.
Using the data with other civic tools
The portal pairs naturally with other official sources. A resident following a council debate can use the Clerk's legislation search for the text and the portal for the data behind it. how to follow city news: official sources, meetings and data portals describes the whole set of official sources and a weekly routine for following them. Someone choosing a restaurant can combine the food inspection dataset with the walk-through in Reading a Chicago restaurant inspection report, and Public health in the city: clinics, inspections and West Nile surveillance explains the department that does the inspecting.
Tips for beginners
- Start with the description. A few minutes with the description and the data dictionary saves hours.
- Begin small. Filter to a single month or a single ward before pulling an entire year.
- Use a spreadsheet. A free spreadsheet program can sort, count and chart a filtered download.
- Save your steps. Note which filters you used so that you or someone else can repeat the analysis.
- Ask the department. If a number looks wrong, the department that supplies the data can explain how it is collected, and 311 can route a question.
The portal is no substitute for judgment, but it lets you start with the city's own record and test what you read against it. For a resident who wants to know how the city is really doing, that is the place to begin.