> 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/izvoz-prenos/izvoz-zapiskov-s-pregleda-na-terenu-kot-shapefile.md).
# Izvoz zapiskov s pregleda na terenu kot shapefile
Izvozite več točk pregleda ali vzorčenja kot shapefile.
GeoPard omogoča paketni izvoz oglednih zapisov prek uporabniškega vmesnika v formatu shapefile.
### Možnost 1: Izvoz shapefile
Ogledne zapise lahko prenesete iz **Izvoz** v levem meniju: [app.geopard.tech/#/export](http://app.geopard.tech/#/export)\
Prenesena datoteka ZIP vsebuje enega ali več shapefileov, z enim SHP na posamezno ogledno plast.
Datoteka ZIP: shapefile na polje z oglednimi/vzorčnimi točkami
Shapefile je v QGIS videti takole:
GeoPard ogledne točke, prenesene in prikazane v QGIS
### Možnost 2: Kopiranje koordinat ogledne točke iz kontrolnika na zemljevidu
Možnost 2: kopirajte koordinate točke na zemljevidu
### Možnost 3: izvoz prek API-ja
[Izvoz oglednih točk](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/71.-mutacija-ustvari-zip-arhiv-z-notes.md) prek API-ja GeoPard.
---
# 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/izvoz-prenos/izvoz-zapiskov-s-pregleda-na-terenu-kot-shapefile.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.
