> 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/uvoz-podatkov-za-natancno-kmetijstvo/lastniski-formati-strojev.md).

# Lastniški formati strojev

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

Za nalaganje datotek v lastniških formatih mehanizacije izberite **Uvozi podatke** meni in **Naloži datoteke** postavko. Nato izberite **Formati mehanizacije**.

Upoštevajte, da veljajo nekatere omejitve:

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

  [Preberite več o združljivosti podatkov GeoPard Import & Export.](https://geopard.tech/data-compatibility/)
* Največja velikost - 100 MB.
* GeoPard samodejno razčleni arhiv v namenski nabor podatkov za operacije in jih poveže z ustreznimi mejami polja.

<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 mehanizacije</p></figcaption></figure>

1. Izberite kmetijo, v katero želite naložiti podatke. Kliknite **Kot izvedeno/kot zasejano** .
2. Na ploščo lahko povlečete in spustite en sam ali več naborov podatkov za izvedene operacije ali kliknete **Prebrskaj** gumb in izberete nabor podatkov iz svojega računalnika.
3. Kliknite **gumb Naloži** gumb. Nato bo aplikacija preverila, ali datoteka izpolnjuje zahteve, in shranila podatke.

Počakajte na potrditveno pogovorno okno, da vidite, da je bil nabor podatkov uspešno naložen:

<figure><img src="https://lh4.googleusercontent.com/xoQ_v-Ze506YEJkMtaG_Hg1rih-yQwCPBpqwHyNMSELmDnSvLmf_YhGOH3wXpTZ6AjpW4uyXXK6JD_A-CIC1kf4awf1Gf_4lsQSvri-VYREeMynsdor4ZMoWWt5bTKVEOfaEQN5U" alt=""><figcaption></figcaption></figure>

Razčlenjeni nabori podatkov bodo na voljo v drevesu 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>Nabor podatkov o pridelku, razčlenjen 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/uvoz-podatkov-za-natancno-kmetijstvo/lastniski-formati-strojev.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.
