What does the Pinellas County FL 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 Pinellas County FL 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.

Pinellas County FL 311

Public data

Ready to useNo account needed

Pinellas County, Florida publishes service requests with coordinates and service codes. 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

Map request hotspotsPlot coordinates to see which areas of the county report the most.
Track request typesCount requests by code to see what kinds of work come in most.
Measure geographic spreadAnalyze location data to guide where to send crews first.

What you get

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

Good to know

Service requests: The first run loads the last 30 days. After that, each run keeps the last 30 days current, re-reading older days after one day. Days older than 30 days keep the values they had when last read.
Service types: Re-read at most once a day. Service types that change are updated, and types the source removes stay in your table.

How it works

Choose Pinellas County FL 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 Pinellas County FL 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 Pinellas County FL 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Pinellas County FL 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 pinellascounty_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` Loads the previous 30 completed UTC creation days from the public Pinellas County account by default. The current UTC day becomes eligible after it ends. This is a configurable bounded horizon, not full history or all county reporting channels. Each day uses fixed20-row page-number pagination. Completed windows inside the horizon become refresh-eligible one day after their last successful read, on a subsequent run. Edits to requests outside the creation horizon are not routinely captured. Merge updates returned IDs and retains deleted, hidden and out-of-horizon previously loaded requests. Missing catalog codes and nullable coordinates do not filter out requests. Older completed days wait longer between reads, becoming eligible again only after the longer of the refresh interval and a twentieth of their age at their last read (with the default interval, a day read at 40 days old waits 2 days).	beta	window	merge	`service_request_id`	lookback_days, staleness_days
`services` Reads the current public service-type catalog exposed by the Pinellas County SeeClickFix Open311 organization. It becomes eligible for refresh one day after its last successful read on a subsequent scheduled run. Merge updates returned service codes; removed or no-longer-exposed codes retain their last loaded values. The catalog is organization-scoped, is not used to filter or limit request rows, and does not enumerate every municipal service.	beta	staleness	merge	`service_code`	-