What does the Youngstown OH 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 Youngstown OH 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.

Youngstown OH 311

Public data

Ready to useNo account needed

Youngstown 311 requests with service codes, coordinates, and dates. 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

Count request typesTally by service code to understand what problems need attention.
Map problem areasPlot coordinates to find where the most requests come from.
Track request flowMonitor dates to see when calls arrive and spot busy periods.

What you get

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

Good to know

Service requests: Each run re-reads all published requests and updates those that changed. Requests removed from the source stay in your table.
Service types: Each run re-reads the full list of service types and updates those that changed. Types the city removes stay in your table.

How it works

Choose Youngstown OH 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 Youngstown OH 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 Youngstown OH 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Youngstown OH 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 youngstown_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
`service_requests` Re-fetches the currently exposed public request collection on each run using page-number pagination, with no creation-date horizon. This is a full-read plan for the provider collection, not a guarantee of lifetime municipal history. Returned request IDs are updated by merge; deleted or no-longer-exposed requests retain their last loaded values.	beta	full	merge	`service_request_id`	-
`services` Reads the current public service-type catalog exposed by this organization on each run. All returned service codes are retained; the catalog is not used to filter request rows. Merge updates returned codes, while removed or no-longer-exposed codes retain their last loaded values.	beta	full	merge	`service_code`	-