What does the Sacramento CA 311 data include?

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

Do I need an account with Sacramento CA 311?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

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.

Sacramento CA 311

Public data

Ready to useNo account needed

Sacramento 311 requests with creation and update dates, covering recent years. 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.5 millionservice requests as of September 2026
About 12,000new service requests a week
1 tableone row per service request

What people use it for

Track request additionsMonitor when requests arrive to understand when problems are reported.
Spot recent changesUse update dates to see which requests received attention recently.
Understand scaleUse record counts to gauge the scope of 311 work across the city.

What you get

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

Good to know

Each run replaces the table with the currently published requests, so status changes and closures show up on the next run. Requests removed from the public layer disappear on the next run.

How it works

Choose Sacramento 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 Sacramento CA 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Sacramento CA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Sacramento 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 the currently published requests, so status changes and closures show up on the next run. Requests removed from the public layer disappear on 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 sacramento_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services5.arcgis.com/54falWtcpty3V47Z/arcgis/rest/services/SalesForce311_View/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` Full snapshot of the layer currently published in the SalesForce311_View service, which the official ArcGIS Hub item "Sacramento 311 Calls View (Current)" links to this exact SalesForce311_View endpoint; the layer's own description string is "SalesForce311_Dev". The publisher describes the item as updated in real time, holding records last updated on or after 2023-01-01; a live full capture shows DateCreated as early as 2020-07-26 and DateUpdated as early as 2024-01-01, so pre-2023 creation dates can exist and no complete call history is warranted. Measured at 1,538,243 rows via ArcGIS returnCountOnly on 2026-09-14; a full run re-reads the whole published view in 2,000-row resultOffset/resultRecordCount pages ordered by OBJECTID and replaces the destination. That fits the 1,600,000-row resultOffset depth cap and the 1,000-page ceiling only (at most 770 data pages); an estimate from sampled all-attribute records puts the raw volume near 0.68 GB, which is an estimate, not a certified bound, and the scan stops bounded if the source ever grows past the depth cap. Each run captures current edits; records dropped from the public view are absent on the next snapshot and no deletion or rolloff cause is assigned. Native ArcGIS Date fields (DateCreated, DateUpdated, DateClosed) arrive as epoch-millisecond integers since 1970-01-01 UTC and are preserved as raw bigint.	beta	full	replace	`OBJECTID`	-