Do I need an account with Aurora 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.

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.

Aurora IL 311

Public data

Ready to useNo account needed

Aurora IL 311 data, published as Aurora IL 311 publishes it. 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.

23,248rows as of September 2026
About 21new rows a week
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
featureserver `featureserver`	Complete current contents of the City of Aurora's public OneView service-request point layer (OneView_ServiceRequests_Points_Mapped_view, FeatureServer 0): 23,248 records counted via returnCountOnly on 2026-09-16, read over 24 pages at the layer's 1,000-row transfer cap and ordered by the layer's object-id field OBJECTID1. Each run re-reads the full current view and REPLACES the destination, so the latest statuses and closure dates are always reflected, and requests retired from the view drop out; no retention or history guarantee is claimed beyond what the service currently publishes. DateCreated and DateClosed are ArcGIS native Date fields transmitted as UTC epoch MILLISECONDS and loaded as bigint (divide by 1000 for seconds); no timestamp conversion is applied.

featureserver

featureserver

Complete current contents of the City of Aurora's public OneView service-request point layer (OneView_ServiceRequests_Points_Mapped_view, FeatureServer 0): 23,248 records counted via returnCountOnly on 2026-09-16, read over 24 pages at the layer's 1,000-row transfer cap and ordered by the layer's object-id field OBJECTID1. Each run re-reads the full current view and REPLACES the destination, so the latest statuses and closure dates are always reflected, and requests retired from the view drop out; no retention or history guarantee is claimed beyond what the service currently publishes. DateCreated and DateClosed are ArcGIS native Date fields transmitted as UTC epoch MILLISECONDS and loaded as bigint (divide by 1000 for seconds); no timestamp conversion is applied.

How it works

Choose Aurora 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

Do I need an account with Aurora IL 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Aurora 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.
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 aurorail_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services1.arcgis.com/79UxTxnBeBW8JHY4/arcgis/rest/services/OneView_ServiceRequests_Points_Mapped_view/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` Complete current contents of the City of Aurora's public OneView service-request point layer (OneView_ServiceRequests_Points_Mapped_view, FeatureServer 0): 23,248 records counted via returnCountOnly on 2026-09-16, read over 24 pages at the layer's 1,000-row transfer cap and ordered by the layer's object-id field OBJECTID1. Each run re-reads the full current view and REPLACES the destination, so the latest statuses and closure dates are always reflected, and requests retired from the view drop out; no retention or history guarantee is claimed beyond what the service currently publishes. DateCreated and DateClosed are ArcGIS native Date fields transmitted as UTC epoch MILLISECONDS and loaded as bigint (divide by 1000 for seconds); no timestamp conversion is applied.	beta	full	replace	`OBJECTID1`	-

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, Austin TX 311.

Get Aurora IL 311 data into your warehouse

Last updated 2026-10-16.