Land Records Logo

Land Records

Moore County, TN Parcels & GIS Data

Moore County, TN parcel data: 4,272 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Moore County, Tennessee parcel data covering 4,272 property records.

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

Moore County is a county located in the south central part of the U.S. state of Tennessee. As of the 2020 census, the population was 6,461, making it the third-least populous county in Tennessee. It forms a consolidated city-county government with its county seat of Lynchburg.

FIPS 47127

Official county website: https://metromoorecounty.org/

The FIPS code for Moore County is 47127.

Explore Moore County data
FranklinCoffeeLincolnBedfordMoore
Buy dataset · $110.00One-time downloadSubscribe · $195.001 year of quarterly updates

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%4,272
parcelid100%4,272
parcelid298.8%4,221
ogparcelid100%4,272
ogparcelid298.8%4,221
parentid<0.1%0
stackid<0.1%0
geoid100%4,272
statefp100%4,272
countyfp100%4,272
countyname100%4,272
cousubfp100%4,272
cousubname100%4,272
tractce100%4,272
tractname100%4,272
taxacctnum<0.1%0
taxyear<0.1%0
taxdistrict<0.1%0
usecode<0.1%0
usedesc<0.1%0
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs99.8%4,262
numunits<0.1%2
yearbuilt<0.1%0
numfloors<0.1%2
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
taxacres100%4,272
calcarea100%4,272
saleamt<0.1%0
saledate<0.1%0
ownertype99.9%4,269
ownername99.9%4,269
owneraddr<0.1%0
ownercity<0.1%0
ownerstate<0.1%0
ownerzip<0.1%0
parceladdr100%4,272
parcelcity100%4,272
parcelstate100%4,272
parcelzip100%4,272
legaldesc20.3%866
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
block<0.1%0
lot100%4,272
parceltype9.1%388
accesstype9.1%388
iucnclass9.0%386
placename12.7%542
placetype12.5%536
firmid100%4,271
firmdate100%4,271
fldzone100%4,271
zonesubty97.9%4,181
staticbfe<0.1%0
elevmin95.4%4,077
elevmax95.4%4,077
elevavg95.4%4,077
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
naicscode15.3%654
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated100%4,272
centroidx100%4,272
centroidy100%4,272
surfpointx100%4,272
surfpointy100%4,272
geom100%4,272
extras100%4,272
ownerlist<0.1%0

Schema mapping

How source columns from the acquired Moore 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 — Moore County, Tennessee (47127) 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 geom · derived from geometry geom dem.us_1m · USGS 1m DEM 95.4% elevmin 95.4% elevmax 95.4% elevavg s_fld_haz_ar · FEMA NFHL 100% fldzone 97.9% zonesubty 100% firmdate 100% firmid supplemented · derived / other pipelines 98.8% parcelid2 98.8% ogparcelid2 100% numbldgs 100% parcelstate 100% parcelzip lrid parcelid parcelid2 ogparcelid ogparcelid2 geoid statefp countyfp countyname cousubfp cousubname tractce tractname numbldgs taxacres calcarea ownertype ownername parceladdr parcelcity parcelstate parcelzip lot firmid firmdate fldzone zonesubty 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 parentid, stackid, taxacctnum, taxyear, 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 staticbfe, 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 Moore County:

Frequently asked questions

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

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

How many parcels are in Moore County, TN?

The current dataset contains 4,272 parcel records for Moore County, TN, each with its boundary geometry and assessor attributes.

What is the FIPS code for Moore County, TN?

The FIPS code for Moore County, TN is 47127.

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

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

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

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

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated