TaskData
ISO 11783-10 TaskData exchange. Zip format, ISOXML structure, and use cases
| Property | Value |
|---|---|
| Technical Message Type | iso:11783:-10:taskdata:zip |
| Information Type | TaskData |
| Format | ZIP (binary) |
| Protobuf Schema | None (binary zip format) |
Overview
TaskData is the main format for exchanging agricultural task information through agrirouter. It follows the ISO 11783-10 standard (ISOXML) and is used to move work orders, application maps, as-applied data, and yield maps between farm management systems and machines.
Data Format
A TaskData message contains a zip file holding an ISOXML dataset. The entry point inside the zip is TaskData.xml, which references every other resource in the dataset.
Package the ISOXML dataset into a zip archive and send the raw zip bytes as the request body with Content-Type: application/octet-stream. Do not Base64-encode the payload yourself; agrirouter applies transport encoding internally for chunked message types.
Chunking
The API handles chunking for you. If a TaskData zip exceeds the internal chunk size, the API splits it on the way out and the recipient gets the reassembled file as a single FILE_RECEIVED event. No manual chunking or reassembly on your side.
Use Cases
- Task planning: sending work orders and job definitions from FMIS to machines
- Application maps: variable-rate prescriptions for seeding, fertilizing, or spraying
- As-applied data: actual application records collected during field operations
- Yield maps: harvest data collected by combine harvesters or other machines
ISOXML Structure
The ISOXML dataset in the zip follows the ISO 11783-10 standard. TaskData.xml is the main descriptor and references any additional data files (binary time logs, grid files) in the archive.
For the full specification, refer to the ISO 11783-10 standard documentation.