bricks self-service data platform · Twin Cities

Brick & Mortar · datasets

Who lives here, and what they pay

Population, income, rent and housing age for one county, as the Census publishes them. The one layer here that describes the people rather than the buildings.

A row here is a whole county. For the same measures around one address, use the census tract file — it resolves to the tract your parcel is in.

The file

2020-2024 ACS 5-year

24 rows

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

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.

measurevaluecountyunit
population1,269,496Hennepin County, Minnesotapeople
rent for a year$17,844Hennepin County, MinnesotaUSD
rent as a share of income29%Hennepin County, Minnesotapercent
housing units571,527Hennepin County, Minnesotaunits
housing built since 201010.9%Hennepin County, Minnesotapercent
median household income$81,568Ramsey County, MinnesotaUSD
rent for a year$15,948Ramsey County, MinnesotaUSD
homes that are rented39.4%Ramsey County, Minnesotapercent
housing units233,870Ramsey County, Minnesotaunits
worked from home15.4% (was 5.1% in 2019)Ramsey County, Minnesotapercent

The cuts of this file

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

2 scopes
CutRowsFile
The Minneapolis side 12 CSV
The St. Paul side 12 CSV

Every column in this file

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

6 columns
ColumnWhat it isIn the default file
measure measure default
shown value default
county county default
unit unit default
value raw value optional
period vintage optional

Where it comes from

U.S. Census Bureau, American Community Survey

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 U.S. Census Bureau. A work of the United States government, which is not subject to copyright protection in the U.S. (17 U.S.C. § 105).

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

Without the page

/api/export?dataset=county-profile&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=county-profile&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.