Land Use & Zoning
How land is used and regulated - from both county sources and standardized classifications.
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).
lbcs_function — Land Use Code: Function ⭐
lbcs_function — Land Use Code: Function ⭐| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | numeric | Regrid | Yes | Yes |
Description: Economic function or type of establishment: agricultural, commercial, industrial. See https://www.planning.org/lbcs/standards/function/
Use it for: A standardized 4-digit LBCS code for the parcel's economic function (e.g. residential, commercial, industrial, agricultural), derived by Regrid from local use and zoning codes. Standardized nationwide, so it is the field to use for comparing or aggregating land use across counties and states. Pair with lbcs_function_desc for the label.
Do not use it for: The physical activity on the parcel (vs. its economic function) - for that use lbcs_activity. lbcs_function holds the numeric code; lbcs_function_desc holds the readable text.
Related fields: lbcs_function_desc, lbcs_activity ⭐, usecode, usedesc, zoning
How it's made: Human and automatic classification
Units: Code · Valid range: See linked docs · Example: 1000,2000,3000 (100% standardized values, see url)
Coverage: See lbcs_function_pct in the live Coverage Report CSV.
Related docs: Standardized Land Use Code Keys
Also known as: land use, standardized land use, property use, land use category, residential commercial industrial, consistent land use nationwide, compare land use across counties (field aliases: LBCS_function_code, function_code)
lbcs_function_desc — Land Use Code Description: Function
lbcs_function_desc — Land Use Code Description: Function| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Regrid | Yes | — |
Description: Description of the LBCS numeric code
Use it for: The human-readable description of the standardized LBCS economic function code (e.g. "Residential"), the text counterpart to lbcs_function. Standardized nationwide, suitable for cross-jurisdiction comparison and reporting.
Related fields: lbcs_function ⭐, lbcs_activity_desc
How it's made: Human and automatic classification
Valid range: See linked docs
Coverage: See lbcs_function_desc_pct in the live Coverage Report CSV.
Related docs: LBCS Function Dimension with Descriptions
Also known as: land use label, land use description, standardized land use name, what is the land used for (field aliases: LBCS_function_description)
lbcs_activity — Land Use Code: Activity ⭐
lbcs_activity — Land Use Code: Activity ⭐| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | numeric | Regrid | Yes | Yes |
Description: Actual use of land: farming, shopping, manufacturing. See https://www.planning.org/lbcs/standards/activity/
Use it for: A standardized 4-digit LBCS code for the activity that physically takes place on the parcel (e.g. farming, shopping, manufacturing), derived by Regrid from local use and zoning codes. Standardized nationwide, so suitable for comparing land use across counties and states. Pair with lbcs_activity_desc for the label.
Do not use it for: Economic function or establishment type - for that use lbcs_function. Example: a parking lot serving a school has a parking-related activity but a school-related function.
Related fields: lbcs_activity_desc, lbcs_function ⭐, usecode, usedesc
How it's made: Human and automatic classification
Units: Code · Valid range: See linked docs · Example: 1000,2000,3000 (100% standardized values, see url)
Coverage: See lbcs_activity_pct in the live Coverage Report CSV.
Related docs: Standardized Land Use Code Keys
Also known as: land use, land activity, what happens on the property, actual use, standardized land use, residential commercial industrial, compare land use across counties (field aliases: LBCS_activity_code, activity_code)
lbcs_activity_desc — Land Use Code Description: Activity
lbcs_activity_desc — Land Use Code Description: Activity| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Regrid | Yes | — |
Description: Description of the LBCS numeric code
Use it for: The human-readable description of the standardized LBCS activity code (the text counterpart to lbcs_activity). Standardized nationwide.
Related fields: lbcs_activity ⭐, lbcs_function_desc
How it's made: Human and automatic classification
Valid range: See linked docs
Coverage: See lbcs_activity_desc_pct in the live Coverage Report CSV.
Related docs: LBCS Activity Dimension with Descriptions
Also known as: land use label, activity description, land use activity name (field aliases: LBCS_activity_description, activity_description)
lbcs_structure — Land Use Code: Structure
lbcs_structure — Land Use Code: Structure| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | numeric | Regrid | Yes | Yes |
Description: Type of structure or building: single-family house, office building, warehouse. See https://www.planning.org/lbcs/standards/structure/
Use it for: A standardized 4-digit LBCS code for the type of structure on the parcel (e.g. single-family house, office building, warehouse), derived by Regrid from local use and zoning codes. Standardized nationwide. Pair with lbcs_structure_desc for the label.
Related fields: lbcs_structure_desc, lbcs_function ⭐, ll_bldg_count ⭐
How it's made: Human and automatic classification
Units: Code · Valid range: See linked docs · Example: 1000,2000,3000 (100% standardized values, see url)
Coverage: See lbcs_structure_pct in the live Coverage Report CSV.
Related docs: Standardized Land Use Code Keys
Also known as: structure type, building type, standardized structure type, single family multifamily office warehouse (field aliases: LBCS_structure_code, structure_code)
lbcs_structure_desc — Land Use Code Description: Structure
lbcs_structure_desc — Land Use Code Description: Structure| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Regrid | Yes | — |
Description: Description of the LBCS numeric code
Use it for: The human-readable description of the standardized LBCS structure code (the text counterpart to lbcs_structure). Standardized nationwide.
Related fields: lbcs_structure
How it's made: Human and automatic classification
Valid range: See linked docs
Coverage: See lbcs_structure_desc_pct in the live Coverage Report CSV.
Related docs: LBCS Structure Dimension with Descriptions
Also known as: structure type name, building type description (field aliases: LBCS_structure_description)
lbcs_site — Land Use Code: Site
lbcs_site — Land Use Code: Site| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | numeric | Regrid | Yes | Yes |
Description: What is on the land. See https://www.planning.org/lbcs/standards/site/
Use it for: A standardized 4-digit LBCS code for the site's development character (e.g. developed vs. vacant land), derived by Regrid from local use and zoning codes. Standardized nationwide. Pair with lbcs_site_desc for the label.
Related fields: lbcs_site_desc, struct, lbcs_function ⭐
How it's made: Human and automatic classification
Units: Code · Valid range: See linked docs · Example: 1000,2000,3000 (100% standardized values, see url)
Coverage: See lbcs_site_pct in the live Coverage Report CSV.
Related docs: Standardized Land Use Code Keys
Also known as: site development, is the land developed, vacant land, developed or undeveloped (field aliases: LBCS_site_code, site_code)
lbcs_site_desc — Land Use Code Description: Site
lbcs_site_desc — Land Use Code Description: Site| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Regrid | Yes | — |
Description: Description of the LBCS numeric code
Use it for: The human-readable description of the standardized LBCS site code (the text counterpart to lbcs_site). Standardized nationwide.
Related fields: lbcs_site
How it's made: Human and automatic classification
Valid range: See linked docs
Coverage: See lbcs_site_desc_pct in the live Coverage Report CSV.
Related docs: LBCS Site Dimension with Descriptions
Also known as: site development description (field aliases: LBCS_site_description)
usedesc — Parcel Use Description
usedesc — Parcel Use Description| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium & Standard | text | Authoritative (County) | No | — |
Description: A human-readable description of the property's use as provided by the county (e.g. "Single Family Residential").
Use it for: Good for local-level detail. Each county writes its own descriptions, so wording and categories are not consistent from place to place.
Do not use it for: Comparing or grouping land use across counties or states - descriptions are not standardized between jurisdictions. For one consistent land use classification that works nationwide, use the standardized LBCS fields (Premium): lbcs_function and lbcs_activity.
Related fields: lbcs_function ⭐, lbcs_activity ⭐, usecode, zoning
Example: Residential
Coverage: Many counties do not provide lookups or human-readable names for their use codes. See usedesc_pct in the live Coverage Report CSV.
Also known as: land use, property use, property type, land use description, what is the property used for, residential or commercial (field aliases: property_class_description, land_use_description, use_description)
usecode — Parcel Use Code
usecode — Parcel Use Code| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium & Standard | text | Authoritative (County) | No | — |
Description: County's own numeric code for property use.
Use it for: Good for local-level detail and for matching a specific county's records. Each county maintains its own coding system, so the same code means different things in different places.
Do not use it for: Comparing or aggregating land use across counties or states - these codes are not standardized between jurisdictions. For one consistent land use classification that works nationwide, use the standardized LBCS fields (Premium): lbcs_function and lbcs_activity.
Related fields: lbcs_function ⭐, lbcs_activity ⭐, usedesc, zoning
Example: 104
Coverage: See usecode_pct in the live Coverage Report CSV.
Also known as: land use, property use, property type, what is the property used for, use code, property classification, residential or commercial (field aliases: property_class_code, land_use_code, use_code, prop_class)
zoning_type — Zoning Type ⭐
zoning_type — Zoning Type ⭐| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Third Party (Zoneomics) | Yes | Yes |
Description: A standardized zoning type
Use it for: High-level categories of zoning. Standardized; use for analysis and comparison across places.
Related fields: zoning_subtype, zoning, lbcs_function ⭐
How it's made: Proprietary steps developed by Zoneomics
Units: Code · Valid range: Residential, Commercial, Industrial, Agriculture, Mixed, Special, Planned, Overlay · Example: Residential
Coverage: See zoning_type_pct in the live Coverage Report CSV.
Related docs: Standardized Zoning
Matched product: Matched Zoning (separate matched dataset available from Regrid)
Also known as: standardized zoning, zoning category, comparable zoning, zoning type, residential commercial industrial zoning (field aliases: zoning_category, generalized_zoning, primary_zoning_type)
zoning_subtype — Zoning Subtype
zoning_subtype — Zoning Subtype| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Third Party (Zoneomics) | Yes | Yes |
Description: A standardized zoning subtype
Use it for: More detailed categories of zoning. Standardized; use for analysis and comparison across places.
Related fields: zoning_type ⭐, zoning
How it's made: Proprietary steps developed by Zoneomics
Units: Code · Valid range: Single Family, Two Family, Multi Family, Mobile Home Park, General Commercial, Core Commercial, Retail Commercial, Neighborhood Commercial, Office, Special Commercial, Agriculture, Mixed Use, Industrial, Light Industrial, Special, Planned, Overlay · Example: Single-family
Coverage: See zoning_subtype_pct in the live Coverage Report CSV.
Related docs: Standardized Zoning
Matched product: Matched Zoning (separate matched dataset available from Regrid)
Also known as: detailed zoning category, zoning subtype, standardized zoning detail (field aliases: zoning_detail, zoning_subcategory, secondary_zoning_type)
zoning — Zoning Code
zoning — Zoning Code| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium & Standard | text | Authoritative (Zoneomics) | No | Yes |
Description: Governing municipality's zoning code
Use it for: The zoning code for the parcel as set by the local jurisdiction (often sourced via Zoneomics). Good for local-level detail. Each jurisdiction defines its own codes, so the same code is not comparable across places.
Do not use it for: Comparing zoning across jurisdictions - codes are local and not standardized. For standardized zoning categories comparable nationwide, use zoning_type and zoning_subtype (Premium). For standardized land use rather than zoning, use the LBCS fields.
Related fields: zoning_type ⭐, zoning_subtype, zoning_description, lbcs_function ⭐
Example: R-1
Coverage: Unincorporated areas often do not have zoning. Houston, Texas does not have zoning. A few counties don't have zoning. See zoning_pct in the live Coverage Report CSV.
Matched product: Matched Zoning (separate matched dataset available from Regrid)
Also known as: zoning, zoning code, how is it zoned, zoning classification, what is it zoned for (field aliases: zoning_code, zoning_district, zone)
zoning_description — Zoning Description
zoning_description — Zoning Description| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium & Standard | text | Authoritative (Zoneomics) | No | — |
Description: Governing municipality's zoning code description
Use it for: A human-readable name for the local zoning code, as defined by the jurisdiction. Good for local-level detail; not consistent across places.
Do not use it for: Comparing zoning across jurisdictions. For standardized, comparable zoning categories use zoning_type and zoning_subtype (Premium).
Related fields: zoning_type ⭐, zoning_subtype, zoning
Example: Residential
Coverage: See zoning_description_pct in the live Coverage Report CSV.
Matched product: Matched Zoning (separate matched dataset available from Regrid)
Also known as: zoning name, zoning description, what does the zoning code mean (field aliases: zoning_district_description, zone_description)
zoning_code_link — Zoning Code Link
zoning_code_link — Zoning Code Link| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | text | Third Party (Zoneomics) | Yes | — |
Description: Direct link to the municipality's zoning code
Use it for: A link to the source municipalities' zoning details which Zoneomics used to extrapolate their standardized zoning fields.
Related fields: zoning_type ⭐, zoning
Valid range: Valid URL · Example: http://mohavecounty-az.elaws.us/code/coor_ptii_sec11
Coverage: See zoning_code_link_pct in the live Coverage Report CSV.
Related docs: Standardized Zoning
Matched product: Matched Zoning (separate matched dataset available from Regrid)
Also known as: zoning code link, municipal zoning source (field aliases: zoning_code_url, zoning_ordinance_url, municode_link)
zoning_id — Zoning Area ID
zoning_id — Zoning Area ID| Schemas | Type | Source | Standardized | API Queryable |
|---|---|---|---|---|
| Premium only | integer | Third Party (Zoneomics) | Yes | Yes |
Description: ID for the zoning area for matching to the full Regrid zoning add-on product
Use it for: Join key to get more details from matched zoning data
Do not use it for: Zoneomics ID, not used by counties or referenced in zoning codes. Joins to zoneomics data
Related fields: zoning_type ⭐, zoning_subtype
Units: Numeric · Example: 5656
Coverage: See zoning_id_pct in the live Coverage Report CSV.
Related docs: Standardized Zoning
Matched product: Matched Zoning (separate matched dataset available from Regrid)
Also known as: zoning join key, zoneomics id (field aliases: zone_id, zoning_area_id, zoning_polygon_id)
Updated about 2 months ago
