---
updatedAt: 2026-06-12T13:55:23.000Z
agentTools:
  projectIndex: https://support.regrid.com/llms.txt
---

# Identification

*Parcel IDs and stable keys for lookup and for tracking parcels over time.*

Part of the [Regrid Parcel Schemas](/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).

### `parcelnumb` — Parcel ID

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

Parcel ID/Parcel Number

**Use it for:** The primary parcel ID as provided by the county. We try to identify the best ID provided by the county.

> **Do not use it for:** A unique or stable key - parcel IDs are not unique nationwide (often not even within a county) and can change between updates. To track a specific parcel reliably across data updates, use ll\_uuid.

**Related fields:** `ll_uuid` ⭐, `parcelnumb_no_formatting`, `state_parcelnumb`, `alt_parcelnumb1`
**Example:** 2004940
**Coverage:** Some parcels don't even have a parcelnumb See `parcelnumb_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: parcel number, APN, parcel id, assessor parcel number, PIN (field aliases: parcel\_id, parcel\_number, APN, PIN, AIN, SBL, TMS, TMK)*

### `ll_uuid` — Regrid ID ⭐

| Schemas            | Type | Source | Standardized | API Queryable |
| ------------------ | ---- | ------ | ------------ | ------------- |
| Premium & Standard | uuid | Regrid | Yes          | **Yes**       |

Uniquely identifies a single parcel. A stable parcel id across county data refreshes. It is the value that should be used for tracking individual parcels. It is also the value that should be used for linking to any other data or as a foreign key.

**Use it for:** Universally unique ID for this parcel, persists across updates

**Related fields:** `ll_stable_id`, `ll_stack_uuid`, `parcelnumb`
**How it's made:** Persisted between updates by matching to previous parcels using geometry and attributes for disambiguation
**Valid range:** See linked docs  ·  **Example:** 4cc9eda6-883c-4f38-9a07-b44900a64b16
**Coverage:** See `ll_uuid_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).
**Related docs:** The Regrid ID (ll\_uuid)

*Also known as: unique parcel id, stable id, persistent id, track a parcel over time, parcel identifier (field aliases: parcel\_uuid, regrid\_uuid, stable\_parcel\_id)*

### `parcelnumb_no_formatting` — Parcel ID Without Formatting

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

This is the county-provided 'parcelnumb' schema attribute, but has all non A-Z and 0-9 characters removed. It is intended to make searching and matching on county parcel number, PIN, or APN easier as formatting and spacing can vary. Please note that sometimes formatting and spacing is required to make parcel numbers unique and as a result this attribute is more likely to have duplicate parcel numbers, it should be used as a last resort for matching.

> **Do not use it for:** Whitespace can be meaningful in a parcel ID.

**Related fields:** `parcelnumb`
**How it's made:** We remove non-alphanumeric values, including whitespace.
**Example:** XH0118ROAD00
**Coverage:** See `parcelnumb_no_formatting_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: parcel number without spaces, normalized parcel id (field aliases: apn\_unformatted, parcel\_number\_stripped, parcel\_id\_noformat, apn\_nf)*

### `state_parcelnumb` — State Provided Parcel ID Number

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

Statewide parcel identification number. Collected where available from states that provide a statewide parcel ID.

> **Do not use it for:** Often has a county prefix. Prefix is often the county 2- or 3- digit FIPS code, but might not be.

**Related fields:** `parcelnumb`
**Example:** 22051-0600003127
**Coverage:** See `state_parcelnumb_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: state parcel id, statewide parcel number (field aliases: statewide\_parcel\_id, state\_apn, state\_pin)*

### `alt_parcelnumb1` — First Alternative Parcel ID

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

A county-provided parcel id number that is not considered to be the primary parcel id number used by the county, but is also used as a parcel id in some contexts. These could be previously used parcel numbers, map numbers, online system id numbers, etc. It is provided in this schema attribute for easy, consistent access, but is also duplicated as a county specific custom column to retain its original, county-provided attribute name.

**Example:** RA0580030000
**Coverage:** See `alt_parcelnumb1_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: alternate\_parcel\_id, alt\_apn, legacy\_parcel\_id, prior\_parcel\_id, map\_number)*

