What does the Memphis TN 311 data include?

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

Do I need an account with Memphis TN 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.

Memphis TN 311

Public data

Ready to useNo account needed

Service requests from Memphis, Tennessee's 311 system, 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.

402,595service requests as of September 2026
About 3,500new service requests a week
1 tableone row per service request

What people use it for

See all current requestsReview the complete current collection to understand the full problem landscape.
Spot geographic concentrationsPlot requests by coordinates to find neighborhoods with highest demand.

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

Vendor documentation: https://311.memphistn.gov/server/rest/services/311/311_Request_Map_PROD/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` Every service request currently published in the City of Memphis public 311 Requests layer (402,595 records counted via returnCountOnly on 2026-09-14; the layer is live and grows continuously). Each run reads the full layer ordered by the native OBJECTID and replaces the destination table with exactly what that run saw: current statuses (including later closures) and current field values are captured, and records that stop being published disappear from the next load. The city publishes no retention window for this layer, so this connector describes the current published collection and makes no claim of lifetime history. OBJECTID is the layer's native OID, unique within the published snapshot, and is the primary key (INCIDENT_ID is null on the newest rows and is not used). ArcGIS Date fields travel as Unix epoch milliseconds and are preserved as raw bigint values; rows with null date fields are loaded with nulls intact. ArcGIS reports query failures as HTTP 200 with a $.error body; response.error_path treats that as a failure instead of data.	beta	full	replace	`OBJECTID`	-