Tacoma WA 311
Public data
Tacoma WA 311 data, published as Tacoma WA 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.
- 150,525rows as of September 2026
- About 670new rows a week
- 1 tablein your warehouse
What you get
| Table | Each row is |
|---|---|
featureserverfeatureserver | The complete public feature layer SeeClickFix_Requests (FeatureServer layer 0) maintained by the City of Tacoma. Every run reloads the entire current layer and replaces the destination, so the destination mirrors the layer as it exists at run time: later edits to requests (status, assignment, comments) are captured on every sync, and rows removed from the layer disappear on the next run. Measured 2026-09-16 the layer held 150,525 records with created_at spanning 2022-06-17 to 2026-09-01. ArcGIS native Date fields arrive on the wire as Unix epoch milliseconds (esriFieldTypeDate) and are preserved as bigint, not converted. |
How it works
- Choose Tacoma WA 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 Tacoma WA 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Tacoma WA 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 tacoma_311, version 0.1.0, a REST source, status beta, authentication none.
Vendor documentation: https://services3.arcgis.com/SCwJH1pD8WSn5T5y/arcgis/rest/services/SeeClickFix_Requests/FeatureServer/0
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
featureserverThe complete public feature layer SeeClickFix_Requests (FeatureServer layer 0) maintained by the City of Tacoma. Every run reloads the entire current layer and replaces the destination, so the destination mirrors the layer as it exists at run time: later edits to requests (status, assignment, comments) are captured on every sync, and rows removed from the layer disappear on the next run. Measured 2026-09-16 the layer held 150,525 records with created_at spanning 2022-06-17 to 2026-09-01. ArcGIS native Date fields arrive on the wire as Unix epoch milliseconds (esriFieldTypeDate) and are preserved as bigint, not converted. | beta | full | replace | OBJECTID | - |
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 Tacoma WA 311 data into your warehouse
Last updated .