Land Records Logo

Land Records

Coffee County, TN Parcels & GIS Data

Coffee County, TN parcel data: 32,728 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Coffee County, Tennessee parcel data covering 32,728 property records.

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

Coffee County is a county located in the central part of the state of Tennessee, in the United States. As of the 2020 census, the county's population was 57,889. Its county seat is Manchester. Coffee County is part of the Tullahoma–Manchester, TN Micropolitan Statistical Area.

FIPS 47031

Official county website: http://coffeecountytn.org

The FIPS code for Coffee County is 47031.

Explore Coffee County data
FranklinMooreBedfordCannonRutherfordWarrenGrundyCoffee
Buy dataset · $165.00One-time downloadSubscribe · $290.001 year of quarterly updates

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%32,728
parcelid100%32,728
parcelid21.6%521
ogparcelid100%32,728
ogparcelid21.6%521
parentid<0.1%0
stackid<0.1%0
geoid100%32,728
statefp100%32,728
countyfp100%32,728
countyname100%32,728
cousubfp100%32,728
cousubname100%32,728
tractce100%32,728
tractname100%32,728
taxacctnum<0.1%0
taxyear<0.1%1
taxdistrict<0.1%1
usecode<0.1%1
usedesc<0.1%1
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs100%32,728
numunits<0.1%11
yearbuilt<0.1%0
numfloors<0.1%11
bldgsqft<0.1%0
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue<0.1%0
landvalue<0.1%1
agvalue<0.1%0
totalvalue<0.1%1
taxacres100%32,728
calcarea100%32,728
saleamt<0.1%1
saledate<0.1%1
ownertype99.9%32,700
ownername99.9%32,700
owneraddr<0.1%1
ownercity<0.1%1
ownerstate<0.1%1
ownerzip<0.1%1
parceladdr100%32,728
parcelcity100%32,728
parcelstate100%32,728
parcelzip100%32,728
legaldesc1.1%374
township<0.1%0
section<0.1%0
qtrsection<0.1%0
range<0.1%0
plssdesc<0.1%0
book<0.1%1
page<0.1%1
block<0.1%0
lot100%32,728
parceltype0.3%93
accesstype0.3%93
iucnclass0.1%44
placename4.5%1,483
placetype4.4%1,446
firmid100%32,727
firmdate100%32,727
fldzone100%32,727
zonesubty98.1%32,096
staticbfe<0.1%2
elevmin98.5%32,237
elevmax98.5%32,237
elevavg98.5%32,237
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
naicscode11.2%3,666
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated100%32,728
centroidx100%32,728
centroidy100%32,728
surfpointx100%32,728
surfpointy100%32,728
geom100%32,728
extras100%32,728
ownerlist<0.1%0

Schema mapping

How source columns from the acquired Coffee 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 — Coffee County, Tennessee (47031) 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 PARCEL parcelid calc_acre owner address city lot lastupdate geom 16 cols ⇢ parcelid taxacres ownername parceladdr parcelcity lot updated geom extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname 0.0% taxyear geom · derived from geometry geom dem.us_1m · USGS 1m DEM 98.5% elevmin 98.5% elevmax 98.5% elevavg s_fld_haz_ar · FEMA NFHL 100% fldzone 98.1% zonesubty 0.0% staticbfe 100% firmdate 100% firmid supplemented · derived / other pipelines 100% numbldgs 100% parcelstate 100% parcelzip lrid parcelid ogparcelid geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxyear numbldgs taxacres calcarea ownertype ownername parceladdr parcelcity parcelstate parcelzip lot firmid firmdate fldzone zonesubty staticbfe elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras publish.parcel_layer columns not fed by these sources (56) — empty or below 50% fill in this county parcelid2, ogparcelid2, parentid, stackid, taxacctnum, taxdistrict, usecode, usedesc, zoningcode, zoningdesc, numunits, yearbuilt, numfloors bldgsqft, bedrooms, halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, saleamt, saledate, owneraddr, ownercity, ownerstate ownerzip, legaldesc, township, section, qtrsection, range, plssdesc, book, page, block, parceltype, accesstype, iucnclass, placename, placetype fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit ownerlist PARCEL 8 mapped · 16 kept in extras · 46 unmapped (NULL) SOURCE COLUMNS HARMONIZED → PARCEL parcelid calc_acre owner address city lot lastupdate geom parcelid taxacres ownername parceladdr parcelcity lot updated geom extras · 16 source columns preserved as json gislink, county_id, parcel_type, file_type, conum, cmap, gp parcel, deedac, calcac, owner2, subdiv, shape_starea__ shape_stlength__, objectid_1, full_search_field extras not present in source — filled with NULL (46) parcelid2, taxacctnum, taxyear, usecode, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft, bedrooms halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, saleamt, saledate, owneraddr, ownercity, ownerstate, ownerzip, parcelstate parcelzip, legaldesc, township, section, qtrsection, range, plssdesc, book, page, block, sourceurl, taxdistrict, parentid, fireplaces, heating cooling, foundation, roofcover, siding, heatfuel

Neighboring counties

Parcel data for counties bordering Coffee County:

Frequently asked questions

Where can I find Coffee County, TN parcel and GIS data?

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

How many parcels are in Coffee County, TN?

The current dataset contains 32,728 parcel records for Coffee County, TN, each with its boundary geometry and assessor attributes.

What is the FIPS code for Coffee County, TN?

The FIPS code for Coffee County, TN is 47031.

What information does each Coffee County, TN parcel record include?

Each Coffee County, TN 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 Coffee County, TN parcel data free?

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

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

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated