Minneapolis MN 311
Public data
Public service requests from Minneapolis for 2026, 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.
- 73,583service requests as of September 2026
- About 2,100new service requests a week
- 1 tableone row per service request
What people use it for
- Review all current casesSee the complete current collection to understand the citywide problem mix.
- Map problem locationsPlot requests by coordinates to find where help is needed most.
What you get
| Table | Each row is |
|---|---|
Service requestsfeatureserver | 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 Minneapolis MN 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 Minneapolis MN 311 data include?
- One table, service requests, with one row per service request.
- Do I need an account with Minneapolis MN 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Minneapolis MN 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 minneapolis_311, version 0.1.0, a REST source, status beta, authentication none.
Vendor documentation: https://services.arcgis.com/afSMGVsC7QlRK1kZ/arcgis/rest/services/Public_311_2026/FeatureServer/0
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
featureserverCurrent snapshot of the full public Minneapolis 311 service-request layer Public_311_2026 published by the City of Minneapolis. Every run reads the complete layer (measured 73,583 records on 2026-09-14) with ordered offset pages and replaces the destination with the returned snapshot, so both removals from the layer and upstream edits to already loaded records are reflected on the next run. The layer's name marks the 2026 calendar-year edition; this connector reads exactly the published layer and makes no claim about other years. Date fields arrive as Unix epoch milliseconds and are preserved raw as bigint. | beta | full | replace | OBJECTID | - |
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 Minneapolis MN 311 data into your warehouse
Last updated .