Columbus OH 311
Public data
Service requests reported to Columbus, Ohio's 311 line in roughly the last 30 days, as the city publishes them. 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.
- 33,336service requests as of September 2026
- About 7,800new service requests a week
- 1 tableone row per service request
What people use it for
- See how requests change statusTrack when a request's status last changed.
- Watch request volume over timeSee how many requests come in from week to week.
What you get
| Table | Each row is |
|---|---|
Service requestsmapserver | One service request |
Good to know
Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
How it works
- Choose Columbus OH 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 Columbus OH 311 data include?
- One table, service requests, with one row per service request.
- Do I need an account with Columbus OH 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Columbus OH 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 replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
- Will running it again create duplicate rows?
- No. Each run replaces the table, so it never holds two copies of the same row.
- 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 columbus_311, version 0.1.0, a REST source, status beta, authentication none.
Vendor documentation: https://maps2.columbus.gov/arcgis/rest/services/Applications/ServiceRequests/MapServer/0
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
mapserverAll public Columbus 311 service requests in the ArcGIS layer "All Service Requests - Last 30 Days". The layer is a rolling 30-day window (33,336 records at authoring time): rows age out of the source, so each full refresh re-fetches the current window and is not a claim of complete history. Date fields (REPORTED_DATE, STATUS_DATE, REQUEST_MODIFIED) are returned as ArcGIS epoch milliseconds and are preserved as bigint with that unit; they are not Unix seconds and must not be cast to timestamp. CASE_ID is not unique in the source (224 duplicate CASE_IDs in a 10,000-record sample); DATAHUB_ID is unique across all 10,000 probed records and identifies each service request. | beta | full | replace | DATAHUB_ID | - |
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 Columbus OH 311 data into your warehouse
Last updated .