What does the Wayne County MI 311 data include?

2 tables: service requests (one row per service request) and service types (one row per service type).

Do I need an account with Wayne County MI 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 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.

Wayne County MI 311

Public data

Ready to useNo account needed

Wayne County, Michigan publishes requests for roads, parks and public services. Ingest delivers this data to a data warehouse you own as 2 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

Find problem locationsUse coordinates and zip codes to map where requests cluster.
Analyze request typesCount by service code to see which county services get most calls.
Track demand timingMonitor submission dates to find when call volume peaks.

What you get

Table	Each row is
Service requests `service_requests`	One service request
Service types `services`	One service type

Good to know

Service requests: The first run loads the last 90 days. After that, each run keeps the last 90 days current, re-reading older days after 30 days have passed. Days older than 90 days keep the values they had when last read.
Service types: Re-read at most once a day. Service types that change are updated, and types the county removes stay in your table.

How it works

Choose Wayne County MI 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 Wayne County MI 311 data include?: 2 tables: service requests (one row per service request) and service types (one row per service type).
Do I need an account with Wayne County MI 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Wayne County MI 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 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 waynecountymi_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://seeclickfix.com/open311/v2/docs

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`service_requests` Loads the previous 90 completed UTC creation days by default, using the fixed vendor page size of 20 and continuing to an empty page. The current UTC day becomes eligible after it ends. The configurable horizon is bounded, not all history. Completed windows inside the horizon become eligible for refresh 30 days after their last successful read by default, on a subsequent scheduled run. Older creation windows outside the horizon are not routinely refreshed. Merge updates returned IDs and retains deleted, hidden and out-of-horizon previously loaded requests. Codes missing from the current catalog do not filter out requests. Older completed days wait longer between reads, becoming eligible again only after the longer of the refresh interval and a twentieth of their age at their last read (with the default interval, a day read at 1,200 days old waits 60 days).	beta	window	merge	`service_request_id`	lookback_days, staleness_days
`services` Reads the current public service-type catalog for the Wayne County account. It becomes refresh-eligible one day after its last successful read, on a subsequent run. Merge updates returned codes and retains previously loaded codes no longer exposed by the source. Catalog membership never filters request rows.	beta	staleness	merge	`service_code`	-