bricks self-service data platform · Twin Cities

Brick & Mortar · datasets

What the 911 calls around here are about

The file

Minneapolis only — 87 neighbourhoods inside one city of a seven-county market. 1,646,661 calls from 2020-08-20 to 2026-08-20, aggregated to the neighbourhood because the source publishes no address.

22,123 rows

Counties in this file: Hennepin · 20 columns available · free, no account, no rate limit.

Joins to an address on neighbourhoods, so it can be pointed at one property rather than read whole.

What the rows look like

10 real rows from this file, spread evenly across it rather than taken off the top — every file here is written in some order, so its first rows are never a fair sample of it. These are the default columns, which is what the download button hands over.

neighbourhoodwhat the call was aboutcallsvs city (100 = same)
Downtown WestUnwanted Person10,418186
North LoopF Alarm-Residential-Multi15572
Downtown WestPersonal Inj Acc-Report5677
HaleBurglary Dwlng In Progress25125
Downtown WestAudible Business Alarm11180
East HarrietRobbery Of Biz In Progress5135
Sumner - GlenwoodPerson In Crisis346
BottineauDriving While Intoxicated1325
Lowry Hill EastCode 31150
Windom ParkUnwanted Person1129

An em dash means the record is blank, and that is the source's gap rather than ours. Across the whole file: vs city (100 = same) is blank on 2.9% of rows.

The cuts of this file

Every cut is the same columns, filtered. Pick one and the row count changes; the file does not.

5 scopes
CutRowsFile
every call 22,123 CSV
business alarms only 413 CSV
police responded 13,348 CSV
fire and EMS responded 7,024 CSV
behavioral crisis team 1,751 CSV

Every column in this file

Columns marked default come down unless you pick your own with &columns=.

20 columns
ColumnWhat it isIn the default file
neighbourhood neighbourhood default
subject what the call was about default
calls calls default
vs_city vs city (100 = same) default
pct_of_this_neighbourhood share of this neighbourhood optional
pct_citywide share city-wide optional
pct_of_city_for_this_subject share of the city's calls for this optional
agency who responded optional
dispositioned_false marked false optional
no_disposition no outcome recorded optional
priority_1 at top priority optional
neighbourhood_calls all calls in this neighbourhood optional
first_year first year optional
last_year last year optional
calls_2021 2021 optional
calls_2022 2022 optional
calls_2023 2023 optional
calls_2024 2024 optional
calls_2025 2025 optional
business_alarm is a business alarm optional

Where it comes from

City of Minneapolis, Incidents_Reported_911 — every 911 call from the public that was dispatched, ArcGIS FeatureServer, CC0-1.0

This source does not stamp the day it was published, so we cannot honestly date our copy of it and will not guess. The period the records themselves cover is on the system card.

What this layer cannot answer is stated in full on the system card — read it before quoting a figure.

What you may do with it

Creative Commons Attribution 4.0 International (CC BY 4.0). Share it, change it, build a product on it, sell that product — all fine. The one condition is credit: say it came from Brick & Mortar and link back.

Records published by City of Minneapolis. Government data held by a Minnesota state agency or political subdivision, presumed public under the Minnesota Government Data Practices Act (Minn. Stat. ch. 13) and published by the agency itself.

Read the full licence · how we license every dataset, and the two we do not

Without the page

/api/export?dataset=emergency-calls&format=csv returns the same file. Call /api/export with no arguments for the whole catalogue.

Point an AI at it

Every file carries its own source, its capture date and the layer's own warnings in the header, so a model reading one gets the caveats with the numbers rather than the numbers alone. Paste this at an assistant that can fetch a URL:

Read https://brickandmortar.dev/api/export?dataset=emergency-calls&format=csv
Everything above the header row is provenance and limits. Read it first,
then answer using only what the rows support.

llms.txt describes the whole warehouse the same way — what each dataset holds, which counties it really covers, and what it cannot answer.