Land Records Logo

Land Records

Big Stone County, MN Parcels & GIS Data

Big Stone County, MN parcel data: 8,062 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Big Stone County, Minnesota parcel data covering 8,062 property records.

This page documents parcel-level coverage for Big Stone County, Minnesota. Each parcel record carries its boundary polygon (GIS geometry) along with attributes such as the parcel ID/APN, owner name and mailing address, situs (property) address, assessed land and improvement values, acreage, land-use and zoning codes, year built, and most recent sale price and date. Exact fill rates for Big Stone County are listed in the attribute-coverage table below. Preview the data in the interactive explorer, or download the complete Big Stone County property dataset.

Big Stone County is a county in the U.S. state of Minnesota. As of the 2020 census, the population was 5,166. Its county seat is Ortonville.

FIPS 27011

Official county website: https://bigstonecounty.gov

The FIPS code for Big Stone County is 27011.

Explore Big Stone County data
SwiftGrantLac qui ParleStevensRobertsTraverseBig Stone
Buy dataset · $130.00One-time downloadSubscribe · $230.001 year of quarterly updates

Attribute coverage

Big Stone County contains 8,062 parcels in the current dataset. Column coverage is the percentage of those parcels for which the attribute is populated (non-NULL).

ColumnCoverageRecords populated
lrid100%8,062
parcelid98.2%7,919
parcelid298.2%7,916
ogparcelid98.2%7,919
ogparcelid298.2%7,916
parentid<0.1%2
stackid<0.1%0
geoid100%8,062
statefp100%8,062
countyfp100%8,062
countyname100%8,062
cousubfp100%8,062
cousubname100%8,062
tractce100%8,062
tractname100%8,062
taxacctnum<0.1%0
taxyear98.2%7,916
taxdistrict<0.1%2
usecode13.8%1,110
usedesc13.8%1,110
zoningcode<0.1%2
zoningdesc<0.1%2
numbldgs48.9%3,945
numunits25.9%2,087
yearbuilt<0.1%0
numfloors25.9%2,087
bldgsqft<0.1%0
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue<0.1%0
landvalue<0.1%0
agvalue<0.1%0
totalvalue<0.1%0
taxacres<0.1%2
calcarea100%8,062
saleamt<0.1%0
saledate<0.1%0
ownertype9.8%787
ownername9.8%788
owneraddr<0.1%3
ownercity<0.1%2
ownerstate<0.1%2
ownerzip<0.1%2
parceladdr68.4%5,516
parcelcity64.5%5,204
parcelstate100%8,062
parcelzip100%8,062
legaldesc91.6%7,386
township92.5%7,455
section92.5%7,455
qtrsection<0.1%0
range92.5%7,455
plssdesc92.5%7,455
book<0.1%2
page<0.1%2
block0.1%5
lot0.1%6
parceltype9.7%786
accesstype9.7%786
iucnclass9.1%735
placename12.9%1,043
placetype12.4%998
firmid<0.1%1
firmdate<0.1%1
fldzone<0.1%1
zonesubty<0.1%1
staticbfe<0.1%0
elevmin100%8,061
elevmax100%8,061
elevavg100%8,061
fireplaces<0.1%0
heating<0.1%0
heatfuel<0.1%0
cooling<0.1%0
foundation<0.1%0
roofcover<0.1%0
siding<0.1%0
bldgtype<0.1%0
naicscode1.8%148
frsid0.8%63
dfrurl0.8%63
caapermit0.8%63
cwapermit0.8%63
rcrapermit0.8%63
updated100%8,062
centroidx100%8,062
centroidy100%8,062
surfpointx100%8,062
surfpointy100%8,062
geom100%8,062
extras<0.1%1
ownerlist<0.1%0

Schema mapping

How source columns from the acquired Big Stone County GIS layers map into the harmonized entity schemas and assemble into the published parcel table, alongside supplemented fields (elevation, flood zone) and deterministic columns.

