Kalkaska County, MI Parcels & GIS Data

Kalkaska County, MI parcel data: 20,474 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Kalkaska County, Michigan parcel data covering 20,474 property records.

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

Kalkaska County is located in the U.S. state of Michigan. As of the 2020 census, its population was 17,939. The county seat is Kalkaska.

FIPS 26079

Official county website: http://www.kalkaskacounty.net

The FIPS code for Kalkaska County is 26079.

RoscommonCrawfordGrand TraverseWexfordMissaukeeAntrimOtsegoKalkaska
Hosted Web API$200/mo

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%20,474
parcelid100%20,474
parcelid298.3%20,119
ogparcelid100%20,474
ogparcelid298.2%20,106
parentid<0.1%0
stackid<0.1%0
geoid100%20,474
statefp100%20,474
countyfp100%20,474
countyname100%20,474
cousubfp100%20,474
cousubname100%20,474
tractce100%20,474
tractname100%20,474
taxacctnum<0.1%0
taxyear100%20,474
taxdistrict98.2%20,101
usecode98.2%20,101
usedesc0.2%31
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs0.9%177
numunits0.8%156
yearbuilt<0.1%0
numfloors<0.1%0
bldgsqft<0.1%0
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue93.6%19,172
landvalue93.6%19,172
agvalue93.6%19,172
totalvalue98.2%20,101
taxacres<0.1%0
calcarea100%20,474
saleamt98.2%20,101
saledate27.1%5,546
ownertype100%20,470
ownername100%20,470
owneraddr99.3%20,335
ownercity100%20,467
ownerstate100%20,467
ownerzip100%20,467
parceladdr99.7%20,409
parcelcity<0.1%1
parcelstate100%20,474
parcelzip99.6%20,386
legaldesc98.2%20,099
township100%20,471
section100%20,471
qtrsection100%20,471
range100%20,471
plssdesc100%20,471
book<0.1%0
page<0.1%0
block<0.1%0
lot<0.1%0
parceltype0.4%83
accesstype2.2%445
iucnclass0.3%61
placename28.6%5,849
placetype4.4%892
firmid<0.1%4
firmdate<0.1%4
fldzone<0.1%4
zonesubty<0.1%4
staticbfe<0.1%0
elevmin97.2%19,904
elevmax97.2%19,904
elevavg97.2%19,904
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
naicscode34.5%7,067
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated98.3%20,119
centroidx100%20,474
centroidy100%20,474
surfpointx100%20,474
surfpointy100%20,474
geom100%20,474
extras100%20,474
ownerlist82.6%16,910
placefp25.2%5,162
zoningurl<0.1%0

Schema mapping

How source columns from the acquired Kalkaska 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 — Kalkaska County, Michigan (26079) 1 entity · most recent acquisition per entity · generated 2026-08-30 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 PARCEL pid owner owneraddre ownercity ownerstate ownerzip propaddres twnunit geom 2 cols ⇢ parcelid ownername owneraddr ownercity ownerstate ownerzip parceladdr township geom extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname 100% taxyear 98.3% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 97.2% elevmin 97.2% elevmax 97.2% elevavg s_fld_haz_ar · FEMA NFHL 0.0% fldzone 0.0% zonesubty 0.0% firmdate 0.0% firmid supplemented · derived / other pipelines 98.3% parcelid2 98.2% ogparcelid2 98.2% taxdistrict 98.2% usecode 93.6% imprvalue 93.6% landvalue 93.6% agvalue 98.2% totalvalue 98.2% saleamt 100% parcelstate 100% parcelzip 98.2% legaldesc 100% section 100% qtrsection 100% range 100% plssdesc 82.6% ownerlist lrid parcelid parcelid2 ogparcelid ogparcelid2 geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxyear taxdistrict usecode imprvalue landvalue agvalue totalvalue calcarea saleamt ownertype ownername owneraddr ownercity ownerstate ownerzip parceladdr parcelstate parcelzip legaldesc township section qtrsection range plssdesc firmid firmdate fldzone zonesubty elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras ownerlist publish.parcel_layer columns not fed by these sources (43) — empty or below 50% fill in this county parentid, stackid, taxacctnum, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft, bedrooms, halfbaths fullbaths, taxacres, saledate, parcelcity, book, page, block, lot, parceltype, accesstype, iucnclass, placename, placetype, staticbfe fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit placefp, zoningurl PARCEL 9 mapped · 2 kept in extras · 45 unmapped (NULL) SOURCE COLUMNS HARMONIZED → PARCEL pid owner owneraddre ownercity ownerstate ownerzip propaddres twnunit geom parcelid ownername owneraddr ownercity ownerstate ownerzip parceladdr township geom extras · 2 source columns preserved as json subname, globalid extras not present in source — filled with NULL (45) parcelid2, taxacctnum, taxyear, usecode, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft, bedrooms halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, taxacres, saleamt, saledate, parcelcity, parcelstate, parcelzip, legaldesc section, qtrsection, range, plssdesc, book, page, block, lot, updated, sourceurl, taxdistrict, parentid, heatfuel, fireplaces, heating, cooling foundation, roofcover, siding

Neighboring counties

Parcel data for counties bordering Kalkaska County:

Frequently asked questions

Where can I find Kalkaska County, MI parcel and GIS data?

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

How many parcels are in Kalkaska County, MI?

The current dataset contains 20,474 parcel records for Kalkaska County, MI, each with its boundary geometry and assessor attributes.

What is the FIPS code for Kalkaska County, MI?

The FIPS code for Kalkaska County, MI is 26079.

What information does each Kalkaska County, MI parcel record include?

Each Kalkaska County, MI 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 Kalkaska County, MI parcel data free?

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

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

On this page