### `alt_parcelnumb2` — Second Alternative Parcel ID

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

A county-provided parcel id number that is not considered to be the primary parcel id number used by the county, but is also used as a parcel id in some contexts. These could be previously used parcel numbers, map numbers, online system id numbers, etc. It is provided in this schema attribute for easy, consistent access, but is also duplicated as a county specific custom column to retain its original, county-provided attribute name.

**Example:** RA0580030000
**Coverage:** See `alt_parcelnumb2_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: alternate\_parcel\_id, alt\_apn, legacy\_parcel\_id, prior\_parcel\_id, map\_number)*

### `alt_parcelnumb3` — Third Alternative Parcel ID

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

A county-provided parcel id number that is not considered to be the primary parcel id number used by the county, but is also used as a parcel id in some contexts. These could be previously used parcel numbers, map numbers, online system id numbers, etc. It is provided in this schema attribute for easy, consistent access, but is also duplicated as a county specific custom column to retain its original, county-provided attribute name.

**Example:** RA0580030000
**Coverage:** See `alt_parcelnumb3_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: alternate\_parcel\_id, alt\_apn, legacy\_parcel\_id, prior\_parcel\_id, map\_number)*

### `account_number` — Parcel Account Number

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

The assessor or tax collector's account identification number for a property.

**Example:** 01234X
**Coverage:** See `account_number_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: account\_no, assessment\_account, tax\_account, schedule\_number, folio\_number)*

### `tax_id` — Parcel Tax Identification Number

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

The assessor or tax collector's tax identification number for a property.

**Example:** 87642-2002
**Coverage:** See `tax_id_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: tax\_parcel\_id, tax\_number, parcel\_key, tax\_map\_number, TMS, TMK, SBL)*

### `path` — Parcel Path

| Schemas            | Type | Source | Standardized | API Queryable |
| ------------------ | ---- | ------ | ------------ | ------------- |
| Premium & Standard | text | Regrid | Yes          | **Yes**       |

A Regrid human-readable ID for this parcel. Not guaranteed to be stable between updates. Use ll\_uuid for a permanent and persistent Regrid parcel id.

**Use it for:** Regrid's human-readable identifier for a parcel (a URL-style path). Convenient for reference, but not guaranteed stable between updates.

> **Do not use it for:** A stable key for tracking parcels across updates - use ll\_uuid.

**Related fields:** `ll_uuid` ⭐
**How it's made:** A human-readable path for URLs, calculated from the ogc\_fid, admin0, admin1, and admin2 values (country/state/county/ogc\_fid)
**Valid range:** File-type path with an integer at the end (e.g. /us/mi/washtenaw/123)  ·  **Example:** /us/mi/wayne/detroit/123, /us/fl/456
**Coverage:** See `path_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).

*Also known as: parcel path, parcel url (field aliases: regrid\_path, human\_readable\_id, slug)*

### `ll_stable_id` — Stable ID Status

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

Indicates if the 'll\_uuid' value has changed or was newly assigned during the last refresh from the county. A 'null' indicates a new ll\_uuid and path were generated because the new data was not matched to any existing data during the county data refresh process. If there is any value in this field besides a NULL or empty string, it means we were able to match the refreshed parcel with a parcel in our previous data. The available non-null values are 'parcelnumb', 'address', 'geometry' or 'preserved' and they indicate what attribute we used to match the refreshed parcel to the previous parcel. 'preserved' is a legacy value and just indicates that the ll\_uuid was carried forward from the previous data.

**Use it for:** Flags if this ID is new or was persisted in the last update

**How it's made:** Persisted between updates by matching to previous parcels using geometry and attributes for disambiguation
**Units:** Code  ·  **Valid range:** See linked docs  ·  **Example:** 'parcelnumb', 'address', 'geometry', 'preserved'  or null
**Coverage:** Filled only when an ID was preserved See `ll_stable_id_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).
**Related docs:** The Regrid ID (ll\_uuid)

