Charleston County SC 311
Public data
Service requests reported through Charleston County, South Carolina's 311 service, as the county publishes them. 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
- See which request types stand outCount requests by type to see what residents report most.
- Watch how demand shifts over timeTrack how many requests are made, week by week.
- Map where requests are madePlot requests using their coordinates to see where they cluster.
What you get
| Table | Each row is |
|---|---|
Service requestsrequests | One service request |
Request typesservices | One request type the county accepts |
Good to know
- Service requests: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
- Request types: Re-read in full at most once a day. Rows that changed are updated, and rows the source removes stay in your table.
How it works
- Choose Charleston County SC 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 Charleston County SC 311 data include?
- 2 tables: service requests (one row per service request) and request types (one row per request type the county accepts).
- Do I need an account with Charleston County SC 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Charleston County SC 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 charlestoncountysc_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 |
|---|---|---|---|---|---|
requestsRe-fetches the public request collection currently exposed by Charleston County SC SeeClickFix Open311 organization 1233 on each run, using page-number pagination with 20-row pages and no creation-date horizon. This covers provider-exposed public records, not all county reporting channels, private requests or guaranteed lifetime history. Re-reading the collection updates returned request IDs, including older requests still exposed by the provider. Merge retains the last loaded values of records deleted or no longer exposed by the source. | beta | full | merge | service_request_id | - |
servicesReads the current public service-type catalog exposed by the Charleston County SC SeeClickFix Open311 organization (1233). 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. This organization-scoped catalog is not used to filter request rows. | beta | staleness | merge | service_code | - |
Where this lands, and what else connects
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.
- How Ingest reads a REST source
- Ingest for government teams
- The tables Ingest creates
- Every source Ingest connects
Get Charleston County SC 311 data into your warehouse
Last updated .