Utah County, UT parcel and infrastructure data API

Korzy has about 280,000 parcel records for Utah County, Utah, with source updates through October 2026. 87% include land use and 83% include values. In and around the county the API also maps about 15 data-center projects (6 operating and 4 under construction); about 10 power plants with about 2,000 MW of capacity, led by natural gas; and about 190 miles of active rail. 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 Utah County

About 280,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from October 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 · 98%
Owner nameSome · 25%
Assessed or market valueMost · 83%
Year builtMany · 73%
Building sizeMany · 73%
Last saleNot published
Land useMost · 87%
ZoningNot published

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

Infrastructure in and around Utah County

Power plants

About 10 operable plants with about 2,000 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, solar. Proposed generators add about 160 MW.

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

Substations and transmission

About 160 in-service substations, 3 rated 230 kV or higher.

About 1,000 miles of transmission lines: about 110 mi at under 100 kV; about 560 mi at 100–161 kV; about 330 mi at 345 kV.

Water and sewer service

Service areas of about 50 community water systems cover about 17% of the county.

Sewer service areas of about 10 systems cover about 10%.

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

Data-center projects

About 15 tracked projects: 6 operating, 4 under construction, 4 proposed. Reported operating capacity: about 200 MW. Reported planned capacity: about 1,900 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

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

Mapped wetlands cover about 2%.

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

Rail, ports and freight

  • About 190 miles of active rail, about 150 of it main line
  • About 45 miles of national freight network highway

Within 25 km: /v1/lookup section logistics

Example requests for Utah 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 596 N MILL RD, Vineyard, UT 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":"596 N MILL RD, Vineyard, UT","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "596 N MILL RD, Vineyard, UT", "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": -111.73845245044964,
    "latitude": 40.30777415,
    "address": "596 N MILL RD, Vineyard",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "49049-7479c2a3b626f5320466",
        "korzy_id": "49049-7479c2a3b626f5320466",
        "parcelid": "560480002",
        "parceladdr": "596 N MILL RD",
        "parcelcity": "Vineyard",
        "situs_zip": "84059",
        "statefp": "49",
        "geoid": "49049",
        "longitude": -111.73845245044964,
        "latitude": 40.30777415,
        "usedesc": "Commercial",
        "yearbuilt": 2023,
        "bldgsqft": 8580,
        "taxacres": 1.413568,
        "totalvalue": 2089500,
        "land_value_usd": 900500,
        "market_value_usd": 2089500,
        "updated": "2026-10-19"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_8a590b1ddba2cb6e27e2",
            "project_id": "dc_8a590b1ddba2cb6e27e2",
            "name": "Flexential Salt Lake City - Lindon",
            "operator": "Flexential",
            "status": "operating",
            "state": "UT",
            "city": "Lindon",
            "address": "333 South 520 West",
            "longitude": -111.7278754,
            "latitude": 40.332648,
            "location_precision": "exact",
            "operational_mw": 0.57,
            "source_count": 3,
            "source_date": "2026-09-21",
            "mapped": true,
            "distance_km": 2.907581120622117
          },
          {
            "id": "datacenter:dc_abb4e440b2ea16bbddcd",
            "project_id": "dc_abb4e440b2ea16bbddcd",
            "name": "Voonami Orem Data Center",
            "operator": "Voonami",
            "status": "operating",
            "state": "UT",
            "city": "Orem",
            "longitude": -111.69443,
            "latitude": 40.29816,
            "location_precision": "approximate",
            "operational_mw": 2,
            "source_count": 1,
            "source_date": "2026-08-15",
            "mapped": true,
            "distance_km": 3.883211481633515
          },
          {
            "id": "datacenter:dc_f1bd02bee70522e86d5a",
            "project_id": "dc_f1bd02bee70522e86d5a",
            "name": "Fibernet Orem Data Center",
            "operator": "Fibernet",
            "status": "operating",
            "state": "UT",
            "city": "Orem",
            "longitude": -111.67595,
            "latitude": 40.27619,
            "location_precision": "exact",
            "source_count": 1,
            "source_date": "2026-08-15",
            "mapped": true,
            "distance_km": 6.358955639550305
          }
        ],
        "truncated": false,
        "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 49049-7479c2a3b626f5320466, 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":"49049-7479c2a3b626f5320466"}],"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/49049-7479c2a3b626f5320466
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("49049-7479c2a3b626f5320466")}`, {
  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);

Utah County data questions

How many parcels in Utah County include year built?
About 200,000 of about 280,000 parcel records (73%) include year built.
Does the Korzy API return owner names for Utah County parcels?
Yes. 25% of Utah 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 Utah County?
Korzy tracks about 15 data-center projects in Utah County: 6 operating, 4 under construction and 4 proposed. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Utah County?
About 10 operable power plants in Utah County total about 2,000 MW of nameplate capacity, mainly natural gas, battery and pumped storage and solar.
Which water systems serve Utah County?
Service areas of about 50 community water systems cover about 17% of Utah County, and sewer service areas cover about 10%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

All featured Utah counties

Build on Utah 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.