Skip to main content
Every normalized coded field of the v3 parcel record stores a value from the Realie code system — one national codebook, applied identically in API responses and bulk full-record exports. The deliberate exception is the jurisdiction-issued fields (taxDistrictCode, county/state land-use codes, zoningInfo.zoningCode): those carry each jurisdiction’s own code verbatim and have no national decode table. This page is the complete decode reference: every code family, every code, and the fields that carry them. Field names below use the record’s nested paths; the v2-compatible flat shape carries the same values under its flat field names (see the flat-shape field names at the bottom of this page).

​
How the code system works

Coded facts appear in the record in one of three representation classes:
  1. Realie codes (XX####) — a two-letter family prefix plus a four-digit number, e.g. RM0001 (COMPOSITION SHINGLE) in the roof-material family. These identify named things: deed types, roof materials, loan products. The digits are an identifier, not a rank — RM0002 is not “more” than RM0001, and the numbers must never be compared, sorted semantically, or used in arithmetic. Always decode them with the tables on this page. One family keeps its historical form: the property-use vocabulary remains the familiar 4-digit scheme (1001, 2000, …) with unchanged code identities.
  2. Integer ordinal and band scales — values that really are ordered. building.quality and building.condition are integers on a 1–20 scale (higher is better); the legacy length-of-residence, LTV-range, and equity-range members are integer band indexes (ordered buckets). Ordinals compare within their own field only — a quality of 11 and a condition of 11 are unrelated facts.
  3. Numeric quantities — real measurements stored as numbers with units, such as mortgages[].rateChangeFrequency (an interval in years). No decode table applies.
The vocabulary is append-only from this release forward. A code id published in this release keeps its meaning forever: ids are never renumbered, reused, or redefined. Coded values persisted from deliveries before August 19, 2026 predate this guarantee — decode those against the Pre-v3 Code Tables (Frozen) archive, not the tables below. New codes join a family under the next free number, and every addition is announced in the changelog. You can safely persist decoded meanings, build logic on specific ids, and update your copy of these tables incrementally. Within each family the initial numbering was assigned by how common each code is nationally, so low numbers tend to be the common members — a convenience of the initial release, not a contract. Some fields ship their vocabulary ahead of their data: the table exists, but no parcel carries a value yet. These are marked on their tables below and will populate in later data releases without any contract change.

​
Classification

Broad property class of the parcel (PC####).
Specific property use. Same 4-digit scheme and code identities as previous releases — an individual parcel can still receive a different code in a newer source delivery because its use or source classification changed. Migrate the vocabulary by code identity rather than translating one use code into another. The top-level convenience key useCode carries the same value.

​
Building characteristics

Each table in this section applies in two places: the top-level building object (the parcel’s primary-building summary) and the per-building mirror under buildingInformation.buildings[].characteristics. building.quality and building.condition are integer ordinals — see Ordinal scales.
Specific building form (BT#### — manufactured house, duplex, row home, …).
Property sub-type of the building (PS####).
Construction class of the building shell (BC#### — fire-resistance and materials class).
Height class of the building (HB####).
Level configuration of the building (BL####).
Footprint shape of the building (BH####).
Architectural style (AS####).
Floor-plan layout (FP####).
Primary structural construction (CT#### — frame, masonry, …).
How the building was produced (CM####).
Exterior wall covering or material (EW####).
Interior wall finish material (IW####).
Roof covering material (RM####).
Roof geometry (RS#### — gable, hip, flat, …).
Floor covering material (FL####).
Foundation type (FN####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.
Basement presence and type (BS####).
Attic presence and finish (AT####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.
Parking arrangement (PK#### — attached garage, carport, …).
Driveway surface material (DM####).
Driveway form (DT####). building.driveway also carries no code when the parcel has no recorded driveway.
Pool or spa type (PT####). The sibling boolean building.pool.exists says whether any pool is present; type is omitted when the source records a pool without a type.
Pool features (PF####); an array — a pool can carry several.
Recorded amenities (AM####); an array — a building can carry several.
Additional named rooms (OR####); an array.
Development type of the building’s setting (DV####).
Construction/completion status (DS####).
Historic designation (HT####).
Age class of the building (AC####).
The kind of measured building area a buildingAreas entry represents (BA####). building.buildingAreaType (and buildingInformation.buildings[].characteristics.buildingAreaType) use the same table to say what kind of measurement the building’s headline buildingArea is.

​
Heating and cooling

Heating is described by five independent facets — equipment, distribution, energy source, configuration, and coverage — because counties record different aspects of the same system. Any subset may be present. Each field appears at the top level (heating.*, cooling.*, primary building) and per building under buildingInformation.buildings[].heating / .cooling.
Heating equipment (HE#### — heat pump, baseboard, stove, …).
How heat is delivered (HD#### — forced air, radiant, steam, …).
Fuel or energy source (HS#### — natural gas, electric, oil, …).
System configuration (HC#### — central vs. unit).
Whether (and how completely) the building is heated, used when the source proves presence without naming the system (HX####).
Cooling equipment (CL#### — central, evaporative, window unit, …).

​
Utilities

Water service for the parcel (WS####).
Sewer service for the parcel (SW####).
Gas service for the parcel (GS####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.
Electric service for the parcel (ES####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.

​
Land and lot

Site topography (TP####).
Road access to the parcel (RA####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.
Waterfront type (WF####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.
View quality (VQ####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.
Lot composition of the legal parcel (LT#### — more than one lot, partial lot, …).

​
Tax

Tax classification of the parcel (TC####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship.

​
Sales and transfers

Recorded instrument (deed) type on the sale or transfer event (TT####).
Why a sale is — or is not — considered a market (arm’s-length) transaction (TQ####). The sibling boolean salesHistory[].armsLength carries the derived arm’s-length verdict; qualification is omitted when the source recorded no reviewed qualification signal for that sale. The flat shape carries this per event as transfers[].saleCode.
How the recorded sale-price figure was obtained (PD#### — stated on the document, computed from transfer tax, from an affidavit, …).
What kind of entity the buyer is (BE#### — individual, company, trust, …).
Relationship between co-buyers (BR#### — husband and wife, …).
Legal role the buyer takes in the transfer (RO#### — beneficiary, trustee, …).
How the buyer holds title (BV#### — joint tenants, tenants in common, …).

​
Mortgages

Loan product or program (LN####).
What the loan financed (LX#### — purchase, refinance, construction, …).
Interest-rate structure (IR#### — fixed, variable, …).
Amortization structure (LA#### — balloon, …).
Index an adjustable rate is tied to (RI####).
Riders recorded on the mortgage instrument (RD####); an array — an instrument can carry several.
Recorded loan-event document types (LD####). Codes are published ahead of population: no parcel stores a value for this member in the current data generation. The table is the committed vocabulary the member will use when values ship. mortgages[].assignmentsReleases[].recordType currently carries the readable values assignment / release.
Numeric quantity, not a code: how often an adjustable rate may change, as an interval in years (e.g. 1.0 = annually, 0.083 ≈ monthly). No decode table applies.

​
Liens and foreclosures

Type of the recorded involuntary lien or judgment (LI####).
Type of the recorded foreclosure event (FR#### — lis pendens, notice of default, …). The flat shape exposes the most recent record’s type as top-level forecloseCode.

​
Ordinal scales and numeric quantities

These fields are numbers, not opaque codes: order is meaningful within each field, and no XX#### prefix applies.
Construction quality — the normalized grade of construction quality, workmanship, and materials on an integer 1–20 scale (1 lowest). Excludes current physical condition, age, and architectural style. Also per building at buildingInformation.buildings[].characteristics.quality.
Physical condition — the normalized state of repair of the improvements on an integer 1–20 scale (1 worst, 20 best). Excludes construction quality, age, and style. A separate field from building.quality: a parcel carries both, and they share only the scale form. Current sources occupy the anchor positions below; intermediate values are reserved for finer-grained sources and compare naturally. Also per building at buildingInformation.buildings[].characteristics.condition.Positions 19 and 20 are reserved headroom above EXCELLENT: the 1–20 range is the scale contract this field shares with building.quality, and no source currently maps a parcel there. Validate against 1–20, and expect the unlabelled positions — both the gaps between anchors and the top two — to fill as finer-grained sources land, under the same append-only guarantee.
Owner-tenure band — an integer band index 1–8; higher bands mean longer tenure. Band boundaries are not published; treat values as ordered buckets, not measurements. Prefer lengthOfResidenceMonths when it is present. The flat shape exposes the same integer under the same name (lengthOfResidenceCode).
Band index for the modeled current loan-to-value estimate — an ordered integer bucket, not a percentage and not an uncertainty spread. Band boundaries are not published. The flat shape exposes the same integer as LTVCurrentEstRange.
Band index for the modeled current owner-equity estimate — an ordered integer bucket over dollar ranges, not a dollar amount. Band boundaries are not published. The flat shape exposes the same integer as equityCurrentEstRange.

​
Flat-shape field names (v2-compatible)

The v2-compatible flat shape carries the same underlying values; the tables above apply under these flat field names.

​
Jurisdiction-issued values

propertyClassification.stateLandUseCode, propertyClassification.countyLandUseCode, and taxInformation.taxDistrictCode are jurisdiction-issued vocabularies carried verbatim, not members of the national code system. No global decode table exists or should be inferred; interpret them within the issuing jurisdiction. zoningInfo.zoningCode is likewise the jurisdiction’s own zoning designation.

​
Self-describing members

Some members carry readable values rather than codes and need no decode table: valuationInformation.exemptions[].exemptionType (Homestead, Senior, Veteran, …), mortgages[].lienPosition (first / second), mortgages[].termUnit (months), mortgages[].assignmentsReleases[].recordType (assignment / release), outbuildingsYardItems[].type, buildingInformation.buildings[].buildingAreas[].areaUnits (SF, LF), and taxInformation.taxStatus (delinquent).