> 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/lva/produkta-apskats-timekla-lietotne/john-deere-operations-center-integration/9.-export-soil-topography-satellite-or-analytics-as-map-layers.md).

# 9. Eksportēt augsnes, topogrāfijas, satelīta vai analītikas datus kā kartes slāņus

GeoPard var eksportēt jebkuru ģeotelpisko slāni uz John Deere Ops Center kā kartes slāni.

#### Ko varat eksportēt

* Pārvaldība **Zonas** (piemēram, sēja, mēslošana, augu aizsardzība)
* **Satelītattēli** (un visi veģetācijas indeksi)
* **Topogrāfija** un atvasinātie slāņi (augstums, slīpums, ekspozīcija)
* **NUE** (slāpekļa izmantošanas efektivitātes) kartes
* **Peļņas** kartes
* Mainīgas normas **Rx** receptes (jebkuram produktam)
* Jebkurš cits GeoPard izveidots rastra vai vektoru slānis

<div data-full-width="true"><figure><img src="https://1923267647-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2F8dKxPmUmV4amrPsHjVS2%2FExport%20GeoPard%20Layer%20to%20John%20Deere%20as%20a%20Map%20Layer.png?alt=media&amp;token=97fa981e-9c01-4755-97ba-c30db4cb27ad" alt=""><figcaption><p>Eksportējiet slāni no GeoPard</p></figcaption></figure> <figure><img src="https://1923267647-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FPiR8QPi144uoawnjNMNO%2FJohn%20Deere%20Ops%20center%20-%20Slope%20-%20via%20GeoPard.png?alt=media&amp;token=6ee97a8c-9132-4434-9452-1e61831b995c" alt=""><figcaption><p>Eksportētais slīpuma slānis ir redzams Ops Center tīmekļa versijā un mobilajā lietotnē</p></figcaption></figure> <figure><img src="https://1923267647-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FGI3nSvBbDJmn26JzGPXr%2FJohn%20Deere%20Ops%20center%20-%20Topography%20-%20via%20GeoPard.png?alt=media&amp;token=49c6ca71-be6e-42e1-920e-077c80ce4df0" alt=""><figcaption><p>Eksportētais augstuma slānis ir redzams John Deere Ops Center tīmekļa versijā un mobilajā lietotnē</p></figcaption></figure></div>

#### Īsi norādījumi

1. Atveriet lauku un atlasiet slāni, ko vēlaties kopīgot.
2. Noklikšķiniet uz **︙** (trīs punktiem) blakus slāņa nosaukumam un izvēlieties **Export → John Deere → Map Layer**.
3. Parasti tas parādās Ops Center 1–2 minūšu laikā.

#### Pārbaudiet Ops Center

1. Piesakieties John Deere Operations Center.
2. Dodieties uz **Field Analyzer → Map Layers**.
3. Jaunais slānis ir redzams sadaļā **Layers**. Ieslēdziet to, lai skatītu kartē.

Tas arī viss — vienkāršs veids, kā GeoPard sniegtās atziņas par lauku parādīt ikvienā John Deere ekrānā saimniecībā.


---

# 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/lva/produkta-apskats-timekla-lietotne/john-deere-operations-center-integration/9.-export-soil-topography-satellite-or-analytics-as-map-layers.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.
