Within Leafs unified API, the Machine Data File Translation Service accepts .zip files with proprietary machine data, detects the specific file types, translates the proprietary operation datasets, and returns point-by-point Standard GeoJSON dataset, a summary of the operation and PNG maps of the desired properties associated with operation. With Leafs Machine Data File translation service, your company becomes compatible with all major agriculture machine file types such as John Deere, CaseIH, Climate FieldView, Trimble, etc.

For example, if you wanted to get the date a field was planted, you could access this information from John Deere, Climate Fieldview, AFS connect, or machine data files stored locally in .jdl, .dat, .cn1, .agdata, .isoxml, or other formats. These data sources all store data in different, proprietary ways, have different authentication and hierarchy structures, dramatically different API design, and different abstraction concepts (season-boundaries vs. static field boundary) so your company would need to build and maintain functions to navigate and translate through these different structures. In addition, these data sources will change their APIs and data structures several times per year. With Leaf, your company can connect once to Leafs API and retrieve and send data across providers without needing to worry about the complexity of each individual provider.