Source & Lineage

Part of the Regrid Parcel Schemas reference. Label definitions, source/standardization value meanings, and live coverage access are on that parent page. ⭐ marks the recommended field for its job; fields marked API Queryable can filter the /parcels/query endpoint (max 4 fields per query).

ll_last_refresh — Last County Refresh Date

Description: This is the date we most recently refreshed the data from the county source. ll_last_refresh is the same for every parcel, as it applies to the county data as a whole. 'll_last_refresh' should be the same value as 'last_refresh' in the 'verse' table file.

Use it for: Date we processed the files and data received for a county

How it's made: Date the data was deployed live, typically within days or at maximum within 3 months of when the data was produced
Units: Date · Valid range: Recent date (within last 5 years) · Example: 2022-01-19
Coverage: See ll_last_refresh_pct in the live Coverage Report CSV.

Also known as: (field aliases: last_refresh, county_refresh_date, source_refresh_date, ingest_date)

reviseddate — Date of Last Revision

Description: The last date of last revision as provided by the county assessor's office if available.

Use it for: When did the county last update this data?

Units: Date · Valid range: Date
Coverage: Many counties don't track when they change values See reviseddate_pct in the live Coverage Report CSV.

Also known as: (field aliases: revised_date, last_revision_date, assessor_revision_date)

sourceurl — Source URL

Description: A county provided url to the county parcel record online

Valid range: Well-formatted URL
Coverage: See sourceurl_pct in the live Coverage Report CSV.

Also known as: (field aliases: source_url, parcel_detail_url, assessor_link, property_card_url)

ll_updated_at — Last Modified

Description: Timestamp of the most recent change of any kind to this row in the table including internal changes to the record, and/or county updates. Use ll_last_refresh instead for the date of the parcel data.

Use it for: Update timestamp for this entire record. Can be used as a cache key.

Do not use it for: Does not identify the attribute changed. Do not use as the date of the parcel data – use ll_last_refresh instead.

How it's made: Updated automatically anytime any attribute is changed for any reason.
Units: Timestamp with time zone · Valid range: Valid timestamp · Example: 2019-06-06 12:45:21.285102-04
Coverage: See ll_updated_at_pct in the live Coverage Report CSV.

Also known as: (field aliases: updated_at, last_modified, modified_timestamp)