The Q2 2026 release of the Land Records Nationwide Parcel Dataset is here. This release appears as 2026.2 in the lrversion field, and it is the biggest schema expansion we’ve shipped in a single release: 40 new attribute columns covering building construction, environmental risk, ownership classification, protected lands, and federal regulatory data.

If you’ve been waiting for a particular attribute to land before pulling the trigger on a subscription — now is a good time to take another look at our schema documentation.

What’s new in 2026.2

Building & structure attributes

A long-standing gap in the dataset has been the lack of construction-detail attributes. With 2026.2, wherever the source data publishes it, we now harmonize:

• foundation, roofcover, siding, bldgtype — construction details for the primary structure.
• heating, heatfuel, cooling — HVAC system type, fuel source, and cooling system. These are populated against a standardized enumeration (e.g. HEAT PUMP, MINI SPLIT, GEOTHERMAL, PROPANE, NO HEAT) so you can filter and aggregate across counties that previously used incompatible local vocabularies. See the new enumeration tables for the full list.
• fireplaces — integer count of fireplaces in the primary structure.

Ownership & access classification

Three new categorical columns let you slice the dataset by who owns the parcel and whether the public can set foot on it:

• ownertype — populated on every parcel. Classifies the legal nature of the recorded owner: PERSON, BUSINESS, NONPROFIT, GOVERNMENT, TRUST, or ESTATE.
• parceltype — the ownership / management category of the parcel itself, with separate values for each level of government (GOVT FEDERAL, GOVT STATE, GOVT LOCAL, GOVT TRIBAL, GOVT TERRITORY, GOVT SPECIAL DISTRICT), plus NGO, PRIVATE, and PRIVATE WITH PUBLIC EASEMENT.
• accesstype — public physical access status: OPEN, RESTRICTED, CLOSED, or UNKNOWN.

Protected lands & places

• iucnclass — IUCN protected-area classification, useful for conservation, ecology, and recreation use cases.
• placename, placetype — the named place a parcel belongs to (park, monument, forest, refuge, etc.).

Flood & elevation

We’ve joined every parcel against the FEMA National Flood Hazard Layer and a national elevation model:

• firmid, firmdate, fldzone, zonesubty, staticbfe — FEMA flood map identifier and effective date, flood zone designation (e.g. AE, X, VE), zone subtype, and the static Base Flood Elevation.
• elevmin, elevmax, elevavg — min, max, and average elevation across the parcel polygon. Particularly useful for hillside, agricultural, and large-acreage parcels where a single elevation point doesn’t tell the story.

Federal regulatory & industry data

• naicscode — North American Industry Classification System code, where the parcel is associated with a commercial or industrial operation.
• frsid, dfrurl — the EPA Facility Registry Service identifier and the URL of the corresponding EPA Detailed Facility Report.
• caapermit, cwapermit, rcrapermit — Clean Air Act, Clean Water Act, and Resource Conservation and Recovery Act permit identifiers, allowing you to filter for environmentally regulated sites.

Geographic context & lineage

• countyname, cousubfp, cousubname, tractce, tractname — county name, county-subdivision FIPS code and name, and census tract code and name. No more joining against TIGER just to get a human-readable county name.
• taxdistrict — named tax district from the source assessor data.
• ogparcelid, ogparcelid2 — the original parcel identifiers as they appear in the source feed, preserved verbatim. Use these to round-trip back to the authoritative county record.
• parentid, stackid — identifiers for parcel hierarchies and stacked parcels (condos, multi-record assemblages). If you’ve ever been frustrated by a county that returns five rows for what visually looks like one parcel, stackid is the column you’ve been waiting for.
• extras — a JSON column for jurisdiction-specific attributes that don’t fit any of the standard columns. We’ll continue promoting fields out of extras into first-class columns as we see them recur across enough jurisdictions.

Renames & deprecations

• assdacres has been renamed to taxacres. The semantics are unchanged.

Improved website search

Alongside the data release, we’ve rebuilt the search box on the landrecords.us homepage. A few things you’ll notice:

• Address search is real now. The old homepage search was limited to exact parcel-number matches. The new search lets you type a street address — "1500 Main St", "742 Evergreen Terrace" — and get a ranked list of matching parcels nationwide. The dropdown shows the parcel ID, secondary parcel ID where present, and the parcel address (or city/county) as a disambiguator.
• Geometry previews in the dropdown. Each result includes a small SVG thumbnail of the parcel boundary, so you can pick the right one at a glance instead of clicking through to check.
• The Data Explorer now reflects the expanded schema, so when you write a natural-language query like "residential parcels in flood zone AE within 10 miles of Charleston SC", the LLM has the new columns available to it.

How to access

Current subscribers can download 2026.2 immediately through your account dashboard. If you have an API plan, the new columns are already live at the API endpoints — no client changes required, the new fields simply appear on parcel responses where source data is available.

Not yet a customer? Browse the US Nationwide Parcel Dataset, try the Data Explorer, or read up on API access. As always, questions and feedback are welcome at hello@landrecords.us — we genuinely want to know what you’re building.