---
updatedAt: 2026-08-04T15:22:18.000Z
agentTools:
  projectIndex: https://support.regrid.com/llms.txt
---

# Source & Lineage

*Data provenance, refresh dates, and record timestamps.*

Part of the [Regrid Parcel Schemas](https://support.regrid.com/docs/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

| Schemas            | Type | Source | Standardized | API Queryable |
| ------------------ | ---- | ------ | ------------ | ------------- |
| Premium & Standard | date | Regrid | Yes          | —             |

**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](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: (field aliases: last\_refresh, county\_refresh\_date, source\_refresh\_date, ingest\_date)*

### `reviseddate` — Date of Last Revision

| Schemas            | Type | Source                 | Standardized | API Queryable |
| ------------------ | ---- | ---------------------- | ------------ | ------------- |
| Premium & Standard | date | Authoritative (County) | Yes          | —             |

**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](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: (field aliases: revised\_date, last\_revision\_date, assessor\_revision\_date)*

### `sourceurl` — Source URL

| Schemas            | Type | Source                 | Standardized | API Queryable |
| ------------------ | ---- | ---------------------- | ------------ | ------------- |
| Premium & Standard | text | Authoritative (County) | No           | —             |

**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](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: (field aliases: source\_url, parcel\_detail\_url, assessor\_link, property\_card\_url)*

### `ll_updated_at` — Last Modified

| Schemas            | Type        | Source | Standardized | API Queryable |
| ------------------ | ----------- | ------ | ------------ | ------------- |
| Premium & Standard | timestamptz | Regrid | n/a          | —             |

**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](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: (field aliases: updated\_at, last\_modified, modified\_timestamp)*