What does the Los Angeles CA 311 data include?

One table, service cases, with one row per service case.

Do I need an account with Los Angeles 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 adds records created since the last run. A record changed later, for example when it is closed, keeps the values it had when first loaded.

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.

Los Angeles CA 311

Public data

Ready to useNo account needed

Service requests from Los Angeles's MyLA311 system from 2026, 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.

1.7 millionservice cases as of September 2026
About 47,000new service cases a week
1 tableone row per service case

What people use it for

See what problems appearTrack new requests as they arrive to respond to emerging issues.
Map problems by areaPlot requests from coordinates to see which neighborhoods report the most.

What you get

Table	Each row is
Service cases `records`	One service case

Good to know

Each run adds records created since the last run. A record changed later, for example when it is closed, keeps the values it had when first loaded.

How it works

Choose Los Angeles 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 Los Angeles CA 311 data include?: One table, service cases, with one row per service case.
Do I need an account with Los Angeles CA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Los Angeles 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 adds records created since the last run. A record changed later, for example when it is closed, keeps the values it had when first loaded.
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 lacity_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.lacity.org/City-Infrastructure-Service-Requests/MyLA311-Cases-2026/2cy6-i7zn

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` MyLA311 case records from the 2026 dataset. Incremental sync follows creation time; later edits to previously loaded cases are not refreshed. Other years are not included.	beta	watermark	merge	`casenumber`	backfill_days