What does the Renton WA 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 Renton WA 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.

Renton WA 311

Public data

Ready to useNo account needed

Renton 311 requests with creation times, coordinates, and zip codes. 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

Spot demand swingsTrack request dates to see when calls surge or drop.
Find geographic patternsUse coordinates and zip codes to pinpoint neighborhoods with the most calls.
Compare request typesCount by service code to see what work gets requested most.

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 30 days. After that, each run keeps the last 30 days current, re-reading older days after one day. Days older than 30 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 Renton WA 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 Renton WA 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 Renton WA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Renton WA 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 renton_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` Public requests from the selected creation-history period, defaulting to the last 30 completed days. Completed days within the horizon become eligible for refresh after 1 day(s); edits are captured when their creation day is read again. Increase lookback_days to include older creation days. Requests outside the horizon and records removed from the source retain their last synced values. Requests are not filtered by membership in the current service-type catalog. 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` Public service types from the municipal SeeClickFix catalog. Each run reads and merges service codes; previously synced types remain if removed from the source. The catalog does not filter requests.	beta	full	merge	`service_code`	-