bricks self-service data platform · Twin Cities

Brick & Mortar · datasets

What businesses around here report to the police

THE LAST YEAR IS SHORT: the feed stops on 2026-08-19, so 2026 is eight months against twelve everywhere else and any fall you see in it is the calendar. It spans the whole file rather than one year deliberately: the median neighbourhood sees 103 of these in ten years, so a per-year index is noise wearing a number.

The file

Minneapolis only — 87 neighbourhoods inside one city of a seven-county market. 18,368 offences against a business, of 226,909 reports filed between 2017-01-01 and 2026-08-19, aggregated to the neighbourhood because the city masks every address to the hundred block before publishing.

2,404 rows

Counties in this file: Hennepin · 12 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.

neighbourhoodoffenceyearreportsvs city (100 = same mix)
ArmatageBurglary Of Business2,0176190
Columbia ParkBurglary Of Business2,0202175
East IslesBurglary Of Business2,0171166
HiawathaBurglary Of Business2,0219106
Logan ParkBurglary Of Business2,01811163
Marcy HolmesShoplifting2,0178111
North LoopShoplifting2,0181344
SewardTheft From Building2,0203114
Ventura VillageBurglary Of Business2,0227144
Windom ParkTrespassed - Burg Buisiness2,0241204

The cuts of this file

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

4 scopes
CutRowsFile
every offence against a business 2,404 CSV
break-ins only 841 CSV
theft and shoplifting 1,142 CSV
robbery of a business 421 CSV

Every column in this file

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

12 columns
ColumnWhat it isIn the default file
neighbourhood neighbourhood default
offence offence default
year year default
reports reports default
vs_city vs city (100 = same mix) default
pct_of_this_neighbourhood share of this neighbourhood optional
reports_citywide reports city-wide that year optional
offence_here_all_years this offence here, all years optional
business_offences_here offences against a business here optional
neighbourhood_reports all reports in this neighbourhood optional
family kind optional
partial_year a part year optional

Where it comes from

Minneapolis Police Department — public incident reports

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=incidents&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=incidents&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.