What does the Elgin IL 311 data include?

One table, service requests, with one row per service request.

Do I need an account with Elgin IL 311?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

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.

Elgin IL 311

Public data

Ready to useNo account needed

Service requests reported to Elgin, Illinois's 311 line, 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.

6,328service requests as of September 2026
About 490new service requests a week
1 tableone row per service request

What people use it for

See which request types are most commonCount requests by type to see what residents report most.
Track how long requests stay openSee how many days a request takes to close, on average.
See a request's current statusCheck whether a request is open, in progress or done.

What you get

Table	Each row is
Service requests `featureserver`	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 Elgin 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 Elgin IL 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Elgin IL 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Elgin 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 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 elgin_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services5.arcgis.com/tsDpkyNqjjzAB8LP/arcgis/rest/services/Requests_311_View_Layer/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` The City of Elgin's public 311 service-request layer (Requests_311_View_Layer, FeatureServer 0). Reads the complete collection currently exposed by the layer — 6,328 records counted independently on 2026-09-14, served over 4 pages at the service's 2,000-row maximum, ordered by OBJECTID. The full scan re-reads the current view on every run and replaces the destination, so each request's current fields (including closures that occur after creation) mirror exactly what the service serves, and rows absent from a later scan drop out. No retention or history guarantee is claimed beyond what the service currently publishes. createdDate and closedDate are ArcGIS native Date fields transmitted as Unix epoch MILLISECONDS and are preserved as bigint (divide by 1000 for seconds); no timestamp inference is applied. The layer has no general edit timestamp and createdDate does not capture later closures, so the whole window is re-read on every run.	beta	full	replace	`OBJECTID`	-