What does the Multnomah County OR 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 Multnomah County OR 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.

Multnomah County OR 311

Public data

Ready to useNo account needed

Public requests from Multnomah County, Oregon and service types the county handles. 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 all requestsSee the full collection to understand what problems residents report.
Monitor updates over timeWatch how requests evolve as the county responds and closes them.

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: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Service types: 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 Multnomah County OR 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 Multnomah County OR 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 Multnomah County OR 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Multnomah County OR 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 multnomahcounty_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` Scans the public requests exposed by the Multnomah County account on each run, without a date filter, using20-row page-number pagination and stopping at a short or empty page. County categories include roads, Mid-County Lighting District, Willamette River Bridges and Code Compliance; this is not all municipal reporting systems or private requests. Subsequent scans capture edits to returned IDs. Merge retains records removed or hidden by the source. Requests are not filtered by current catalog membership, and nullable coordinates and original service names/codes are retained. Full collection completion is subject to runtime limits and must not be inferred from capped certification samples.	beta	full	merge	`service_request_id`	-
`services` Re-fetches the current public service-type catalog exposed by Multnomah County OR SeeClickFix Open311 on each run. The catalog is replaced on each sync, so removed or no-longer-exposed codes disappear from the destination. It is organization-scoped and is not used to filter request rows; existing requests can reference service codes absent from the current catalog.	beta	full	replace	`service_code`	-