parcel
The land parcel as the jurisdiction records it: its identifier, and the formatted variants of that identifier the source publishes.
Represents a parcel of land with unique identifiers and formatted representations for property management and legal documentation purposes.
The question it answers
What is this house, physically?
The feature vector, taken from the source of record rather than from a listing agent. Assessor and parcel records are authoritative; listing fields are agent-entered, inconsistent between markets, and absent entirely for a property that was never listed.
Why it matters
The parcel identifier is how a jurisdiction refers to a property in every record it keeps — the tax roll, the deed index, the permit file. Resolving one across those sources is what turns four unrelated documents into one property history.
In practice
Jurisdictions format the same identifier several ways. A county will publish a punctuated form on the assessor page, an unpunctuated form in a bulk file, and a third form in the clerk's index, so the class carries the formatted variants rather than picking one and losing the ability to match the others.
Properties
| Property | Type | Definition |
|---|---|---|
source_http_request | object | HTTP request configuration for retrieving this data. |
request_identifier | string | null | Identifier value that should be substituted into the source HTTP request to retrieve this specific data. |
parcel_identifier | string | Each parcel of land has a unique Parcel ID that distinguishes it from all other parcels within the jurisdiction. |
Provenance and coverage
A record of this class is validated against the same definition whatever jurisdiction it came from, which is what makes two counties comparable without a per-county adapter. A jurisdiction appears below only where a committed configuration serves this class's surface.
- Lee, Florida
- Palm Beach, Florida
- Miami-Dade, Florida
- Orange, Florida
- Santa Clara, California