> 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/svn/predstavitev-izdelka-spletna-aplikacija/import-precision-agriculture-data/machinery-proprietary-formats.md).

# Lastniški formati strojev

Oglejte si podprte formate datotek strojev za uvoz poljskih operacij in agronomskih naborov podatkov.

Če želite naložiti datoteke v lastniških formatih kmetijske mehanizacije, izberite **Uvozi podatke** in nato meni **Naloži datoteke** ter izberite možnost **Formati kmetijske mehanizacije**.

Upoštevajte naslednje omejitve:

* GeoPard podpira lastniške formate kmetijske mehanizacije proizvajalcev John Deere, CNH, Climate, Precision Planting in IsoXML.
* Med podprtimi formati so: \*.adm, \*.jdl, \*.fdd, \*.fld, \*.fmd, \*.dat, \*.2020, \*.cn1, \*.xml, \*.bin itd.

  [Preberite več o združljivosti podatkov za uvoz in izvoz v GeoPard.](https://geopard.tech/data-compatibility/)
* Največja velikost: 100 MB.
* GeoPard samodejno razčleni arhiv v namenske zbirke podatkov o delovnih opravilih in jih poveže z ustreznimi mejami polj.

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FAyA8wGTgxwgAZsjOhlmz%2Fimage.png?alt=media&amp;token=0aeed3da-5098-404c-a881-2025f690f4bd" alt=""><figcaption><p>Nalaganje lastniških datotek kmetijske mehanizacije</p></figcaption></figure>

1. Izberite kmetijo, v katero želite naložiti podatke. Kliknite zavihek **Dejansko izvedena dela / dejanska setev** .
2. Posamezne zbirke podatkov o dejansko izvedenih delih lahko povlečete in spustite na ploščo, lahko pa kliknete gumb **Prebrskaj** in izberete zbirko podatkov v računalniku.
3. Kliknite gumb **Naloži** . Aplikacija bo nato preverila, ali datoteka izpolnjuje zahteve, in shranila podatke.

Počakajte, da se prikaže potrditveno pogovorno okno, ki potrjuje uspešen prenos nabora podatkov:

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2Fgit-blob-ecd0aabe01c0d22f02191614da9428df953cadff%2Fdocs-img-c883a59613.png?alt=media" alt=""><figcaption></figcaption></figure>

Razčlenjene zbirke podatkov bodo na voljo v drevesnem pogledu v ustreznih razdelkih za nadaljnje delo.

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FbjgnMj0fpETiygfZVAgj%2Fimage.png?alt=media&amp;token=b01b2412-21ed-479a-8ebb-e338656bce44" alt=""><figcaption><p>Zbirka podatkov o pridelku, razčlenjena iz formata DAT</p></figcaption></figure>


---

# 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/svn/predstavitev-izdelka-spletna-aplikacija/import-precision-agriculture-data/machinery-proprietary-formats.md?ask=<question>&goal=<user_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.
