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

Pittsburgh PA 311

Public data

Ready to useNo account needed

Pittsburgh PA 311 data, published as Pittsburgh PA 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.

What you get

Table Each row is

Table	Each row is
records `records`	Full snapshot of every Pittsburgh 311 service request published by the city (969,681 rows at authoring time; the dataset refreshes daily). Each run re-reads the whole collection in ascending _id order and replaces the destination table, so rows the publisher deletes (the datastore's _id sequence had about 10,000 gaps on 2026-09-16) leave with it; _id is the primary key. _id is the CKAN datastore's own stable row identifier, assigned monotonically as rows are inserted; case_number identifies the city case but is the same business number for the separate (Duplicate) case rows this dataset may contain, so _id is the identity that preserves every row. The whole read is about 31 pages and 680 MB of response bytes, above the 512 MiB default batch bound, and CKAN datastore_search has no range filter to page by time, so max_bytes is set to 1 GiB: under the default every run would stop at the bound and restart from record zero.

records

records

Full snapshot of every Pittsburgh 311 service request published by the city (969,681 rows at authoring time; the dataset refreshes daily). Each run re-reads the whole collection in ascending _id order and replaces the destination table, so rows the publisher deletes (the datastore's _id sequence had about 10,000 gaps on 2026-09-16) leave with it; _id is the primary key. _id is the CKAN datastore's own stable row identifier, assigned monotonically as rows are inserted; case_number identifies the city case but is the same business number for the separate (Duplicate) case rows this dataset may contain, so _id is the identity that preserves every row. The whole read is about 31 pages and 680 MB of response bytes, above the 512 MiB default batch bound, and CKAN datastore_search has no range filter to page by time, so max_bytes is set to 1 GiB: under the default every run would stop at the bound and restart from record zero.

How it works

Choose Pittsburgh PA 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 Pittsburgh PA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Pittsburgh PA 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 pittsburgh_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.wprdc.org/dataset/pittsburgh-311-data/resource/5202679a-d243-402e-b82a-63189995a942

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Full snapshot of every Pittsburgh 311 service request published by the city (969,681 rows at authoring time; the dataset refreshes daily). Each run re-reads the whole collection in ascending _id order and replaces the destination table, so rows the publisher deletes (the datastore's _id sequence had about 10,000 gaps on 2026-09-16) leave with it; _id is the primary key. _id is the CKAN datastore's own stable row identifier, assigned monotonically as rows are inserted; case_number identifies the city case but is the same business number for the separate (Duplicate) case rows this dataset may contain, so _id is the identity that preserves every row. The whole read is about 31 pages and 680 MB of response bytes, above the 512 MiB default batch bound, and CKAN datastore_search has no range filter to page by time, so max_bytes is set to 1 GiB: under the default every run would stop at the bound and restart from record zero.	beta	full	replace	`_id`	-

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, Aurora IL 311.

Get Pittsburgh PA 311 data into your warehouse

Last updated 2026-10-16.