Chicago IL 311
Public data
Service requests made to Chicago's 311 line, as the City of Chicago publishes them, showing when each was made and where. Ingest delivers this data to a data warehouse you own as one table, and updates it on the schedule you choose. There is no code to write and nothing to install.
- 14.6 millionservice requests as of September 2026
- About 46,000new service requests a week
- 1 tableone row per service request
What people use it for
- See how demand changes over timeCount requests by the day they were made to spot weekly and seasonal patterns.
- Map where requests are concentratedPlot requests using their coordinates to see which areas report the most.
What you get
| Table | Each row is |
|---|---|
Service requestsrecords | One service request |
Good to know
Each run adds requests created since the last run. A request changed later, for example when it is closed, keeps the values it had when first loaded.
How it works
- Choose Chicago IL 311. The data is public, so there is nothing to sign in to.
- Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
- Pick a schedule. Daily is the default, and weekly and monthly are there too.
- Ingest runs it from then on. If a run fails, your dashboard shows which table and why.
Questions
- What does the Chicago IL 311 data include?
- One table, service requests, with one row per service request.
- Do I need an account with Chicago IL 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Chicago IL 311 data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- How fresh is the data?
- As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan. Each run adds requests created since the last run. A request changed later, for example when it is closed, keeps the values it had when first loaded.
- Will running it again create duplicate rows?
- No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference
Connector cityofchicago_311, version 0.1.0, a REST source, status stable, authentication none.
Vendor documentation: https://data.cityofchicago.org/resource/v6vf-nfxy.json
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
recordsChicago 311 service requests (sr_number primary key). | stable | watermark | merge | sr_number | backfill_days |
Where this lands, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.
- How Ingest reads a REST source
- Ingest for government teams
- The tables Ingest creates
- Every source Ingest connects
Get Chicago IL 311 data into your warehouse
Last updated .