Land & Field
A regenerative supply network requires a spatial object more precise than a farm address and more meaningful than a cadastral parcel. Agricultural management occurs on actual pieces of land whose boundaries, soils, water systems, crop histories, and ecological relationships determine what production means. The foundational spatial object is therefore the field, refined where necessary into management zones.
The field is not merely where production happens. It is the point at which the Production Graph and the Landscape Graph become one system.
Agricultural Provenance Begins With Land
Modern supply chains are organized to preserve the identity required for commerce. The important objects are supplier, item, grade, lot, transformation, shipment, receiver, and transaction. This structure is necessary, and standards such as GS1 EPCIS and food-traceability frameworks strengthen the ability to follow products through commercial events. Regenerative agriculture adds an upstream requirement: the commercial object must remain resolvable into the biological production context from which it emerged.
The appropriate lineage begins with land and moves through management into commerce:
Land
↓
Landscape
↓
Farm
↓
Field
↓
Management Zone
↓
Production Cycle
↓
Harvest
↓
Production Lot
↓
Food
↓
MarketThe point is not that every downstream participant must see every upstream fact. The point is that the system must not destroy the relationships. Provenance should remain complete even when disclosure is selective.
Regeneration is especially dependent upon historical continuity. Soil cover in one season, a change in tillage two seasons later, the insertion of grazing, a diversified rotation, or a different irrigation strategy gains meaning only against what occurred before. A field therefore needs a biography, not merely a current-state record.
Farm, Parcel, Field, and Management Zone
Keep legal and agricultural boundaries distinct
A legal parcel describes property ownership and cadastral organization. A field describes an operational unit of agricultural management. The two may align, but the model must not assume that they do. One parcel may hold several fields, and one operational farm may manage parcels under different ownership or lease structures.
Allow fields to contain management zones
A field may contain areas managed differently because of soil, drainage, slope, irrigation blocks, habitat restoration, production trials, equipment constraints, or farmer intent. A management zone therefore requires its own identity when differentiated management materially affects production history or evidence.
Preserve temporal geometry
Field geometry changes. A producer may subdivide a field for a rotation, establish a permanent buffer, combine adjacent blocks, or bring a new area into production. Geometry must therefore have effective dates and lineage rather than being overwritten.
Preserve the source of spatial truth
A boundary drawn by a farmer, imported from equipment software, derived from a government dataset, digitized from imagery, or inferred by an algorithm does not have the same provenance. The field record should retain boundary source, date, confidence, and revision history.
Treat exact geometry as permissioned data
Field polygons can reveal commercially sensitive information. The system needs exact geometry for computation, but a buyer, consumer, researcher, or public interface may be authorized to see only a generalized geography or a verified relationship such as membership in a watershed.
The Landscape Graph
watershed
A field belongs to nested surface-water systems. In the United States, the USGS Watershed Boundary Dataset provides a nationally standardized hydrologic-unit hierarchy that can serve as a baseline spatial reference.
Relates to field, catchment, hydrography, downstream-waterbody
groundwater
Surface drainage and groundwater dependency are different relationships. A field can belong to one surface watershed while depending upon a groundwater basin shared with farms outside that watershed.
Relates to field, aquifer, groundwater-basin, well, irrigation-system
soil
Mapped soil information provides contextual knowledge, while direct samples represent observations at a defined place and time. The system should preserve both without pretending they are interchangeable.
Relates to field, map-unit, sample, management-zone
terrain
Elevation and derived terrain influence runoff, drainage, equipment operation, erosion exposure, and water movement. Terrain is therefore part of field context, not merely a cartographic background.
Relates to field, slope, aspect, flow-path, erosion-context
habitat
Regeneration can involve relationships that extend beyond cropped acreage. Riparian areas, wetlands, habitat corridors, and surrounding land cover can affect both ecological risk and opportunity.
Relates to field, riparian-zone, corridor, wetland, neighboring-landscape
climate
The same practice can have different implications under different climatic conditions. Climate and observed weather must therefore remain part of the context in which production outcomes are interpreted.
Relates to field, production-cycle, weather, drought, evapotranspiration
Geospatial Enrichment
01 Establish the field
The producer or an authorized data source establishes a stable field identity and a current polygon. The system records provenance for the geometry rather than assuming every imported boundary is authoritative.
02 Resolve nested geography
The polygon is intersected with watersheds, subwatersheds, soils, groundwater units, climate layers, and other authoritative geographies. These relationships become part of the Landscape Graph.
03 Derive terrain and hydrology
Elevation data can be used to derive slope, aspect, flow accumulation, drainage pathways, and topographic position. Where additional hydrological information is available, the system can move beyond simple polygon membership toward downstream connectivity.
04 Attach observations
Soil samples, sensor readings, field photographs, agronomist observations, remote-sensing assets, and other measurements are attached to explicit locations and times.
05 Version the place
When field geometry or management boundaries change, the new representation becomes a version with lineage to the prior state. Historical production remains attached to the spatial representation valid when it occurred.
The Field Is the Join
The field matters because it belongs to both ecology and commerce at the same time. Above it sit soils, watersheds, aquifers, terrain, climate, habitat, and hydrological relationships. Below it sit management zones, production cycles, practice events, harvest lots, products, shipments, contracts, and buyers. A system that preserves only one side cannot explain regenerative production.
This also changes the meaning of location. In conventional commerce, location often means origin address, facility, or delivery point. In a regenerative network, place itself becomes computational context. A buyer can eventually reason about the landscape dependencies of sourcing because every commercial lot can resolve back to fields.
Reference Data Is Not Observation
Soil maps describe context, not field measurement
USDA NRCS SSURGO provides detailed mapped soil geography and attributes. Those data are valuable for establishing a field's reference context, but they do not replace direct field sampling when a claim depends upon measured soil condition.
Watershed boundaries describe hydrologic organization
USGS Watershed Boundary Dataset boundaries are based on topography and hydrology rather than political or property boundaries. They provide a natural organizing layer for understanding how farms participate in shared water systems.
Elevation enables derived landscape reasoning
USGS 3DEP elevation and lidar resources can support terrain analysis, but derived erosion or flow interpretations remain model outputs whose assumptions and resolution should stay visible.
Remote sensing provides evidence with limits
Satellite and aerial observations can reveal vegetation, cover, phenology, land-cover change, and other signals. They should be stored with acquisition time, spatial resolution, processing method, and model version rather than treated as omniscient verification.
The Spatial Invariant
The network should be able to answer a deceptively simple question for every material production lot: Which land produced this? The answer must resolve to persistent field and management-unit identities that retain their geometry, lineage, landscape relationships, and production history.
Without that invariant, regenerative provenance becomes another collection of supplier assertions. With it, every subsequent layer has a place to attach.