Washington County, OH Parcels & GIS Data

Washington County, OH parcel data: 62,705 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Washington County, Ohio parcel data covering 62,705 property records.

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

Washington County is a county located in the southeastern part of the U.S. state of Ohio. As of the 2020 census, the population was 59,711. Its county seat is Marietta.

FIPS 39167

Official county website: https://www.washingtongov.org/

The FIPS code for Washington County is 39167.

TylerMonroeNobleMorganPleasantsWoodAthensWashington

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%62,705
parcelid100%62,703
parcelid2100%62,703
ogparcelid100%62,705
ogparcelid2100%62,705
parentid<0.1%0
stackid<0.1%0
geoid100%62,705
statefp100%62,705
countyfp100%62,705
countyname100%62,705
cousubfp100%62,705
cousubname100%62,705
tractce100%62,705
tractname100%62,705
taxacctnum<0.1%0
taxyear<0.1%0
taxdistrict<0.1%1
usecode<0.1%0
usedesc<0.1%0
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs100%62,704
numunits1.2%745
yearbuilt<0.1%0
numfloors1.2%766
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
taxacres98.1%61,512
calcarea100%62,705
saleamt<0.1%0
saledate<0.1%0
ownertype95.9%60,129
ownername95.9%60,129
owneraddr<0.1%1
ownercity<0.1%0
ownerstate<0.1%1
ownerzip<0.1%0
parceladdr89.5%56,099
parcelcity87.4%54,806
parcelstate100%62,705
parcelzip100%62,705
legaldesc<0.1%1
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%1
lot<0.1%1
parceltype2.7%1,710
accesstype2.7%1,710
iucnclass1.7%1,043
placename5.4%3,411
placetype5.4%3,371
firmid100%62,705
firmdate100%62,705
fldzone100%62,705
zonesubty83.8%52,536
staticbfe0.1%82
elevmin99.3%62,278
elevmax99.3%62,278
elevavg99.3%62,278
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
naicscode19.3%12,112
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated100%62,704
centroidx100%62,705
centroidy100%62,705
surfpointx100%62,705
surfpointy100%62,705
geom100%62,705
extras100%62,705
ownerlist<0.1%0

Schema mapping

How source columns from the acquired Washington 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 — Washington County, Ohio (39167) 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 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.3% elevmin 99.3% elevmax 99.3% elevavg s_fld_haz_ar · FEMA NFHL 100% fldzone 83.8% zonesubty 0.1% staticbfe 100% firmdate 100% firmid supplemented · derived / other pipelines 100% numbldgs 95.9% ownertype 95.9% ownername 87.4% parcelcity 100% parcelstate 100% parcelzip lrid parcelid parcelid2 ogparcelid ogparcelid2 geoid statefp countyfp countyname cousubfp cousubname tractce tractname usedesc numbldgs taxacres calcarea ownertype ownername owneraddr ownercity ownerstate ownerzip parceladdr parcelcity parcelstate parcelzip township firmid firmdate fldzone zonesubty staticbfe elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras publish.parcel_layer columns not fed by these sources (50) — 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, legaldesc, section, qtrsection, range, plssdesc, book, page block, lot, parceltype, accesstype, iucnclass, placename, placetype, fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit, ownerlist 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 Washington County:

Frequently asked questions

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

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

How many parcels are in Washington County, OH?

The current dataset contains 62,705 parcel records for Washington County, OH, each with its boundary geometry and assessor attributes.

What is the FIPS code for Washington County, OH?

The FIPS code for Washington County, OH is 39167.

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

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

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

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

On this page