Schema mapping — Big Stone County, Minnesota (27011) 1 entity · most recent acquisition per entity · generated 2026-07-25 direct column transformed (expression) geometry extras json supplemented determined ALL ENTITIES → FINAL PARCEL SCHEMA Harmonized entity columns assemble into publish.parcel_layer — matched by column name. Supplemented fields show their fill rate in this county. SOURCE COLUMNS HARMONIZED ENTITIES PUBLISH.PARCEL_LAYER ADDRESS landmark anumber st_name sub_id1 zip ctu_name postcomm co_name state_code geom 44 cols ⇢ near house_number road unit postcode suburb city state_district state geom extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname 98.2% taxyear 100% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 100% elevmin 100% elevmax 100% elevavg s_fld_haz_ar · FEMA NFHL 0.0% fldzone 0.0% zonesubty 0.0% firmdate 0.0% firmid supplemented · derived / other pipelines 98.2% parcelid 98.2% parcelid2 98.2% ogparcelid 98.2% ogparcelid2 68.4% parceladdr 64.5% parcelcity 100% parcelstate 100% parcelzip 91.6% legaldesc 92.5% township 92.5% section 92.5% range 92.5% plssdesc lrid parcelid parcelid2 ogparcelid ogparcelid2 geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxyear calcarea parceladdr parcelcity parcelstate parcelzip legaldesc township section range plssdesc firmid firmdate fldzone zonesubty elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras publish.parcel_layer columns not fed by these sources (55) — empty or below 50% fill in this county parentid, stackid, taxacctnum, taxdistrict, usecode, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft bedrooms, halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, taxacres, saleamt, saledate, ownertype, ownername, owneraddr ownercity, ownerstate, ownerzip, qtrsection, book, page, block, lot, parceltype, accesstype, iucnclass, placename, placetype, staticbfe fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit ownerlist ADDRESS 10 mapped · 44 kept in extras · 11 unmapped (NULL) SOURCE COLUMNS HARMONIZED → ADDRESS landmark anumber st_name sub_id1 zip ctu_name postcomm co_name state_code geom near house_number road unit postcode suburb city state_district state geom extras · 44 source columns preserved as json add_id, add_id_loc, anumberpre, anumbersuf, st_pre_mod st_pre_dir, st_pre_typ, st_pre_sep, st_pos_typ, st_pos_dir st_pos_mod, sub_type1, sub_type2, sub_id2, zip4, ctu_id_txt co_code, loc_desc, residence, mailable, state_pin, place_loc cen_geo, uni_wo_sub, longitude, latitude, usng_code gis911poc, esn, psap_code, msag_c, verror_911, lst_predir lst_name, lst_type, lst_posdir, status, eff_date, ret_date source, aauthority, edit_org, edit_date, comments extras not present in source — filled with NULL (11) house, category, level, staircase, entrance, po_box, city_district, island, country_region, country, world_region

Neighboring counties

Parcel data for counties bordering Big Stone County:

Frequently asked questions

Where can I find Big Stone County, MN parcel and GIS data?

Land Records publishes a Big Stone County, MN parcel dataset in which every parcel carries its boundary polygon (GIS geometry) along with ownership, assessed value, land use, acreage, and sale history. Preview it in the interactive explorer on this page, or download the full Big Stone County, MN dataset as a GeoPackage or CSV.

How many parcels are in Big Stone County, MN?

The current dataset contains 8,062 parcel records for Big Stone County, MN, each with its boundary geometry and assessor attributes.

What is the FIPS code for Big Stone County, MN?

The FIPS code for Big Stone County, MN is 27011.

What information does each Big Stone County, MN parcel record include?

Each Big Stone County, MN parcel record includes the parcel ID/APN, owner name and mailing address, situs (property) address, assessed land and improvement values, acreage, land-use and zoning codes, year built, and the most recent sale price and date — plus the parcel boundary polygon. Per-attribute fill rates are listed in the coverage table on this page.

Is Big Stone County, MN parcel data free?

You can preview Big Stone County, MN parcels for free in the interactive explorer. The complete dataset is available as a one-time download or through the nationwide parcel web service; see the download options on this page for current pricing.

Does Big Stone County, MN have an official GIS or property records website?

Yes — the official Big Stone County, MN government website is linked in the county details above. Land Records standardizes Big Stone County, MN assessor and recorder records into a single nationwide parcel schema with GIS boundary geometry.

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated