AgGateway.ADAPT.StandardPlugin 1.0.4

Overview

The ADAPT Standard Plugin is a transitional tool to assist the industry in migrating from the ADAPT Framework to the ADAPT Standard. It converts the in-memory ADAPT Framework ApplicationDataModel into serialized data that conforms to the latest version of the ADAPT Standard.

The ADAPT Framework is a .Net plugin toolkit that allows data producers to provide software to data consumers to read proprietary files.

The ADAPT Standard is a replacement that encourages data producers to keep proprietary files in-house and provide consumers with a readable format that requires no software dependencies.

Acknowledgements

AgGateway acknowledges generous support from NIFA (USDA's National Institute of Food and Agriculture) and NAPDC (National Agricultural Producers Data Cooperative).

Usage

See the StandardPluginHarness for a simple example.

Required Input Properties

The ADAPT Framework was largely undocumented. As such, different plugin implementers used data elements in different ways. To convert data, plugin users will need to specify properties based on the source plugin so that data can be interpreted correctly. Below are known settings for various plugins. Data originating in the ADAPT Framework ADM plugin will need to account for the original source of the data.

Source Geometry Position

Some plugins report SpatialRecord.Geometry as the point of the GNSS Receiver, and others report it as the Implement Reference Point. To correctly map the data, this plugin needs to factor this definition to determine which offsets to apply.

GNSS Receiver

• ISOv4Plugin
• Precision Planting

Implement Reference Point

• Climate
• CNH
• John Deere

Source Device Definition

Plugins take different approaches on how to use the DeviceElementUse.Depth concept in the Framework.

DeviceElementHierarchy

• CNH
• ISOv4Plugin
• John Deere
• Precision Planting

Machine0Implement1Section2

• Climate

Data Mappings

ADAPT Standard Version 2.0 released in June 2025. The plugin converts to ADAPT Standard Version 2.0 and intends only to convert to the latest version of the specification at any time.

The following tables summarize plugin implementation where the ADAPT Framework and ADAPT Standard diverge.

Common Properties

Entity Metadata

Devices and Equipment

Most of the Device/Equipment model is omitted from the ADAPT Standard. The ADAPT Standard does not model data from the equipment's point-of-view.

Geometry

Products

Work Orders

Work Records

Omitted Mappings

With decade of production usage behind us, we can look at some of the ADAPT Framework model as well-intentioned theory that never saw usage. Some of this model has not yet or will not be added to the ADAPT Standard.

Not part of ADAPT Standard

• Observations: Observations and Measurements is a likely future extension to the ADAPT Standard
• Irrigation: Not known to be adopted.
• Containers and Packaged Products: Products in ADAPT are models and not instances. Supply chain and traceability are not part of the ADAPT Standard at this time.

No/Limited Use in ADAPT Framework

• Reference Layers: Included in the ADAPT Standard but not known to be used in the Framework
• Plans & Recommendations: While these document types persist in the ADAPT Standard, no known source ADAPT Framework plugin populates these types.
• Sensor Latencies & Calibration Factors: The ADAPT Standard requires that any known calibration/sensor latencies be applied in the data and not reported separately for the data consumer to handle. Many equipment OEM plugins take this approach by default and any calibration data is included in the Framework for information only. Any Framework data that does not handle calibration / flow delay will be technically out of spec for the ADAPT Standard as output by this plugin. To the limited extent such data can be identified and adjusted, this is a known issue.
• Pivot Guidance Patterns Defined as Three Points on a Circle: Pivot guidance patterns are not often seen, and 3-point definitions are rarer. For the plugin to perform such a conversion we would need to add code to reproject coordinates, and this sits open as a known issue.