Murray County, MN Parcels & GIS Data

Murray County, MN parcel data: 10,248 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Murray County, Minnesota parcel data covering 10,248 property records.

This page documents parcel-level coverage for Murray 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 Murray County are listed in the attribute-coverage table below. Preview the data in the interactive explorer, or download the complete Murray County property dataset.

Murray County is a county in the U.S. state of Minnesota. The population was 8,179 at the 2020 census. Its county seat is Slayton.

FIPS 27101

Official county website: http://www.murray-countymn.com

The FIPS code for Murray County is 27101.

NoblesCottonwoodRockPipestoneRedwoodLyonMurray

Attribute coverage

Murray County contains 10,248 parcels in the current dataset. Column coverage is the percentage of those parcels for which the attribute is populated (non-NULL).

ColumnCoverageRecords populated
lrid100%10,248
parcelid99.4%10,185
parcelid299.4%10,185
ogparcelid99.4%10,185
ogparcelid299.4%10,185
parentid<0.1%0
stackid<0.1%0
geoid100%10,248
statefp100%10,248
countyfp100%10,248
countyname100%10,248
cousubfp100%10,248
cousubname100%10,248
tractce100%10,248
tractname100%10,248
taxacctnum<0.1%0
taxyear99.4%10,185
taxdistrict97.1%9,948
usecode86.8%8,896
usedesc86.8%8,896
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs54.7%5,609
numunits42.3%4,332
yearbuilt<0.1%0
numfloors42.3%4,332
bldgsqft<0.1%0
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue53.2%5,457
landvalue96.5%9,890
agvalue<0.1%0
totalvalue96.6%9,899
taxacres<0.1%0
calcarea100%10,248
saleamt<0.1%0
saledate<0.1%0
ownertype97.7%10,017
ownername97.7%10,017
owneraddr97.1%9,948
ownercity97.0%9,940
ownerstate97.0%9,940
ownerzip97.0%9,940
parceladdr61.3%6,282
parcelcity38.6%3,959
parcelstate100%10,248
parcelzip100%10,248
legaldesc98.2%10,063
township100%10,245
section100%10,245
qtrsection100%10,245
range100%10,245
plssdesc100%10,245
book<0.1%0
page<0.1%0
block<0.1%0
lot<0.1%2
parceltype3.2%328
accesstype3.2%328
iucnclass3.1%317
placename6.3%647
placetype5.7%583
firmid<0.1%0
firmdate<0.1%0
fldzone<0.1%0
zonesubty<0.1%0
staticbfe<0.1%0
elevmin100%10,247
elevmax100%10,247
elevavg100%10,247
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.6%160
frsid0.7%71
dfrurl0.7%71
caapermit0.7%71
cwapermit0.7%71
rcrapermit0.7%71
updated100%10,248
centroidx100%10,248
centroidy100%10,248
surfpointx100%10,248
surfpointy100%10,248
geom100%10,248
extras<0.1%0
ownerlist97.6%10,003

Schema mapping

How source columns from the acquired Murray 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 — Murray County, Minnesota (27101) 1 entity · most recent acquisition per entity · generated 2026-08-08 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 99.4% taxyear 100% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 100% elevmin 100% elevmax 100% elevavg supplemented · derived / other pipelines 99.4% parcelid 99.4% parcelid2 99.4% ogparcelid 99.4% ogparcelid2 97.1% taxdistrict 86.8% usecode 86.8% usedesc 54.7% numbldgs 53.2% imprvalue 96.5% landvalue 96.6% totalvalue 97.7% ownertype 97.7% ownername 97.1% owneraddr 97.0% ownercity 97.0% ownerstate 97.0% ownerzip 61.3% parceladdr 100% parcelstate 100% parcelzip 98.2% legaldesc 100% township 100% section 100% qtrsection 100% range 100% plssdesc 97.6% ownerlist lrid parcelid parcelid2 ogparcelid ogparcelid2 geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxyear taxdistrict usecode usedesc numbldgs imprvalue landvalue totalvalue calcarea ownertype ownername owneraddr ownercity ownerstate ownerzip parceladdr parcelstate parcelzip legaldesc township section qtrsection range plssdesc elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras ownerlist publish.parcel_layer columns not fed by these sources (45) — empty or below 50% fill in this county parentid, stackid, taxacctnum, zoningcode, zoningdesc, numunits, yearbuilt, numfloors, bldgsqft, bedrooms, halfbaths, fullbaths, agvalue taxacres, saleamt, saledate, parcelcity, book, page, block, lot, parceltype, accesstype, iucnclass, placename, placetype, firmid, firmdate fldzone, zonesubty, staticbfe, fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl caapermit, cwapermit, rcrapermit 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 Murray County:

Frequently asked questions

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

Land Records publishes a Murray 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 Murray County, MN dataset as a GeoPackage or CSV.

How many parcels are in Murray County, MN?

The current dataset contains 10,248 parcel records for Murray County, MN, each with its boundary geometry and assessor attributes.

What is the FIPS code for Murray County, MN?

The FIPS code for Murray County, MN is 27101.

What information does each Murray County, MN parcel record include?

Each Murray 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 Murray County, MN parcel data free?

You can preview Murray 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 Murray County, MN have an official GIS or property records website?

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

On this page