> 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/uvoz-meja-polj.md).
# Uvoz meja polj
Podprti formati datotek in koraki za uvoz meja polj v GeoPard.
Če imate datoteko oblike (.shp) za svoje njive, jih lahko naložite z uporabo **Uvozi podatke** menijske možnosti. Pojdite na **Nalaganje datotek** zavihek.
Upoštevajte, da veljajo nekatere omejitve:
* Podprte so samo datoteke oblike WGS84 (EPSG:4326)
* 5 MB je največja velikost datoteke
* 1236 ha/500 ha je največja površina polja
* Vsaka shapefile datoteka se obravnava kot eno polje
* Oznake bodo ustvarjene iz datoteke .dbf
Naloži mejo polja kot shapefile
1. Izberite kmetijo, v katero želite naložiti
2. Kliknite **Prebrskaj** gumb in izberite datoteko iz svojega računalnika.
3. Kliknite **Naloži** gumb. Nato bo aplikacija preverila, ali datoteka izpolnjuje zahteve, in shranila polje.
\
Počakajte na potrditveno pogovorno okno, da vidite, da je bila meja uspešno naložena:
---
# 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/uvoz-meja-polj.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.
