Land Records Logo

Land Records

Traverse County, MN Parcels & GIS Data

Traverse County, MN parcel data: 6,229 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Traverse County, Minnesota parcel data covering 6,229 property records.

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

Traverse County is a county in the U.S. state of Minnesota. As of the 2020 census, the population was 3,360, making it the least-populous county in Minnesota. Its county seat is Wheaton.

FIPS 27155

Official county website: http://www.co.traverse.mn.us

The FIPS code for Traverse County is 27155.

Explore Traverse County data
Big StoneStevensRobertsGrantWilkinRichlandTraverse
Buy dataset · $120.00One-time downloadSubscribe · $210.001 year of quarterly updates

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%6,229
parcelid100%6,229
parcelid2<0.1%0
ogparcelid100%6,229
ogparcelid2<0.1%0
parentid<0.1%0
stackid<0.1%0
geoid100%6,229
statefp100%6,229
countyfp100%6,229
countyname100%6,229
cousubfp100%6,229
cousubname100%6,229
tractce100%6,229
tractname100%6,229
taxacctnum<0.1%0
taxyear95.5%5,951
taxdistrict<0.1%0
usecode<0.1%0
usedesc<0.1%0
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs39.0%2,431
numunits39.0%2,431
yearbuilt<0.1%0
numfloors<0.1%0
bldgsqft<0.1%0
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue39.0%2,431
landvalue91.4%5,694
agvalue<0.1%0
totalvalue91.4%5,695
taxacres95.5%5,951
calcarea100%6,229
saleamt<0.1%0
saledate<0.1%0
ownertype4.3%266
ownername95.5%5,951
owneraddr95.5%5,951
ownercity<0.1%0
ownerstate<0.1%0
ownerzip<0.1%0
parceladdr97.9%6,096
parcelcity97.9%6,096
parcelstate100%6,229
parcelzip100%6,229
legaldesc95.5%5,951
township<0.1%0
section<0.1%0
qtrsection<0.1%0
range<0.1%0
plssdesc<0.1%0
book<0.1%0
page<0.1%0
block95.5%5,951
lot95.5%5,951
parceltype2.1%131
accesstype2.1%131
iucnclass2.0%125
placename3.9%246
placetype3.9%245
firmid<0.1%0
firmdate<0.1%0
fldzone<0.1%0
zonesubty<0.1%0
staticbfe<0.1%0
elevmin71.5%4,453
elevmax71.5%4,453
elevavg71.5%4,453
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
naicscode0.6%36
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated100%6,229
centroidx100%6,229
centroidy100%6,229
surfpointx100%6,229
surfpointy100%6,229
geom100%6,229
extras100%6,229
ownerlist<0.1%0

Schema mapping

How source columns from the acquired Traverse 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 — Traverse County, Minnesota (27155) 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 95.5% taxyear 100% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 71.5% elevmin 71.5% elevmax 71.5% elevavg supplemented · derived / other pipelines 100% parcelid 100% ogparcelid 91.4% landvalue 91.4% totalvalue 95.5% taxacres 95.5% ownername 95.5% owneraddr 97.9% parceladdr 97.9% parcelcity 100% parcelstate 100% parcelzip 95.5% legaldesc 95.5% block 95.5% lot lrid parcelid ogparcelid geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxyear landvalue totalvalue taxacres calcarea ownername owneraddr parceladdr parcelcity parcelstate parcelzip legaldesc block lot elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras publish.parcel_layer columns not fed by these sources (58) — empty or below 50% fill in this county parcelid2, ogparcelid2, parentid, stackid, taxacctnum, taxdistrict, usecode, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt numfloors, bldgsqft, bedrooms, halfbaths, fullbaths, imprvalue, agvalue, saleamt, saledate, ownertype, ownercity, ownerstate, ownerzip township, section, qtrsection, range, plssdesc, book, page, parceltype, accesstype, iucnclass, placename, placetype, firmid, firmdate, fldzone zonesubty, 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 Traverse County:

Frequently asked questions

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

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

How many parcels are in Traverse County, MN?

The current dataset contains 6,229 parcel records for Traverse County, MN, each with its boundary geometry and assessor attributes.

What is the FIPS code for Traverse County, MN?

The FIPS code for Traverse County, MN is 27155.

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

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

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

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

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated