What does the Omaha NE 311 data include?

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

Do I need an account with Omaha NE 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.

Omaha NE 311

Public data

Ready to useNo account needed

Mayor's Hotline requests from Omaha and the surrounding Douglas County area. 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.

651,160service requests as of September 2026
About 1,100new service requests a week
1 tableone row per service request

What people use it for

See all current requestsReview the complete collection to understand current problem distribution.
Spot geographic clustersMap requests by coordinates to find areas needing attention.

What you get

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

Vendor documentation: https://dcgis.org/server/rest/services/Cityworks/Mayors_Hotline_Dashboard_Interactive/MapServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`mapserver` All Mayor's Hotline service-request records exposed by MapServer layer 0 (where=1=1, every attribute, geometry omitted). Published by the Douglas-Omaha GIS Portal, the collection covers the Omaha/Douglas County area and records are not necessarily within Omaha city limits. This is the publisher's current public snapshot: the row count changes between runs (651,160 measured 2026-09-14; close dates of existing records are also edited live) and the publisher may retire rows, so each run reloads the complete currently exposed collection (full + replace) rather than promising full history. No edit watermark is exposed; the oldest record currently observed is dated 2007-03-27, which does not prove earlier or uninterrupted retention. DATETIMEINITFULL and DATETIMECLOSED are ArcGIS native Date values sent as epoch milliseconds and are preserved as bigint (unit: Unix milliseconds); DATETIMEINIT is a date-only value (YYYY-MM-DD). Stamped-record bytes at the measured row count are an estimate of about 0.55 GB (derived from representative pages at offsets 0, mid- and deep-range); the scan sorts by OBJECTID and the final page is partial, so completion is signaled from the response body.	beta	full	replace	`OBJECTID`	-