Davidson County, TN parcel and infrastructure data API

Korzy has about 290,000 parcel records for Davidson County, Tennessee, with source updates through November 2026. Nearly every record carries owner names, values, last sale and land use. In and around the county the API also maps about 15 data-center projects (7 operating and 1 under construction); 1 port with reported cargo; and 4 power plants with about 55 MW of capacity, led by hydro. 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 Davidson County

About 290,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 /v1/records/{id}. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 99%
Year builtNot published
Building sizeNot published
Last saleNearly all · 100%
Land useNearly all · 95%
ZoningNearly all · 99%

Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 99% of Davidson County records carry an owner name.

Infrastructure in and around Davidson County

Power plants

4 operable plants with about 55 MW of nameplate capacity; largest by capacity: hydro, natural gas, solar.

Within 50 km: /v1/lookup section power; details: /v1/records/{id}

Substations and transmission

About 100 in-service substations, 2 rated 230 kV or higher.

About 570 miles of transmission lines: about 45 mi at under 100 kV; about 370 mi at 100–161 kV; about 30 mi at 500 kV.

Water and sewer service

Service areas of about 15 community water systems cover about 88% of the county.

Sewer service areas of 4 systems cover about 87%.

At an address or point: /v1/lookup section utilities

Data-center projects

About 15 tracked projects: 7 operating, 1 under construction, 2 proposed, 3 status not reported. Reported planned capacity: about 90 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

Special flood hazard areas cover about 13% of the county on the current federal flood maps, published October 2026.

Mapped wetlands cover about 1%.

At an address or point: /v1/lookup section environment

Rail, ports and freight

  • About 200 miles of active rail, about 120 of it main line
  • About 100 miles of national freight network highway
  • 1 port area with reported cargo tonnage
  • 1 intermodal rail terminal

Within 25 km: /v1/lookup section logistics

Example requests for Davidson County

The lookup response is a real production response, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel and nearby data-center projects

/v1/lookup matches 420 MURFREESBORO PIKE, NASHVILLE, TN and returns the parcel's korzy_id and record, plus the data-center projects within 10 km, nearest first. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"420 MURFREESBORO PIKE, NASHVILLE, TN","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "420 MURFREESBORO PIKE, NASHVILLE, TN", "sections": ["datacenters"]},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=60,
)
response.raise_for_status()
body = response.json()
parcel = body["parcels"]["records"][0]
print(parcel["korzy_id"], body["sections"]["datacenters"]["status"])
Production response (trimmed)
{
  "location": {
    "longitude": -86.74739223948211,
    "latitude": 36.14426365,
    "address": "420 MURFREESBORO PIKE, NASHVILLE",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "47037-7f64a1f0951f9aca0538",
        "korzy_id": "47037-7f64a1f0951f9aca0538",
        "parcelid": "10601005600",
        "parceladdr": "420 MURFREESBORO PIKE",
        "parcelcity": "NASHVILLE",
        "situs_zip": "37210",
        "statefp": "47",
        "geoid": "47037",
        "longitude": -86.74739223948211,
        "latitude": 36.14426365,
        "usedesc": "HOTEL/MOTEL",
        "land_use_code": "059",
        "zoning_code": "CS",
        "taxacres": 1.8,
        "totalvalue": 1301560,
        "land_value_usd": 3239800,
        "improvement_value_usd": 14100,
        "assessed_value_usd": 1301560,
        "market_value_usd": 3253900,
        "saledate": "2004-03-15",
        "saleamt": 506306,
        "updated": "2025-01-01"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_16a525ce366b52f189c2",
            "project_id": "dc_16a525ce366b52f189c2",
            "name": "Cogent Data Center - Nashville (338 Woodycrest Ave)",
            "operator": "Cogent Communications",
            "status": "operating",
            "state": "TN",
            "city": "Nashville",
            "address": "338 Woodycrest Avenue",
            "longitude": -86.752262,
            "latitude": 36.132143,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-10-10",
            "mapped": true,
            "distance_km": 1.4169285776296612
          },
          {
            "id": "datacenter:dc_3fa4e7110230a7bbf1f4",
            "project_id": "dc_3fa4e7110230a7bbf1f4",
            "name": "Unnamed data center",
            "status": "unknown",
            "state": "TN",
            "longitude": -86.7641314700172,
            "latitude": 36.14049695,
            "location_precision": "footprint",
            "source_count": 2,
            "source_date": "2026-02-09",
            "mapped": true,
            "distance_km": 1.5603794370563493
          },
          {
            "id": "datacenter:dc_6d785382fb83f8fee7c0",
            "project_id": "dc_6d785382fb83f8fee7c0",
            "name": "H5 Data Centers Nashville (147 Fourth Avenue)",
            "operator": "H5 Data Centers",
            "status": "operating",
            "state": "TN",
            "city": "Nashville",
            "address": "147 Fourth Avenue North, 8th Floor",
            "longitude": -86.778674,
            "latitude": 36.162626,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-09-21",
            "mapped": true,
            "distance_km": 3.4723317207629316
          }
        ],
        "truncated": true,
        "note": "Straight-line distance to the reported project point; inspect location_precision. Projects merge supported source matches, not every nearby building. Approximate locations do not identify a parcel. Reported IT load, facility power, planned capacity and estimates remain separate source claims. No record or unknown status does not establish absence or inactivity."
      },
      "provenance": [
        {
          "dataset": "datacenters",
          "as_of": "2026-11-02",
          "data_version": "20261102T123021962884Z"
        }
      ]
    }
  },
  "credits": {
    "charged": 2,
    "refunded": 0
  }
}

2. Add owner and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 47037-7f64a1f0951f9aca0538, with the owner group. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"korzy_id":"47037-7f64a1f0951f9aca0538"}],"fields":["identity","sale","owner"]}' \
  https://api.korzy.co/v1/enrich

3. Fetch the record again by ID

/v1/records/{id} returns the stored parcel's full record, without owner fields. 1 credit.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  https://api.korzy.co/v1/records/47037-7f64a1f0951f9aca0538
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("47037-7f64a1f0951f9aca0538")}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { record } = await response.json();
console.log(record.parceladdr, record.usedesc);

Davidson County data questions

How many parcels in Davidson County include last sale?
About 290,000 of about 290,000 parcel records (100%) include last sale.
Does the Korzy API return owner names for Davidson County parcels?
Yes. 99% of Davidson County parcel records carry an owner name. Ask /v1/enrich for the owner group; each parcel then costs 2 credits instead of 1 credit. Lookups and records never include owner fields.
How many data-center projects are in Davidson County?
Korzy tracks about 15 data-center projects in Davidson County: 7 operating, 3 status not reported and 2 proposed. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Davidson County?
4 operable power plants in Davidson County total about 55 MW of nameplate capacity, mainly hydro, natural gas and solar.
Which water systems serve Davidson County?
Service areas of about 15 community water systems cover about 88% of Davidson County, and sewer service areas cover about 87%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

All featured Tennessee counties

Build on Davidson County parcel data

Lookups, enrichment and records work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics, power, grid, data-center and terrain sections.