Construct or parse an ISO 11783-10 (ISOXML) TASKDATA file for a precision ag task.
domain: isoxml.tools · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Build/parse a TASKDATA folder with the root TASKDATA.XML file plus any binary time-log (TLG) files it references
Confirm which schema generation is in play — 3.3.x is the widely-deployed legacy version, 4.3 adds guidance patterns, product mixtures, and link lists
Model each object (Task, Field/Partfield, Device, Product, Worker, Customer/Farm) once and reference it elsewhere by its ID attribute
Keep planned data (tasks, product allocations, treatment zones, grid maps) separate from recorded/as-applied data (time logs, positions, logged values)
Validate the package against the ISO 11783-10 XSD for the target schema version before sending it to a task controller/display
Known gotchas
Mixing 3.3.x and 4.3-only elements in one file breaks compatibility with older displays — target the lowest schema version your fleet supports
IDs are referenced, not embedded — a broken ID reference can silently drop data on import in some implementations
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?