Agriculture / Precision-Farming DSLs Family Index
type: language-family-index family: agriculture-farming languages_catalogued: 22 tags: [language-reference, family-index, agriculture-farming, isobus, iso-11783, isoxml, adapt, aggateway, fmis]
Agriculture / Precision-Farming — Family Index
Family overview
Agricultural-data DSLs are the textual and structured-schema languages that describe what a tractor, implement, or farm-management system knows — equipment buses, task plans, prescription maps, agronomic samples, field boundaries, crop traits, and the FMIS-to-equipment data exchanges that tie them together. Unlike most language families this one is dominated not by a syntax but by a single physical bus standard: ISO 11783, marketed as ISOBUS, a 14-part ISO standard ratified part-by-part from 2007 through the 2019 revisions, layered on the SAE J1939 CAN-bus and maintained by ISO TC 23 / SC 19 / WG 1 + WG5 with industry stewardship from the Agricultural Industry Electronics Foundation (AEF, founded 2008). Every modern tractor + implement combination ships ISOBUS — virtual-terminal screens (Part 6), task controllers (Part 10), and tractor-implement-management (Part 14 sequence control, Class 3 TIM) all sit on top of it.
The data-exchange layer sitting above the bus is ISOXML (the TASKDATA.XML schema defined by ISO 11783-10), which is what farm-management information systems (FMIS) and equipment task controllers actually trade. ISOXML currently exists in two deployed generations: the long-tail v3.x (3.3.x sub-revisions, still common in installed-base equipment) and the modern v4.x which adds guidance patterns, product mixtures, link lists and richer prescription support; ISO 11783-10:2015 is the current published revision with an AWI (Approved Work Item) replacement in progress. ISOXML, together with AEF Conformance Test certification executed by the three accredited labs (TCI in Germany, REI in Italy, NTTL at University of Nebraska–Lincoln), is the reason cross-brand tractor + implement combinations actually plug-and-play at all.
Sitting alongside ISOBUS is the open data-exchange framework layer from AgGateway: the original ADAPT Framework (2015, an adapter-based C# plugin toolkit for reading proprietary FMIS files), succeeded in June 2024 by the ADAPT Standard 1.0 — a software-dependency-free data schema with standard data types and unit-of-measure abbreviations for B2B agricultural production data. AgGateway also publishes SPADE (Standardized Precision Ag Data Exchange, the interchange model), PAIL (Precision Ag Irrigation Language), and Modus v2 (lab-test data exchange, released 2025). Most FMIS adoption today still goes through ADAPT Framework with a migration path to ADAPT Standard via an AgGateway-developed plugin funded by USDA NIFA.
The remaining mass of the field is proprietary FMIS platforms: John Deere Operations Center (with the developer.deere.com APIs and an organisation-permissions model), Bayer’s Climate FieldView (and the partner program brokered increasingly through Leaf’s unified API), Trimble Ag, AGCO Fuse / Connect, CNH AFS, Topcon X35 Gen2. The cross-platform interop story is the single biggest unsolved problem in precision ag, and it is now under pressure from three directions: (1) the OPC UA Companion Specification for Agriculture push, driven by VDMA inside the broader OPC UA / I4.0 ecosystem; (2) right-to-repair legislation — the US EPA’s February 2026 guidance affirming farmers’ Clean Air Act right to repair, the January 2025 FTC + state-AG antitrust suit against Deere, and the pending federal FARM Act; and (3) AgGateway’s ADAPT Standard 1.0 acting as a vendor-neutral semantic anchor.
In our deep library
None catalogued. Agriculture / precision-farming data formats do not have standalone deep-library notes — they live in this family index and cross-link to siblings.
Cross-reference:
- automotive-onvehicle — sibling family; ISOBUS sits on SAE J1939 which sits on CAN, the same physical bus stack used in passenger / heavy-duty automotive. The diagnostic, parameter-group-number, and address-claim mechanics carry across.
- industrial-automation — sibling; the OPC UA Companion Specification for Agriculture is the agricultural extension of the same OPC UA framework that I4.0 / manufacturing uses, and VDMA is the publishing body for both.
- geospatial — field boundaries are exchanged as Shapefile (legacy installed base) and increasingly GeoJSON (modern FMIS REST APIs). Both are catalogued in geospatial; cross-listed here because field boundaries are the universal cross-platform primitive.
- api-description — ISOXML, ADAPT Standard, BrAPI, and OPC UA Companion Specs are all XML / JSON / schema-driven.
- notation-spec — formal grammars and standards-document conventions apply to the ISO 11783 part series.
- robotics-control and ros2-robotics-config — agricultural-robotics overlap (autonomous tractors, ag-bots), where ROS 2 increasingly sits next to or above ISOBUS.
Tier 3 family table — ISOBUS / ISO 11783 family
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| ISO 11783 / ISOBUS (umbrella, 14 parts) | First parts 2007; Parts 2/3/12 revised 2019; Part 1:2017 | ISO TC 23/SC 19/WG 1 + WG 5, harmonised with SAE J1939 on CAN | Multi-part international standard; physical bus + protocol stack + application layer | Active, foundational; AEF database (isobus.net) actively maintained, recent updates May 2026 | https://www.iso.org/standard/57556.html |
| ISOXML / ISO 11783-10 TASKDATA.XML | 2009 (Part 10 first ed.); 2015 second ed.; v3.x and v4.x schemas in field | ISO TC 23/SC 19, AgGateway-influenced | XML schema for FMIS↔TC task data, prescriptions, time-logs | Active, dominant FMIS↔equipment exchange; AWI replacement for 11783-10:2015 in progress | https://www.iso.org/standard/89951.html |
| DDOP (Device Description Object Pool) | 2007+ (Part 6 / Part 10) | ISO 11783 sub-DSL | Binary-encoded object pool describing terminal screens, device elements, and process-data variables | Active, every ISOBUS implement ships one | https://www.iso.org/standard/57556.html |
| Process Data (PDV / DDI dictionary) | 2007+ (Part 11) | ISO 11783-11; AEF-administered DDI registry at isobus.net | Numeric data dictionary (DDIs) for every measurable agricultural quantity | Active, the DDI list grows with each AEF release | https://www.isobus.net/isobus/ |
| TIM (Tractor Implement Management, Class 3) | ~2013+ | AEF / ISO 11783 Part 9 + Part 7 extensions | Functional class allowing implement to command tractor (speed, hitch, hydraulics) | Active, AEF certified TIM functions ship on flagship implements | https://www.aef-online.org/about-us/projects/tim.html |
| Sequence Control (ISO 11783-14) | 2013 | ISO 11783-14:2013 | Record-edit-playback of commanded operator sequences | Active but lightly adopted | https://www.iso.org/standard/43984.html |
| AEF Conformance Test (ISOBUS certification) | 2014 launch of certified label | AEF; labs TCI (DE), REI (IT), NTTL (US) | Conformance test scheme + public database | Active, the de facto interop gate for tractor/implement OEMs | https://www.aef-online.org/about-us/isobus.html |
| ISOBUS Data Dictionary (online) | 2010s | AEF / isobus.net | Web-queryable DDI registry mirroring 11783-11 | Active, mirror updated May 2026 | https://www.isobus.net/isobus/ |
Tier 3 family table — Open exchange frameworks
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| AgGateway ADAPT Framework | 2015 | AgGateway (US trade association) | C#/.NET plugin toolkit: proprietary FMIS files in, common ADAPT object model out | Maintenance; AgGateway will continue accepting code contributions but new development is on ADAPT Standard | https://adaptframework.org/ |
| AgGateway ADAPT Standard 1.0 | June 2024 | AgGateway | Data schema + standard data types + UoM abbreviations; no software dependency | Active, current; an ADAPT Standard Plugin is under USDA-NIFA-funded development for migration | https://adaptstandard.org/docs/ |
| AgGateway SPADE (Standardized Precision Ag Data Exchange) | mid-2010s | AgGateway working group | Reference data-exchange model underlying ADAPT | Active (as reference model) | https://aggateway.org/GetConnected/ADAPTStandard.aspx |
| AgGateway PAIL (Precision Ag Irrigation Language) | 2010s | AgGateway irrigation work group | XML language for irrigation prescriptions, schedules, system descriptions | Active (niche) | https://aggateway.org/CurrentWork/On-Farm.aspx |
| AgGateway Modus v2 | 2025 | AgGateway | Standard for ag lab-test result interchange (soil, tissue, water) | New (2025), displacing legacy Modus 1 | https://aggateway.org/News/2025PressReleases/AgGateway%E2%80%99sModusv2SetsaNewStandardforAgriculturalLabTestDataExchange.aspx |
| Crop Ontology + BrAPI | 2008 (CO at CGIAR); 2016+ (BrAPI) | Bioversity/Alliance; BrAPI consortium | RDF-style controlled vocabulary for crop traits (4,235 traits / 6,151 variables, 31 species as of 2025) + REST API for plant breeding | Active, FAIR-aligned, integrated with MIAPPE / GA4GH / GeoJSON | https://cropontology.org/ |
| OPC UA Companion Spec for Agriculture | In development | VDMA + OPC Foundation working group | OPC UA information model for ag machines and processes | In development / draft; sits alongside other VDMA 40xxx companion specs published 2025–2026 | https://opcua.vdma.org/en/ |
Tier 3 family table — Proprietary FMIS / OEM
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| John Deere Operations Center API | 2014+ (MyJohnDeere) → Ops Center | Deere & Company | REST API + Files API; org-permission model; OAuth2 | Active, but under FTC + state-AG antitrust suit (Jan 2025) and EPA right-to-repair guidance (Feb 2026) | https://developer.deere.com/ |
| Climate FieldView (Bayer) API + partner program | 2013 (Climate Corp) → Bayer 2018 | Bayer Crop Science | Proprietary FMIS + partner API; Leaf-brokered integration path | Active; major partner-program expansion in 2024–2026 (CLAAS Telematics, RCIS, Ceres AI) | https://climate.com/ |
| Trimble Ag (Trimble Ag Software / Trimble Connect) | 2010s (post-FarmWorks acquisition) | Trimble (now AGCO joint venture as of 2024) | Proprietary FMIS + cloud APIs | Active; in transition under AGCO–Trimble JV | https://agriculture.trimble.com/ |
| CNH Industrial AFS / AFS Connect | ~2000 (Advanced Farming Systems); AFS Connect 2018+ | Case IH + New Holland (CNH Industrial) | Proprietary FMIS + display ecosystem | Active | https://www.caseih.com/en-us/unitedstates/products/precision-farming |
| AGCO Fuse / FuseConnect / FuseSmartFarming | 2011 launch | AGCO Corporation (Fendt, Massey Ferguson, Valtra, Challenger) | Proprietary FMIS, integrated post-2024 with Trimble Ag via JV | Active; consolidating with Trimble Ag | https://www.agcocorp.com/products/fuse.html |
| Topcon X35 Gen2 / Topcon Agriculture Platform (TAP) | 2010s | Topcon Positioning Group | Proprietary display + cloud FMIS | Active | https://www.topconpositioning.com/agriculture |
Tier 3 family table — Spatial / sensor / vocabulary / adjacent
| Format | First appeared | Origin | Type | Status (2026) | URL |
|---|---|---|---|---|---|
| GeoJSON field boundaries | 2008 (GeoJSON RFC 7946:2016) | IETF | JSON geospatial encoding; the modern FMIS-API field-boundary lingua franca | Active, default in REST APIs; see geospatial | https://datatracker.ietf.org/doc/html/rfc7946 |
| Esri Shapefile (.shp) field boundaries | 1993 | Esri | Legacy multi-file vector format; still the FMIS-export default for many platforms | Active legacy, ubiquitous; see geospatial | https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf |
| ISO 19156 OGC O&M (Observations & Measurements) | 2011 (ISO); OGC editions | OGC + ISO TC 211 | Conceptual schema for sensor observations; applied to agricultural sensor data | Active (adjacent; cross-listed with geospatial / industrial) | https://www.ogc.org/publications/standard/om/ |
| FAO WaPOR (Water Productivity Open-access) | 2017 | FAO | Open dataset + API for remote-sensing water-productivity over Africa / Near East | Active | https://wapor.apps.fao.org/ |
| FAO GIEWS (Global Information & Early Warning System) | 1975 | FAO | Crop/food-security monitoring data feeds | Active | https://www.fao.org/giews/ |
| USDA NRCS Conservation Compliance Data Standard | 2010s | USDA Natural Resources Conservation Service | US-specific conservation plan + compliance schemas | Active (US-specific) | https://www.nrcs.usda.gov/ |
| Open Planting Initiative (OPI) | mid-2010s | Industry group | Adjacent open-data initiative for planting operations | Niche / mostly absorbed into ADAPT scope | — |
| CAFFE (Common Agricultural Field Format Exchange) | 2010s | Industry working group | Minor field-boundary + attribute exchange | Niche | — |
| DLG-based field data formats | 2010s | DLG e.V. (German Agricultural Society) | Test-protocol-driven equipment data exchange | Active (DE/EU regional) | https://www.dlg.org/ |
Notable threads
-
ISOBUS + AEF certification is the rare interop success story in heavy equipment. Before AEF Conformance Test (2014), tractor + implement combinations from different OEMs technically spoke ISO 11783 but rarely worked end-to-end without manual configuration; the AEF certified label, executed by three accredited labs (TCI in Wieringerwerf-era Germany, REI in Italy, NTTL at the University of Nebraska’s tractor test laboratory in the US), forced a behaviourally compliant implementation rather than a paper-compliant one. The AEF online database — last refreshed May 2026 — lets farmers and dealers verify before purchase which VT / TC-BAS / TC-GEO / TC-SC / TIM functional classes a given pairing supports. This is the layer that made cross-brand plug-and-play actually work, and it is the closest precedent the industry has for the broader FMIS-to-FMIS interop problem.
-
ADAPT’s adapter-based portability is the only viable bridge over proprietary FMIS lock-in. The ADAPT Framework (2015) chose an explicitly adapter architecture: each FMIS or display vendor writes a plugin that reads its proprietary files and emits the ADAPT common object model; consumers read the common model and don’t care about the source. That bought enough portability for production deployments without forcing OEMs to publish their internal schemas. The ADAPT Standard 1.0 (June 2024) is the second-generation answer — a schema-only specification with no software dependency, intended as a true data-exchange contract rather than a runtime-shaped adapter library. Migration is now the central work item: AgGateway is building an ADAPT Standard Plugin (USDA-NIFA-funded via the National Agricultural Producers Data Cooperative) that lets ADAPT Framework consumers route into the Standard.
-
The proprietary lock-in problem is precision ag’s biggest unsolved issue. John Deere Operations Center, Climate FieldView, Trimble Ag (now under the 2024 AGCO joint venture), CNH AFS, AGCO Fuse, and Topcon TAP each present themselves as the customer’s data home, and each makes it operationally costly to move data sideways. Farmers running mixed fleets — extremely common — accumulate parallel histories in three or four FMIS clouds. The third-party API ecosystem is healthy in pockets (Leaf has become a critical broker for Bayer’s partner expansion; Aegro, ARVA Intelligence, Hutchinsons, Landus, Ceres AI all integrate via Leaf), but no platform exposes write-equivalent parity to its own UI, and agronomic prescriptions in particular tend to round-trip poorly between vendors despite ISOXML being the supposed common ground.
-
OPC UA Companion Specification for Agriculture is the next-gen interop attempt. VDMA (which publishes most OPC UA Companion Specs in the broader I4.0 / mechanical-engineering ecosystem, including the OPC UA Robotics 1.02 release and the 2026-scheduled Powertrain and Battery Production drafts) has a working group developing an agriculture-focused companion specification. The architectural bet is that an OPC UA information model — strongly typed, semantically rich, transport-agnostic — can sit above ISOBUS on the machine side and above FMIS clouds on the IT side, giving a single semantic surface where today there are two disjoint ones. Status as of May 2026 is “in development / draft” rather than published.
-
Right-to-repair pressure is now reshaping the data layer, not just the wrench layer. The US picture in 2025–2026 has shifted fast: the January 2025 FTC + state-AG antitrust suit against Deere & Company alleging restricted access to repair tools and software; the EPA’s February 2026 guidance affirming that the Clean Air Act protects farmers’ right to repair nonroad diesel equipment including emission-control systems and DEF-related repairs; the FARM Act (Freedom for Agricultural Repair and Maintenance, introduced by Reps. Gluesenkamp Perez and Neguse in late 2025) which would mandate availability of documentation, parts, software, and tools; and Farm Bureau MOUs now covering roughly three-quarters of US ag machinery sales. Australia opened consultation in early 2026 to fold farm equipment into its national right-to-repair regime. None of this directly forces FMIS-data portability — but each pushes the equipment-software boundary toward more openness, and the FMIS-data layer is the natural next front.
-
The Crop Ontology + BrAPI stack is the FAIR-data answer at the agronomic-trait layer. Where ISOBUS / ISOXML / ADAPT deal with operations and equipment, the Crop Ontology (CGIAR/Alliance Bioversity-CIAT) and BrAPI (the Breeding API) deal with what the crop actually is — 4,235 traits and 6,151 variables across 31 species as of 2025, with DOIs on Zenodo, and integrations with MIAPPE, GA4GH, GeoJSON, and Planteome. BrAPI is what plant-breeding informatics speaks; CO is the controlled vocabulary that makes the trait names mean the same thing in Bonn, Ibadan, and Hyderabad. This stack is largely disjoint from the ISOBUS world today, but a complete farm-data lifecycle has to bridge them eventually.
Citations
- ISO 11783-1:2017 (General standard, mobile data communication): https://www.iso.org/standard/57556.html
- ISO 11783-10 AWI revision (Task controller / FMIS data interchange): https://www.iso.org/standard/89951.html
- ISO 11783-14:2013 (Sequence control): https://www.iso.org/standard/43984.html
- ISO 11783 — Wikipedia (14-part overview): https://en.wikipedia.org/wiki/ISO_11783
- AEF — ISOBUS conformance and certification: https://www.aef-online.org/about-us/isobus.html
- AEF ISOBUS Data Dictionary (live mirror, refreshed May 2026): https://www.isobus.net/isobus/
- AgGateway ADAPT Framework: https://adaptframework.org/
- AgGateway ADAPT Standard 1.0 (released June 2024): https://aggateway.org/News/2024PressReleases/AgGatewayReleasesAdaptStandardVersion10.aspx
- AgGateway ADAPT Standard docs: https://adaptstandard.org/docs/
- AgGateway Modus v2 (2025 release): https://aggateway.org/News/2025PressReleases/AgGateway%E2%80%99sModusv2SetsaNewStandardforAgriculturalLabTestDataExchange.aspx
- John Deere Developer Portal (Operations Center APIs): https://developer.deere.com/
- Climate FieldView (Bayer): https://climate.com/
- Leaf — unified API for ag-platform integration: https://withleaf.io/
- VDMA OPC UA Companion Specifications portal: https://opcua.vdma.org/en/
- OPC UA Robotics Companion Specification 1.02 (VDMA, 2025): https://www.industrialautomationindia.in/news/vdma-opc-robotics-companion-specification-1-02-digital-production
- Crop Ontology (CGIAR / Alliance Bioversity–CIAT): https://cropontology.org/
- BrAPI (Breeding API): https://brapi.org/
- EPA right-to-repair guidance (February 2026): https://www.epa.gov/newsreleases/epa-advances-farmers-right-repair-their-own-equipment-saving-repair-costs-and
- FTC / state-AG Deere antitrust suit (January 2025) — coverage via PIRG: https://pirg.org/resources/john-deere-and-right-to-repair-over-the-years/
- USDA NRCS (Conservation Compliance): https://www.nrcs.usda.gov/
- FAO WaPOR: https://wapor.apps.fao.org/