Skip to content

Farm parcels and land units

What this entity is: The abstract pattern of how land is subdivided for management—parcels, paddocks, zones, fields, access roads—and how those units get stable IDs in records and maps. This page does not replace a deed or a farm map; it points to the vault’s minimum standard for naming and authority.

Why it matters: Telemetry, grazing plans, and system of record entries must attach to the same land objects; mixed CRS or ad hoc names cause silent mismatch between dashboards and field truth.

Canonical analysis: Farm spatial model and asset registry standard (IDs, MAP_AUTHORITY_LABEL, device naming).

Product touchpoint: farmOS asset/geometry model—see source-notes on Assets / Logs.

Does not claim: Your parcel boundaries, acreage to the tenth, or conservation program enrollments.

Authority chain (land capability — generic workflow)

  1. Federal soil survey data: Use Web Soil Survey / SSURGO map units for labeling capability classes and limiting factors on your tracts (no substitute for field verification). See Web Soil Survey & 3D Elevation — captures and Execution readiness gap audit §1.
  2. Local buildability / wetness: County septic / SSDS rules and site morph drive structures—not wiki tables. See Tennessee — onsite sewage / septic (captures).
  3. Operating IDs: Once map units and permit classes are known for your sites, attach stable PARCEL-* / PADDOCK-* IDs per Farm spatial model and asset registry standard.

Related