What does the West Des Moines IA 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 West Des Moines IA 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.

West Des Moines IA 311

Public data

Ready to useNo account needed

West Des Moines requests with status, agency assignment, and descriptions. 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

Track agency workloadGroup by agency to see which city department handles the most.
Monitor request statusFilter by status to track open work and recent completions.
Find need hotspotsUse coordinates and zip codes to map where requests cluster.

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 one day. Days older than 90 days keep the values they had when last read.
Service types: Each run re-reads the full list of service types and updates those that changed. Types the city removes stay in your table.

How it works

Choose West Des Moines IA 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 West Des Moines IA 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 West Des Moines IA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can West Des Moines IA 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 westdesmoines_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 public requests in the previous 90 completed UTC creation days by default; the current UTC day becomes eligible after it ends. The configurable horizon is bounded, not all history. Pages return 20 rows and traversal continues until an empty page. Completed creation windows inside the horizon become eligible for refresh one day after their last successful read, on a subsequent run. Requests outside the horizon are not routinely refreshed. Merge updates returned IDs; deleted, hidden and out-of-horizon previously loaded requests retain their last loaded values. 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 40 days old waits 2 days).	beta	window	merge	`service_request_id`	lookback_days
`services` Reads the current public service-type catalog for West Des Moines on every run. Merge updates returned service codes and retains previously loaded codes that disappear from the source. Requests are not filtered by catalog membership; codes absent from this catalog remain on request rows.	beta	full	merge	`service_code`	-