*Also known as: (field aliases: stable\_id\_status, match\_basis)*

### `ll_stack_uuid` — Parcel Stack UUID

| Schemas            | Type | Source | Standardized | API Queryable |
| ------------------ | ---- | ------ | ------------ | ------------- |
| Premium & Standard | text | Regrid | Yes          | **Yes**       |

A universal unique id for a "stack" of parcels. The same ll\_stack\_uuid is assigned to every parcel in a group of parcels with exactly the same geometry, what we call a "stack". Only parcels that are are part of stack of parcels will have a ll\_stack\_uuid, all other parcels will have a NULL for this attribute. Released on Oct. 17th, 2022

**Use it for:** Is this part of a stack of idendical parcels? (condos)

**Related fields:** `ll_uuid` ⭐
**How it's made:** Detects identical geometry stacks. See documentation for details.
**Valid range:** See linked docs  ·  **Example:** 4cc9eda6-883c-4f38-9a07-b44900a64b16
**Coverage:** Filled only when parcel is part of a stack See `ll_stack_uuid_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).
**Related docs:** Working with Stacked Parcels and Condos

*Also known as: stacked parcels, condos, duplicate geometry parcels (field aliases: stack\_uuid, coincident\_group\_id, geometry\_group\_id)*

### `placekey` — Placekey

| Schemas          | Type | Source                    | Standardized | API Queryable |
| ---------------- | ---- | ------------------------- | ------------ | ------------- |
| **Premium only** | text | Regrid Partner (Placekey) | Yes          | —             |

A unique ID for a geographic place used for linking different geospatial datasets and addresses. See: <https://www.placekey.io/>

> **Do not use it for:** A parcel can overlap multiple placekey H3 hexes; a parcel may have multiple addresses (and therefore multiple placekeys)

**How it's made:** Calculated by Placekey
**Valid range:** Matches Placekey spec  ·  **Example:** 227-223\@5vg-82n-pgk
**Coverage:** See `placekey_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).
**Related docs:** Premium Schema Now Contains Placekey

*Also known as: placekey, place identifier*

### `precisely_id` — Precisely ID

| Schemas          | Type | Source                     | Standardized | API Queryable |
| ---------------- | ---- | -------------------------- | ------------ | ------------- |
| **Premium only** | text | Regrid Partner (Precisely) | Yes          | —             |

PreciselyID represents a point addressable location.  If a location has multiple alias addresses (alias street names, vanity city names, etc), it will receive the same PreciselyID

**Use it for:** ID in the Preciesly dataset. Useful for lookups across products.

**How it's made:** Calculated by Precisely
**Coverage:** See `precisely_id_pct` in the live [Coverage Report CSV](https://docs.google.com/spreadsheets/d/1rvRYv6_ppZlwbmyi2kbzemot6FOEm2EEPdHPyENTQPE/export?format=csv\&gid=1284673582).
**Related docs:** PreciselyID FAQ

*Also known as: precisely id, cross product lookup*

### `ogc_fid` — Object ID

| Schemas            | Type               | Source | Standardized | API Queryable |
| ------------------ | ------------------ | ------ | ------------ | ------------- |
| Premium & Standard | serial primary key | Regrid | Yes          | —             |

object ID - Not unique across counties, not persistant over time, use 'll\_uuid' preferably below.

**Use it for:** A row object ID. Not unique across counties and not stable over time.

> **Do not use it for:** Tracking a parcel over time or as a unique key - ogc\_fid is neither stable across versions nor unique across counties. Use ll\_uuid.

**Related fields:** `ll_uuid` ⭐
**Units:** Numeric
**Coverage:** See `ogc_fid_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: OBJECTID, OGC\_FID, OID, FID)*