Scenario 1 - Yield, Planting and As-Applied Map Data
1.0 Overview
The exchange of geospatial field operation data is a common use case between systems. Historically systems have needed to deploy software from the equipment OEMs to translate proprietary files into a readable object model. Following that translation, each system needed to interpret that object model into its own model for display to the user. It has been unavoidable that each system makes its own unique interpretations of the data (e.g., how to map data at the end of a pass, how to total the values, etc.), and the result is incongruous views of the same data facing the same person looking at two different systems.
ADAPT addresses the issues of disparate maps from the same files by abstracting field data away from the machinery. In ADAPT, the data producer generates the coverage polygons, applies any sensor latencies such as yield flow delays, applies any known sensor calibrations. The result is that every data consumer sees the same view of the data as the data producer intended it be mapped.
1.1 Business Workflow (Sequence)
1.2 Examples
Harvest
Soybean harvest data from a simulated field
- Variables in the Operation map to column indexes in the associated GeoParquet file by Variable.FileDataIndex
- Variables also map to ADAPT Data Type Definitions by definition code.
- There are no section polygons for harvest. The coverage polygon should narrow as appropriate to reflect newly harvested ground.
- There is no reported flow delay or calibration factor. These values must be pre-applied in the values. Similarly, any logged yield on turns or otherwise while the header is up must be allocated to the engaged polygons. Since ADAPT looks at data from the field vs. the machine, there is no concept of a disengaged coverage polygon.
Planting
Corn planting data from a simulated field
- Includes liquid and granular application functions. Each of the three coincident applications is reported as a separate Operation with separate GeoParquet files.
Tillage
An example including timestamps only
Higher Density Data
Corn harvest on a simulated field
- Data is has five points per second vs. 1 point per second on North field data above. The ADAPT standard does not define the frequency data at which data is reported.
Left/Right Planting
“Left/Right” or “Split Planter” Corn planting data on a simulated field
- Operation contains seed rate variables mapped to each of two varieties.
- Section polygons report a non-zero rate on active products and zero rates on other products.
- The same pattern may be used on multi-hybrid planting or other applications where product varies by individual row.