Brick & Mortar · datasets

Every sheriff's foreclosure sale in Dakota County

Type an address for the sales around it, or pick the years.

The file

15,062 sheriff's foreclosure sales in Dakota County, 2007 to 2026, dated and priced, 11,748 of them on the parcel their point falls in. Busiest year 2010 (2,147); newest sale 2026-05-28.

15,062 rows

Counties in this file: Dakota · 9 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.

sale dateaddresscitysale amount (winning bid)parcel id
2007-01-023655 SIRETT COURTHastings—191640007090
2008-01-171067 WILLOW TRAILFarmington—143020002300
2008-10-2317391 GLACIER WAYLakeville——
2009-10-063924 155TH ST WRosemount278,788.94345410101050
2010-07-206749 FOLIAGE COURT WESTRosemount153,443.03225135001060
2011-05-0513992 HOLYOKE COURTApple Valley175,733.07016640001030
2012-03-301080 ASTON CIRCLEBurnsville156,457.06028481601060
2013-07-096883 FOLKSTONE RDApple Valley202,956.24—
2016-02-26115 ELM STFarmington3,250,000142583101031
2026-05-283150 MIKE COLLINS DRIVEEagan1,788,186.5102250302051

An em dash means the record is blank, and that is the source's gap rather than ours. Across the whole file: sale amount (winning bid) is blank on 24.4% of rows, parcel id is blank on 22.0% 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.

3 scopes
CutRowsFile
every sale, 2007 on 15,062 CSV
2007 to 2012 11,156 CSV
2020 on 645 CSV

Every column in this file

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

9 columns
ColumnWhat it isIn the default file
sale_date sale date default
address address default
city city default
sale_amount sale amount (winning bid) default
parcel_id parcel id default
crn crn (county record number) optional
year year optional
lat latitude optional
lon longitude optional

Where it comes from

Dakota County Sheriff's Office, via the county's DCGIS_OL_PropertyInformation MapServer (one layer per year)

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 Dakota County Sheriff's Office, Dakota County. 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=dakota-foreclosures&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=dakota-foreclosures&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.