> 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/satelitsko-spremljanje/graf-indeksa-razvoja-kulture.md).
# Graf indeksa razvoja kulture
Spremljajte razvoj kulture skozi čas z grafom, ki primerja vrednosti posnetkov med datumi in polji.
GeoPard ponuja grafe razvoja posevkov vse od leta 1988. Ti so samodejno ustvarjeni za vsako njivo, pri čemer uporabljajo samo podatke iz **območij brez oblakov in senc** . Z miško se pomaknite nad točke, da vidite povprečne vrednosti NDVI. Preklapljate lahko med **letnim in mesečnim** pogledi za podrobnejši vpogled.
Ti grafi pomagajo kmetom **določiti optimalen čas žetve**, spremljati posevke na širšem območju ter izboljšati produktivnost in trajnost.
Graf razvoja posevka je na voljo za podatke od leta 1988. Graf se samodejno ustvari za vsako njivo
---
# 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/satelitsko-spremljanje/graf-indeksa-razvoja-kulture.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.
