Do I need an account with Burlington VT 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.

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.

Burlington VT 311

Public data

Ready to useNo account needed

Burlington VT 311 data, published as Burlington VT 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.

53,597rows as of September 2026
1 tablein your warehouse

What you get

Table	Each row is
featureserver `featureserver`	All SeeClickFix service requests in the layer (53,597 rows measured 2026-09-16 via returnCountOnly). Full snapshot on every run; the city stopped refreshing the export in April 2026 (layer last edited 2026-04-27, newest request created 2026-04-26). CreatedDate/UpdatedDate/DataImportDate are US-format strings and are delivered as text, not timestamps.

How it works

Choose Burlington VT 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 Burlington VT 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Burlington VT 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 burlingtonvt_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services1.arcgis.com/1bO0c7PxQdsGidPK/arcgis/rest/services/SeeClickFix/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` All SeeClickFix service requests in the layer (53,597 rows measured 2026-09-16 via returnCountOnly). Full snapshot on every run; the city stopped refreshing the export in April 2026 (layer last edited 2026-04-27, newest request created 2026-04-26). CreatedDate/UpdatedDate/DataImportDate are US-format strings and are delivered as text, not timestamps.	beta	full	replace	`RequestId`	-

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.

Get Burlington VT 311 data into your warehouse

Last updated 2026-10-16.