> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/import-precision-agriculture-data/machinery-proprietary-formats.md).
# Machinery Proprietary Formats
See supported machinery file formats for importing field operations and agronomic datasets.
To upload files in machinery proprietary formats choose the **Import Data** menu and the **Upload Files** item. Then select **Machinery Formats**.
Keep in mind that there are some restrictions:
* GeoPard supports proprietary machinery formats from John Deere, CNH, Climate, Precision Planting, and IsoXML.
* Among the supported formats: \*.adm, \*.jdl, \*.fdd, \*.fld, \*.fmd, \*.dat, \*.2020, \*.cn1, \*.xml, \*.bin, etc.
[Read more about GeoPard Import & Export data compatibility.](https://geopard.tech/data-compatibility/)
* Max size - 100 MB.
* GeoPard automatically parses the archive into the dedicated Operation Datasets and links them to the related Field boundaries.
Upload Machinery Proprietary Files
1. Select the Farm you want to upload data to. Click **As Applied/As Planted** tab.
2. You can either drag-and-drop single or multiple as-applied datasets to the panel or click **Browse** button and select a dataset from your computer.
3. Click **Upload** button. Then the application will verify that the file meets the requirements and save the data.
Wait for the confirmation dialog to see that the dataset was uploaded successfully:
The parsed datasets will be available in the tree in the associated sections for further interactions.
Yield Dataset parsed from DAT format
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/import-precision-agriculture-data/machinery-proprietary-formats.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
