What does the Honolulu HI 311 data include?

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

Do I need an account with Honolulu HI 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.

Honolulu HI 311

Public data

Ready to useNo account needed

Service requests reported to Honolulu, Hawaii's 311 line over roughly the last 30 days, as the city 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.

What people use it for

Map requests by zip codeSee which zip codes report the most requests.
Watch how many requests come inSee roughly how many requests are made over the last month.

What you get

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

Vendor documentation: https://data.honolulu.gov/Community/HNL-311-Reports/jdy7-ftwe

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Honolulu 311 requests from a rolling 30-day dataset updated daily. Each sync replaces the destination snapshot, removing requests that age out of the source.	beta	full	replace	`id`	-