Franklin County, OH parcel and infrastructure data API
Korzy has about 500,000 parcel records for Franklin County, Ohio, with source updates through November 2026. Nearly every record carries values, last sale and land use; 85% include year built and 84% include building size. In and around the county the API also maps about 40 data-center projects (15 operating and 1 under construction); about 240 miles of active rail; and 6 power plants with about 15 MW of capacity, led by oil. Look up any parcel by address or coordinates, then check nearby data-center projects, utilities and grid context at the same point.
Parcel coverage in Franklin County
About 500,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from November 2026. Each record has a stable korzy_id you can store and look up again with /api/parcel-record. Share of records with each field:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Nearly all · 99% | |
| Owner name | Some · 9% | |
| Assessed or market value | Nearly all · 99% | |
| Year built | Most · 85% | |
| Building size | Most · 84% | |
| Last sale | Nearly all · 99% | |
| Land use | Nearly all · 99% | |
| Zoning | Not published |
Owner name and mailing address are returned with include_owner=true, which doubles a request's cost: a parcel record costs 2 credits instead of 1. 9% of Franklin County records carry an owner name.
Infrastructure in and around Franklin County
Power plants
6 operable plants with about 15 MW of nameplate capacity; largest by capacity: oil, natural gas, solar. Proposed generators add about 200 MW.
Plant details: /api/power/plants/{plant_id}
Substations and transmission
About 95 in-service substations, 5 rated 230 kV or higher.
About 510 miles of transmission lines: about 45 mi at under 100 kV; about 300 mi at 100–161 kV; about 120 mi at 345 kV.
Water and sewer service
Service areas of about 40 community water systems cover about 82% of the county.
Sewer service areas of about 10 systems cover about 78%.
At a point: /api/utilities/context
Data-center projects
About 40 tracked projects: 15 operating, 1 under construction, 25 status not reported. Reported operating capacity: about 740 MW. Reported planned capacity: about 460 MW.
Within 10 km of a point: /api/datacenters/context
Grid capacity data
2 utility-published grid capacity layers cover parts of Franklin County, including load headroom.
Sources and dates: /api/grid/capacity/summary
Flood zones and wetlands
Special flood hazard areas cover about 10% of the county on the current federal flood maps, published October 2026.
Mapped wetlands cover about 1%.
Rail, ports and freight
- About 240 miles of active rail, about 160 of it main line
- About 120 miles of national freight network highway
- 1 intermodal rail terminal
Within 25 km of a point: /api/logistics/context
Example requests for Franklin County
Real responses from the production API, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.
1. Find a parcel by address
/api/search matches 296 HARTMAN POND DR 205, OH 43207 and returns the parcel's korzy_id, coordinates and record. 1 credit.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'q=296 HARTMAN POND DR 205, OH 43207' \
https://api.korzy.co/api/searchPython
import os
import requests
response = requests.get(
"https://api.korzy.co/api/search",
params={"q": "296 HARTMAN POND DR 205, OH 43207"},
headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
timeout=30,
)
response.raise_for_status()
parcel = response.json()["results"][0]
print(parcel["korzy_id"], parcel["longitude"], parcel["latitude"])Response (trimmed)
{
"results": [
{
"korzy_id": "39049-4815b86734a3a1d801c3",
"address": "296 HARTMAN POND DR 205",
"postcode": "43207",
"county": "Franklin",
"statefp": "39",
"longitude": -82.99649211585884,
"latitude": 39.864488936830575,
"match_type": "exact",
"parcelid": "510-327701",
"parceladdr": "296 HARTMAN POND DR 205",
"situs_zip": "43207",
"usedesc": "EXEMPT PROP OWN/ACQUIRE BY MET AUTH",
"land_use_code": "645",
"yearbuilt": 2023,
"bldgsqft": 1015,
"taxacres": 0.23584909,
"totalvalue": 148200,
"land_value_usd": 25000,
"improvement_value_usd": 123200,
"saledate": "2025-01-16",
"saleamt": 0,
"updated": "2026-11-03",
"geoid": "39049"
}
],
"truncated": false
}With include_owner=true (2 credits) the record adds owner fields, shown here as placeholders:
{
"owner_name": "EXAMPLE HOLDINGS LLC",
"owner_mailing_address": "100 EXAMPLE ST, SAMPLE CITY, ST 00000"
}2. Look up the parcel at a point
/api/query/point returns every parcel whose boundary covers the coordinates; here it returns the same record, 39049-4815b86734a3a1d801c3, in records. 1 credit per 10 records requested.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-82.996492' \
--data-urlencode 'latitude=39.864489' \
--data-urlencode 'limit=5' \
https://api.korzy.co/api/query/pointJavaScript
const params = new URLSearchParams({"longitude": "-82.996492", "latitude": "39.864489", "limit": "5"});
const response = await fetch(`https://api.korzy.co/api/query/point?${params}`, {
headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { records } = await response.json();
console.log(records.map((record) => record.korzy_id));3. Check nearby data-center projects
/api/datacenters/context lists data-center projects within 10 km of the point, nearest first. 1 credit per 10 records requested.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-82.996492' \
--data-urlencode 'latitude=39.864489' \
--data-urlencode 'radius_km=10' \
--data-urlencode 'limit=3' \
https://api.korzy.co/api/datacenters/contextPython
import os
import requests
response = requests.get(
"https://api.korzy.co/api/datacenters/context",
params={"longitude": "-82.996492", "latitude": "39.864489", "radius_km": "10", "limit": "3"},
headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
timeout=30,
)
response.raise_for_status()
for project in response.json()["projects"]:
print(project["name"], project["status"], project["distance_km"])Response (trimmed)
{
"projects": [
{
"project_id": "dc_afe17b9ebd007a3d2d9a",
"name": "Google Columbus",
"operator": "Google",
"status": "operating",
"city": "Columbus",
"state": "OH",
"longitude": -82.9966065,
"latitude": 39.849132999999995,
"location_precision": "footprint",
"operational_mw": 303,
"planned_mw": 464,
"distance_km": 1.7075396231725812
}
],
"radius_km": 10,
"limit": 3,
"truncated": false
}Franklin County data questions
- How many parcels in Franklin County include year built?
- About 430,000 of about 500,000 parcel records (85%) include year built.
- Does the Korzy API return owner names for Franklin County parcels?
- Yes. 9% of Franklin County parcel records carry an owner name. Add include_owner=true to a point, search or parcel-record request; it doubles the request's cost, so a single parcel record costs 2 credits.
- How many data-center projects are in Franklin County?
- Korzy tracks about 40 data-center projects in Franklin County: 25 status not reported, 15 operating and 1 under construction. /api/datacenters/context lists projects within 10 km of any point.
- How much power generation is in Franklin County?
- 6 operable power plants in Franklin County total about 15 MW of nameplate capacity, mainly oil, natural gas and solar.
- Which water systems serve Franklin County?
- Service areas of about 40 community water systems cover about 82% of Franklin County, and sewer service areas cover about 78%. /api/utilities/context returns the water and sewer matches at a point.
More featured counties
- Cuyahoga County, OHabout 520,000 parcels
- Butler County, OHabout 170,000 parcels
- Hamilton County, OHabout 420,000 parcels
Build on Franklin County parcel data
Search, point and record lookups work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics and data-center routes.