Every parcel outside the metro, county by county

The file

1,567,765 parcels across the 52 Minnesota counties outside the seven metro counties that publish their parcel file through MnGeo — one file per county, with the county's own use class, value, year built and last sale where the county fills them.

Counties in this file: Aitkin, Becker, Benton, Big Stone, Carlton, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Douglas, Fillmore, Grant, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lake of the Woods, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Red Lake, Renville, Rice, Sherburne, St. Louis, Stearns, Steele, Stevens, Traverse, Wabasha, Waseca, Wilkin, Winona, Wright, Yellow Medicine · 23 columns available · free, no account, no rate limit.

Joins to an address on lat, lon, 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.

An em dash means the record is blank, and that is the source's gap rather than ours. Across the whole file: last sale is blank on 93.6% of rows, year built is blank on 89.9% of rows, address is blank on 43.7% of rows, lot acres is blank on 37.3% of rows, city or township is blank on 35.1% of rows, assessed is blank on 35.0% of rows, use (county's class) is blank on 17.0% of rows, parcel id (county) is blank on 0.8% 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.

Every column in this file

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

Where it comes from

MnGeo Plan Parcels Open (plan_parcels_open, layer 1) — the opted-in counties' own parcel files

Records retrieved 2026-09-10 — the oldest capture date among the layers behind this file, because data is no fresher than its stalest input.

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 Minnesota Geospatial Information Office, county assessors. 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=mn-parcels&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=mn-parcels&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.