Hancock County, OH Parcels & GIS Data

Hancock County, OH parcel data: 38,864 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Hancock County, Ohio parcel data covering 38,864 property records.

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

Hancock County is a county located in the U.S. state of Ohio. As of the 2020 census, the population was 74,920. Its county seat and largest city is Findlay.

FIPS 39063

Official county website: http://www.co.hancock.oh.us

The FIPS code for Hancock County is 39063.

PutnamHenrySenecaWoodWyandotHardinHancock
Hosted Web API$200/mo

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%38,864
parcelid100%38,864
parcelid299.4%38,638
ogparcelid100%38,864
ogparcelid2100%38,864
parentid<0.1%0
stackid<0.1%0
geoid100%38,864
statefp100%38,864
countyfp100%38,864
countyname100%38,864
cousubfp100%38,864
cousubname100%38,864
tractce100%38,864
tractname100%38,864
taxacctnum<0.1%0
taxyear<0.1%0
taxdistrict0.1%27
usecode<0.1%0
usedesc99.4%38,638
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs100%38,864
numunits<0.1%0
yearbuilt<0.1%0
numfloors3.7%1,430
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
taxacres99.4%38,638
calcarea100%38,864
saleamt<0.1%0
saledate<0.1%0
ownertype<0.1%0
ownername0.1%27
owneraddr99.3%38,600
ownercity99.3%38,595
ownerstate99.2%38,544
ownerzip99.3%38,593
parceladdr99.7%38,760
parcelcity90.8%35,282
parcelstate100%38,864
parcelzip100%38,864
legaldesc0.1%27
township100%38,860
section100%38,860
qtrsection100%38,860
range100%38,860
plssdesc100%38,860
book<0.1%0
page<0.1%0
block<0.1%0
lot<0.1%0
parceltype0.6%228
accesstype0.6%228
iucnclass0.1%22
placename4.6%1,795
placetype4.5%1,762
firmid100%38,863
firmdate100%38,863
fldzone100%38,863
zonesubty92.4%35,912
staticbfe<0.1%1
elevmin99.0%38,468
elevmax99.0%38,468
elevavg99.0%38,468
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
naicscode4.6%1,795
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated100%38,864
centroidx100%38,864
centroidy100%38,864
surfpointx100%38,864
surfpointy100%38,864
geom100%38,864
extras100%38,864
ownerlist<0.1%0
placefp55.5%21,571
zoningurl<0.1%0

Schema mapping

How source columns from the acquired Hancock 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 — Hancock County, Ohio (39063) 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 stateparcelid localparcelid stateluc landarea mailaddressall mailcity mailstate mailzip situsaddressall county camadatasite geom 8 cols ⇢ parcelid parcelid2 usedesc taxacres owneraddr ownercity ownerstate ownerzip parceladdr township sourceurl geom extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname 100% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 99.0% elevmin 99.0% elevmax 99.0% elevavg s_fld_haz_ar · FEMA NFHL 100% fldzone 92.4% zonesubty 0.0% staticbfe 100% firmdate 100% firmid supplemented · derived / other pipelines 100% numbldgs 90.8% parcelcity 100% parcelstate 100% parcelzip 100% section 100% qtrsection 100% range 100% plssdesc 55.5% placefp lrid parcelid parcelid2 ogparcelid ogparcelid2 geoid statefp countyfp countyname cousubfp cousubname tractce tractname usedesc numbldgs taxacres calcarea owneraddr ownercity ownerstate ownerzip parceladdr parcelcity parcelstate parcelzip township section qtrsection range plssdesc firmid firmdate fldzone zonesubty staticbfe elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras placefp publish.parcel_layer columns not fed by these sources (49) — empty or below 50% fill in this county parentid, stackid, taxacctnum, taxyear, taxdistrict, usecode, zoningcode, zoningdesc, numunits, yearbuilt, numfloors, bldgsqft, bedrooms halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, saleamt, saledate, ownertype, ownername, legaldesc, book, page, block, lot parceltype, accesstype, iucnclass, placename, placetype, fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding, bldgtype naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit, ownerlist, zoningurl PARCEL 12 mapped · 8 kept in extras · 42 unmapped (NULL) SOURCE COLUMNS HARMONIZED → PARCEL stateparcelid localparcelid stateluc landarea mailaddressall mailcity mailstate mailzip situsaddressall county camadatasite geom parcelid parcelid2 usedesc taxacres owneraddr ownercity ownerstate ownerzip parceladdr township sourceurl geom extras · 8 source columns preserved as json mailnumber, mailstreetprefix, mailstreetname mailstreetsuffix, mailunitnumber, landarea_py, currentto globalid extras not present in source — filled with NULL (42) taxacctnum, taxyear, usecode, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft, bedrooms, halfbaths, fullbaths imprvalue, landvalue, agvalue, totalvalue, saleamt, saledate, ownername, parcelcity, parcelstate, parcelzip, legaldesc, section, qtrsection range, plssdesc, book, page, block, lot, updated, taxdistrict, parentid, fireplaces, heating, cooling, foundation, roofcover, siding, heatfuel

Neighboring counties

Parcel data for counties bordering Hancock County:

Frequently asked questions

Where can I find Hancock County, OH parcel and GIS data?

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

How many parcels are in Hancock County, OH?

The current dataset contains 38,864 parcel records for Hancock County, OH, each with its boundary geometry and assessor attributes.

What is the FIPS code for Hancock County, OH?

The FIPS code for Hancock County, OH is 39063.

What information does each Hancock County, OH parcel record include?

Each Hancock County, OH 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 Hancock County, OH parcel data free?

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

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

On this page