San Mateo County CA 311
Public data
Illegal dumping, cart and graffiti reports made to San Mateo County, California, with response times and status. 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
- Measure response speedUse minutes-to-acknowledge data to see how quickly the county reacts.
- Track completion timeCompare minutes-to-closed to understand how long work takes.
- Analyze report typesCount by type to see which problems need the most cleanup work.
What you get
| Table | Each row is |
|---|---|
Reportsrecords | One report |
Good to know
Each run replaces the table with all current reports, preserving repeated complaint IDs as separate records.
How it works
- Choose San Mateo County 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 San Mateo County CA 311 data include?
- One table, reports, with one row per report.
- Do I need an account with San Mateo County CA 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can San Mateo County 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 all current reports, preserving repeated complaint IDs as separate records.
- 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 sanmateocounty_311, version 0.1.0, a REST source, status beta, authentication none.
Vendor documentation: https://datahub.smcgov.org/d/4u6x-x6rk
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
recordsReport It! SMC illegal dumping and related reports, including shopping carts and graffiti. Each sync replaces the destination with all published source rows, preserving repeated business report IDs as separate records using Socrata row IDs. | beta | full | replace | socrata_row_id | - |
Where this lands, and what else connects
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.
- How Ingest reads a REST source
- Ingest for government teams
- The tables Ingest creates
- Every source Ingest connects
Get San Mateo County CA 311 data into your warehouse
Last updated .