ADAPT Standard

Overview

The ADAPT Standard is a data schema, set of standard data type defintions and unit of measure abbeviations designed for the business-to-business transfer of agricultural production data.

It is the successor to the AgGateway ADAPT Framework released in 2015 that served as a software plugin toolkit to read proprietary files. Unlike the earlier toolkit, the ADAPT Standard does not have any software dependencies. It is data only.

Format

ADAPT models data in json, GeoParquet and GeoTiff.

• All dates and times are in UTC as ISO8601 strings.

• Unattributed geometries are Well Known Text in EPSG 4326.

• Attributed spatial data is stored in separate GeoParquet or GeoTiff files.

• All attributes are documented in the schema.

• Json objects and spatial binaries may be exchanged individually between partner systems or sent as collected datasets.

  • When sent as a collected dataset, there is a a single “adapt.json” file and zero or more GeoParquet/GeoTiff files.
    • The adapt.json Root object is split between
      • Catalog: Resource/master data
      • Documents: Transactional data and reference layers.
    • Collected datasets are commonly sent as compressed archives.
  • When used individually, implementers may refer to the objects using Json Pointer syntax. E.g., the Grower object is “https://adaptstandard.org/root/2.0.0#/$defs/Grower"

Principles

Earlier approaches have left the data producer options on how to model any data type. As a result, the data consumer was required to implement conditional logic based on data source. The ADAPT Standard requires any given type of data be modeled in the same way for predictable consumability.

Data producers report values via a common set of Data Type Definitions published with the Standard. All numeric values must be reported in the specific unit of measure defined by the Data Type Definition.

Common Conformance Requirements

• A Work Record defines work done on a Field or CropZone at one time. It is composed of one or more Operations.
  • An Operation may contain as little as the fact that an operation happened on a particular date, to a list of totals, to a comprehensive geospatial record of multiple attributes.
  • Where data can be separated
    • Single pass operations (e.g., planting + liquid application) are two Operations on one Work Record
    • Two combines working in tandem on a Field are two Operations on one Work Record
• GeoParquet polygon files are required for any data reported in field operation Work Records representing the spatial coverage of an implement (beyond a simple boundary geometry stored in WKT on the Operation).
  • Point geometries are not supported for this use case. The data producer must derive the polygons from any source points and implement geometries.
  • GeoTiff may be used for Reference Layers or Work Orders (prescriptions), the source of which is raster data.
• Any known adjustments to source data must be applied by the data producer. There is intentionally no place to report such values to ensure consistent interpretation of the data. E.g.,
  • Sensor calibrations
  • Sensor latencies, commonly harvest flow delays.
• Product mixes must be expressed in mass or volume per mass or volume, not as percentages or rates per area.
  • A mix of product A at 10 gal1ac-1 and product B at 1 gal1ac-1 is A = 10/11 gal1gal-1 and B = 1/11gal1gal-1.
  • This approach both ensures accurate definition of mixes blending dry and liquid components as well as separates the definition of a product from its instance-specific application.

Get Started

See the scenarios for specific use cases and examples.

ADAPT Standard Source Files

• ADAPT Standard Data Schema
• ADAPT Standard Data Type Definitions
• ADAPT Standard Unit Abbreviations