What does the Clayton County GA 311 data include?

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

Do I need an account with Clayton County GA 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.

Clayton County GA 311

Public data

Ready to useNo account needed

Public service requests reported through Clayton County, Georgia's 311 system, as the county 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.

26,915service requests as of September 2026
About 74new service requests a week
1 tableone row per service request

What people use it for

Track how long requests take to closeCompare when a request is created and when it closes.
See which requests run past their target timeCompare each request's due date against when it actually closed.
Watch which requests get reopenedSee how often a closed request is reopened later.

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

Vendor documentation: https://services8.arcgis.com/fz3KpsKgK9InMjh8/arcgis/rest/services/SeeClickFix_Requests_%5BPublic%5D_Clayton_County_GA/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` Full snapshot of the current public Clayton County GA 311 request layer, measured at 26,915 rows via ArcGIS returnCountOnly. The layer's view definition restricts to organization_id = 1036 AND private = '0', so only public requests from that organization are exposed; private requests and other organizations are never included. Every run re-reads the whole public collection in 2,000-row pages ordered by OBJECTID and replaces the destination, so current edits are captured and requests that are no longer public are removed on the next full scan. This is a snapshot of the layer as published by Clayton County via SeeClickFix/ArcGIS — it is not a claim of complete request history, and the layer's geographic extent includes outliers beyond the county. Native ArcGIS Date fields (CreationDate, EditDate, created_at, acknowledged_at, closed_at, reopened_at, due_at, sla_expires_at) are carried as raw epoch-millisecond integers; the unit is milliseconds since the Unix epoch (UTC).	beta	full	replace	`OBJECTID`	-