How many parcels in Riverside County include year built?

About 910,000 of about 990,000 parcel records (92%) include year built.

Does the Korzy API return owner names for Riverside County parcels?

Riverside County parcel records do not include owner names. Values, land use and building facts are returned where the county publishes them.

How many data-center projects are in Riverside County?

Korzy tracks 1 data-center project in Riverside County: 1 status not reported. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.

How much power generation is in Riverside County?

About 120 operable power plants in Riverside County total about 11,000 MW of nameplate capacity, mainly solar, battery and pumped storage and natural gas.

Which water systems serve Riverside County?

Service areas of about 120 community water systems cover about 31% of Riverside County, and sewer service areas cover about 13%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

Riverside County, CA parcel and infrastructure data API

Korzy has about 990,000 parcel records for Riverside County, California, with source updates through October 2026. 92% include year built and 92% include building size. In and around the county the API also maps about 120 power plants with about 11,000 MW of capacity, led by solar; 1 data-center project; and about 230 miles of active rail. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.

Get an API key Read the API docs

Parcel coverage in Riverside County

About 990,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:

Field	Coverage	Share
Situs address	Nearly all · 100%
Owner name	Not published
Assessed or market value	Most · 85%
Year built	Most · 92%
Building size	Most · 92%
Last sale	Most · 79%
Land use	Most · 91%
Zoning	Not published

Riverside County records do not include owner names. See pricing for credit costs.

Infrastructure in and around Riverside County

Power plants

About 120 operable plants with about 11,000 MW of nameplate capacity; largest by capacity: solar, battery and pumped storage, natural gas. Proposed generators add about 3,200 MW.

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

Substations and transmission

About 170 in-service substations, about 15 rated 230 kV or higher.

About 2,100 miles of transmission lines: about 430 mi at under 100 kV; about 840 mi at 100–161 kV; about 450 mi at 220–287 kV; about 360 mi at 500 kV.

Water and sewer service

Service areas of about 120 community water systems cover about 31% of the county.

Sewer service areas of about 30 systems cover about 13%.

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

Data-center projects

1 tracked project: 1 status not reported. Reported planned capacity: about 270 MW.

Within 10 km: /v1/lookup section datacenters

Grid capacity data

2 utility-published grid capacity layers cover parts of Riverside County, including loading forecasts.

Nearby records: /v1/lookup section grid

Flood zones and wetlands

Special flood hazard areas cover about 3% 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 230 miles of active rail, about 160 of it main line
About 310 miles of national freight network highway

Within 25 km: /v1/lookup section logistics

Example requests for Riverside 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 its water and sewer service

/v1/lookup matches 21730 BUNDY CANYON RD, WILDOMAR, CA and returns the parcel's korzy_id and record, plus the water and sewer service areas at the parcel and the nearest treatment plants. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"21730 BUNDY CANYON RD, WILDOMAR, CA","sections":["utilities"]}' \
  https://api.korzy.co/v1/lookup

Python

import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "21730 BUNDY CANYON RD, WILDOMAR, CA", "sections": ["utilities"]},
    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"]["utilities"]["status"])

Production response (trimmed)

{
  "location": {
    "longitude": -117.28057757238594,
    "latitude": 33.627806750000005,
    "address": "21730 BUNDY CANYON RD, WILDOMAR",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "06065-919861d16ad4398b7288",
        "korzy_id": "06065-919861d16ad4398b7288",
        "parcelid": "366210052",
        "parceladdr": "21730 BUNDY CANYON RD",
        "parcelcity": "WILDOMAR",
        "situs_zip": "92595",
        "statefp": "06",
        "geoid": "06065",
        "longitude": -117.28057757238594,
        "latitude": 33.627806750000005,
        "usedesc": "Retail - General",
        "yearbuilt": 2013,
        "bldgsqft": 5280,
        "taxacres": 1.45,
        "totalvalue": 0,
        "saledate": "2006-10-19",
        "updated": "2026-10-13"
      }
    ],
    "truncated": false
  },
  "sections": {
    "utilities": {
      "status": "ok",
      "data": {
        "water": [
          {
            "id": "utility:water:5118",
            "feature_id": "water:5118",
            "name": "ELSINORE VALLEY MWD",
            "boundary_basis": "System Sourced"
          }
        ],
        "sewer": [
          {
            "id": "utility:sewer:4641",
            "feature_id": "sewer:4641",
            "name": "Railroad Canyon WWTP",
            "boundary_basis": "Modeled"
          }
        ],
        "treatment_plants": [
          {
            "id": "utility:treatment:9644",
            "feature_id": "treatment:9644",
            "name": "Railroad Canyon WWTP",
            "distance_km": 4.073221445210049
          },
          {
            "id": "utility:treatment:9631",
            "feature_id": "treatment:9631",
            "name": "Perris Valley Regional WRF",
            "distance_km": 7.928212609595855
          },
          {
            "id": "utility:treatment:9645",
            "feature_id": "treatment:9645",
            "name": "Lake Elsinore Regional WWTP",
            "distance_km": 8.11880224648979
          }
        ],
        "truncated": {
          "water": false,
          "sewer": false
        }
      },
      "provenance": [
        {
          "dataset": "water",
          "data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
        },
        {
          "dataset": "sewer",
          "data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
        },
        {
          "dataset": "treatment",
          "data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
        }
      ]
    }
  },
  "credits": {
    "charged": 2,
    "refunded": 0
  }
}

2. Add value and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 06065-919861d16ad4398b7288. 1 credit.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"korzy_id":"06065-919861d16ad4398b7288"}],"fields":["identity","value","sale"]}' \
  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/06065-919861d16ad4398b7288

JavaScript

const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("06065-919861d16ad4398b7288")}`, {
  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);

Riverside County data questions

How many parcels in Riverside County include year built?: About 910,000 of about 990,000 parcel records (92%) include year built.
Does the Korzy API return owner names for Riverside County parcels?: Riverside County parcel records do not include owner names. Values, land use and building facts are returned where the county publishes them.
How many data-center projects are in Riverside County?: Korzy tracks 1 data-center project in Riverside County: 1 status not reported. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Riverside County?: About 120 operable power plants in Riverside County total about 11,000 MW of nameplate capacity, mainly solar, battery and pumped storage and natural gas.
Which water systems serve Riverside County?: Service areas of about 120 community water systems cover about 31% of Riverside County, and sewer service areas cover about 13%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

San Diego County, CABorders Riverside County · about 1.1 million parcels
Los Angeles County, CAabout 2.5 million parcels
Contra Costa County, CAabout 410,000 parcels
Solano County, CAabout 150,000 parcels
Sacramento County, CAabout 550,000 parcels

All featured California counties

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

Get an API key See pricing API reference Use cases for parcel and infrastructure data