What does the Knox County TN 311 data include?

2 tables: service requests (one row per service request) and service types (one row per service type).

Do I need an account with Knox County TN 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 row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

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.

Knox County TN 311

Public data

Ready to useNo account needed

Public service requests in Knox County, Tennessee and service types the county accepts. Ingest delivers this data to a data warehouse you own as 2 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

Track issue evolutionMonitor updates to see how issues progress from creation to closure.
Identify what problems matter mostCount requests by type to guide county response priorities.

What you get

Table	Each row is
Service requests `requests`	One service request
Service types `services`	One service type

Good to know

Service requests: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Service types: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.

How it works

Choose Knox County TN 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 Knox County TN 311 data include?: 2 tables: service requests (one row per service request) and service types (one row per service type).
Do I need an account with Knox County TN 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Knox County TN 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 row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
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 knoxcountytn_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://seeclickfix.com/open311/v2/docs

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`requests` Scans the public requests exposed by the Knox County, Tennessee SeeClickFix account on every run, using 20-row page-number pagination without a date filter. This is the provider-exposed collection, not all county reporting channels or private requests. Returned IDs are merged to capture edits on subsequent scans; records removed or hidden by the source remain in the destination. The service catalog includes county categories and Knoxville/Farragut referral categories. Missing coordinates and request codes absent from the current catalog do not filter out requests. Full collection completion remains subject to runtime limits; the bounded author certification sampled only the first five pages.	beta	full	merge	`service_request_id`	-
`services` Reads the current public service-type catalog, returned as a single complete array by Knox County SeeClickFix Open311 (page parameters are ignored; the whole catalog is fetched every run) and merged by service_code. Removed or no-longer-exposed codes retain their last loaded values. The catalog is organization-scoped and is never used to filter request rows.	beta	full	merge	`service_code`	-