Regrid Parcel Schemas

Our schema is also available as a downloadable spreadsheet here: Regrid Product Schemas

All 160M+ parcels in Regrid's U.S. data include precise parcel boundary geometry. The attributes documented below are joined to those boundaries - every field describes a parcel whose geometry is already in the data.

Attribute coverage varies by county and is refreshed on an ongoing basis as counties update their data. Current per-county, per-attribute fill rates are published in the live Regrid Coverage Report; each attribute has a column named {fieldname}_pct with the percent of parcels populated in each county.

Automated coverage report access (for AI assistants and scripts)

The full report is large (~3,200 rows × 175 columns) and typically exceeds what an AI tool can read in a single fetch, so request only the rows you need with a filtered query. This URL returns all coverage rows for one state as CSV - replace MI with any two-letter state code:

https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/gviz/tq?tqx=out:csv&gid=1284673582&tq=SELECT%20*%20WHERE%20A%3D%27MI%27

To narrow to a single county, extend the query to SELECT * WHERE A='MI' AND B='Wayne' (URL-encoded: tq=SELECT%20*%20WHERE%20A%3D%27MI%27%20AND%20B%3D%27Wayne%27). Column A is the two-letter state code and column B is the county name. The first row returned is the column header - find your attribute's {fieldname}_pct column by name. The complete report is also available as a single CSV download; its first data row holds nationwide coverage percentages for every attribute, so even a truncated fetch returns national figures.

How to read this page

Each attribute below lists the schemas it appears in (Premium & Standard, or Premium only), its data type, its source, and whether it is standardized, followed by structured guidance. Where a county-provided field is not standardized, the entry names the standardized field to use instead for cross-jurisdiction analysis.

What each label means

Use it for — what the field is and the analyses it supports.
Do not use it for — known misuses and traps. Where a standardized or preferred alternative field exists, it is named here, with the reason.
⭐ — marks the recommended field where several fields cover similar ground - typically the standardized or Regrid-calculated field, preferred over raw county counterparts.
Also known as — the italic line ending each entry: plain-language phrases and technical aliases for the field, included mainly for search.
API Queryable — Yes means the field can be used as a filter on the /parcels/query API endpoint. A maximum of 4 fields can be combined in one query, and available operators depend on field type - see Filter Parcels: Query by Field. Fields marked — can be read in API responses but not used as query filters.
Related fields — fields that do the same job or are commonly confused with this one. Where a preferred or standardized alternative exists, it is listed first.
How it's made — how the value is produced or sourced.
Coverage — qualitative coverage notes, plus the exact column to check in the live Coverage Report for current per-county fill rates.

Definitions for every Source, Standardization, and Category value used below are in the reference section at the bottom of this page.

Schema categories

Every attribute lives on one of the category pages below. Each page is self-contained: full guidance per field, including what not to use it for and the recommended alternatives.

Identification Fields (15 attributes) — Parcel IDs and stable keys for lookup and for tracking parcels over time. Key fields: ll_uuid.
Land Use & Zoning Fields (16 attributes) — How land is used and regulated - both local (as-provided) and standardized classifications. Key fields: zoning_type, lbcs_activity, lbcs_function.
Buildings & Structures Fields (18 attributes) — Structure presence, counts, size, and characteristics. Key fields: ll_address_count, ll_bldg_count.
Assessment & Tax Fields (8 attributes) — Assessed values, exemptions, and property tax amounts.
Sales & Transfers Fields (3 attributes) — Sale and ownership-transfer history.
Ownership Fields (11 attributes) — Who owns the parcel and how ownership is classified. Key fields: owner, lbcs_ownership.
Addresses Fields (41 attributes) — Parcel (situs) and owner mailing addresses, with USPS validation attributes. Key fields: scity.
Parcel Geometry & Area Fields (10 attributes) — Parcel size, centroid coordinates, and survey references. Key fields: ll_gisacre, ll_gissqft.
Legal Description & Subdivision Fields (7 attributes) — Recorded legal references: plat, book, page, lot, block, subdivision.
Related Geographies Fields (12 attributes) — Census and administrative geographies containing the parcel.
Environment & Risk Fields (13 attributes) — Flood, natural-hazard, terrain, land-cover, and biodiversity attributes. Key fields: fema_flood_zone, cdl_majority_category.
Public Lands & Access Fields (1 attributes) — Public-land access designations.
Infrastructure & Proximity Fields (2 attributes) — Infrastructure flags and distance measures.
Socioeconomics & Markets Fields (8 attributes) — Census-blockgroup-level demographic and market indicators joined to the parcel.
Source & Lineage Fields (4 attributes) — Data provenance, refresh dates, and record timestamps.

Reference: value definitions

Source types

Authoritative — The value originates with the official source of record - county assessors and GIS offices, USPS, FEMA, the Census Bureau, USDA, USGS. Regrid normalizes formatting, but the underlying value is the authority's.
Regrid — Calculated or derived by Regrid - from parcel geometry, imagery, or by standardizing authoritative values into one consistent nationwide scheme.
Regrid Partner — Produced by a Regrid data partner and joined to parcels by Regrid (Esri, Precisely, Placekey, NatureServe).
Third Party — Licensed from a third-party provider and matched to parcels by Regrid (Zoneomics standardized zoning).

Source subcategories

County — County assessor or local GIS office.
Federal — Federal datasets: USPS, FEMA, US Census Bureau, USDA, USGS.
Regrid — Regrid's own calculations and standardizations.
Esri — Esri Updated Demographics (US Census Bureau data via Esri).
Zoneomics — Zoneomics standardized zoning data.
Precisely — PreciselyID addressable-location identifiers.
Placekey — Placekey location identifiers.
NatureServe — NatureServe InSite biodiversity scoring.

Standardization

Yes — Values follow one consistent scheme nationwide. Safe to compare and aggregate across counties and states.
No — Values are as provided by the local source; meaning and format vary by jurisdiction. Use for local detail, not for cross-place comparison. Where a standardized alternative exists, it is named explicitly in the field's "Do not use it for" guidance and listed first under "Related fields".
Some — Regrid normalizes formatting (e.g. address cleaning and parsing) but the underlying values originate locally. Broadly comparable, with local variation.