> 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/agronomija/rx-zemljevidi-za-setev-in-dusik-na-podlagi-rastlinam-dostopne-vode-in-organske-snovi.md).

# Rx zemljevidi za setev in dušik na podlagi rastlinam dostopne vode in organske snovi

Zgradite Rx zemljevide za setev in dušik z variabilnim odmerjanjem z uporabo rastlinam dostopne vode (PAW) in organske snovi (OM), nato pa jih neposredno izvozite v John Deere kot delovni načrt za brezhibno izvedbo na terenu.

{% hint style="success" %}
Izhodišče je imeti nabor podatkov Soil Scanner (ali ekvivalent) s plastmi podatkov za razpoložljivo vodo v tleh (Plant Available Water / uporabna poljska kapaciteta) in organsko snov.
{% endhint %}

{% hint style="warning" %}
Spodnje vaje podpirajo več jezikov. Izberite tistega, ki vam najbolj ustreza, iz ikone jezika <img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FBI5BLx6lztxQTYIHqvsr%2Fimage.png?alt=media&amp;token=0d402011-668e-4a9c-8853-0fb4f56ace99" alt="" data-size="line">.&#x20;
{% endhint %}

## VRA zemljevid setve za koruzo

Spodaj boste našli interaktivni *večjezični* vodnik, ki prikazuje, kako ustvariti VRA zemljevid setve za koruzo na podlagi podatkov o razpoložljivi vodi v tleh (PAW) iz nabora podatkov Soil Scanner.

{% @arcade/embed flowId="TRjxr1Ga4Kxa6WgTeIwx" url="<https://app.arcade.software/share/TRjxr1Ga4Kxa6WgTeIwx>" %}

## VRA zemljevid dušika skupaj z zemljevidom setve

Spodaj boste našli interaktivni *večjezični* vodnik, ki prikazuje, kako ustvariti VRA zemljevid dušika za koruzo na podlagi podatkov o organski snovi (OM) iz nabora podatkov Soil Scanner.

{% hint style="success" %}
"Običajno prva aplikacija dušika zagotovi približno 40 % skupnih potreb po dušiku pri koruzi.
{% endhint %}

{% @arcade/embed flowId="lkHGC7G8cdQkIc9ofMkv" url="<https://app.arcade.software/share/lkHGC7G8cdQkIc9ofMkv>" %}

## Pošljite oba zemljevida v enem delovnem načrtu v John Deere.

Spodaj boste našli interaktivni *večjezični* vodnik, ki prikazuje, kako ustvariti John Deere delovni načrt, ki vsebuje tako zemljevid setve kot zemljevid dušika v eni operaciji.

{% @arcade/embed flowId="JzY7zlwP6dqWxIE5xWay" url="<https://app.arcade.software/share/JzY7zlwP6dqWxIE5xWay>" %}


---

# 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/agronomija/rx-zemljevidi-za-setev-in-dusik-na-podlagi-rastlinam-dostopne-vode-in-organske-snovi.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.