What does the Berkeley CA 311 data include?

One table, service requests, with one row per service request.

Do I need an account with Berkeley CA 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. Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.

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.

Berkeley CA 311

Public data

Ready to useNo account needed

Service requests and inquiries logged with Berkeley, California's 311 line, as the city publishes them. 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 people use it for

See which problems are commonCount requests by type to see what residents report most.
Track how long requests take to closeCompare when each request opens and closes.
Map where requests happenPlot requests using their coordinates to see where they cluster.

What you get

Table	Each row is
Service requests `records`	One service request

Good to know

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 Berkeley CA 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 Berkeley CA 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Berkeley CA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Berkeley CA 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. Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
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 berkeley_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.cityofberkeley.info/d/p88g-6gs2

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Berkeley 311 service requests and inquiries from the published city dataset. Each sync replaces the destination with the current source snapshot; it does not maintain an accumulating archive.	beta	full	replace	`case_id`	-