ISOXML is an agricultural data format to create Task Descriptions and record machine data in agricultural machines. ISOXML is standardized in ISO11783-10.
Dev4Agriculture is specialized in agricultural data analysis. We love to make farming software work.
This repository consists of multiple sub-projects. They all belong to isoxml.net but onliy Dev4Agriculture.ISO11783.ISOXML is the one that represents the library itself
This subproject is used to autogenerate the classes from XSD Schema Files. Those are adjusted versions of https://isobus.net (adjusted to fit V3 and V4 in parallel)
Guess what, those are the tests for the ISOXML.net library. You may find interesting examples and also a few test data here.
Another sub project that provides Examples
This is the library itself that will be described in the following chapters
isoxml.net is published as a nuget package here: https://www.nuget.org/packages/Dev4Agriculture.ISO11783.ISOXML
The Datastructures in the ISOXML reflect an ISOXML TaskDataSet that was loaded or created:
- Messages: A list of Warnings and errors that accoured during loading
- Data: The TaskData Structure including Tasks, Devices, etc.
- Grids: The List of Grids (Prescription maps) used in the TaskSet
- TimeLogs: The List of MachineData-Packages provided with the TaskSet
- IdTable: The IdTable collects all IDs from within the TaskSet (e.g. CTR1, TSK-1, etc.)
- LinkList: In case of a Version 4 TaskSet, this is the List of Links between TaskData-Internal Ids (e.g. CTR1) and IDs from the FMIS (e.g. UUIDs).
This is the main Class. It consists of functions to create, load and save ISOXML.
The static Load-Functions are used to Load a TaskDataSet from a storage folder. Its result consists of a Type ISOXML. There are also functions to read ISOXML From a Zip File.
Creates an Empty TaskDataSet
Stores the ISOXML to the given FolderPath
This is the RootElement of any TaskData. It includes all the Coding Data Elements of ISOXML such as Customers, Farmers, Partfields etc.
All these subElements have names beginning with ISO. E.g. ISOPartfield, ISOCustomer, ISOTask
The Tasks include links to TimeLogs as well as a grid if those data are available in the TaskSet.
The TaskDataFile is linked within an ISOXML Object as "Data".
This is an Application, Seeding or Prescription Map
Remark: Each Grid can be of Type1 or Type2
- Type1: Type 1 is an array of bytes; each value in the grid redirects to the corresponding TreatmentZone and its proposed Value
- Type2: Type 2 is an array of 32bit integers. It directly includes values rather than a link to the treatmentZone.
Important: Both Grids should be acessed through the Functions GetValue/SetValue only!
An analysis class to Analyse WorkingSetMasterNames/ClientNames
The WorkingSetMasterName, also known as ClientName is the Unique Identifier for a machine in the ISOXML world.(Actually it's "nearly unique" only :-/)
It can be decoded to read things like
- Type of machine
- Name of Manufacturer (via the ID; see https://www.isobus.net/isobus/manufacturerCode)
This outputs the Hex-encoded name.
This is used to export a WorkingSetMasterName to an ISOTaskDataFile.
The TaskController Emulator can be used to generate machine data just like a TaskController would do it.
You find details on that functionality in the specific Chapter;
Please be aware that the logo assigned to this project is only covered under Apache2 when used with this project. You may not use this logo for any other purpose whatsoever without consent by https://www.dev4Agriculture.de