What does the Bellevue WA 311 data include?

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

Do I need an account with Bellevue WA 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.

Bellevue WA 311

Public data

Ready to useNo account needed

Service requests reported to Bellevue, Washington's 311 line over the last five years, 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.

34,305service requests as of September 2026
About 220new service requests a week
1 tableone row per service request

What people use it for

See which problems are growingCount requests by type, week by week, to spot what is rising.
Track how requests change over timeSee when a request was created and last updated.
Map where requests happenPlot requests using their coordinates to see where they cluster.

What you get

Table	Each row is
Service requests `featureserver`	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 Bellevue 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

What does the Bellevue WA 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Bellevue WA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Bellevue 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. 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 bellevue_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services1.arcgis.com/EYzEZbDhXZjURPbP/arcgis/rest/services/MyBellevue_311/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` The complete public service-request collection currently exposed by the MyBellevue_311 feature layer. The source is a rolling five-year view: its definition query returns only rows whose EditDate falls within the last 1825 days. Every run reloads the entire current view and replaces the destination, so rows that age out of the source window disappear on the next run — that mirror is the source's actual retention, and no full-history claim is made — while later status or comment edits to current rows are captured on every run. Measured on 2026-09-13 the view held 34,305 rows (~21 MB), a complete snapshot for one run. DateCreated and EditDate are ArcGIS native Date fields: on the wire they are Unix epoch milliseconds and are preserved as bigint.	beta	full	replace	`OBJECTID`	-