> 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/dokumentacija-api/diagrami-osnovnih-tokov/4.-nalozi-podatkovne-nize-za-tla-or-kot-aplicirano-or-pridelek.md).

# 4. Naloži podatkovne nize za tla | kot-aplicirano | pridelek

Prikazan diagram vizualno prikazuje postopek nalaganja podatkovnih nizov Zemljišče (Soil), Dejanska aplikacija (AsApplied) in Pridelek (Yield) v sistemu GeoPard.

Nalaganje datotek poteka prek vnaprej podpisanih URL-jev S3 in je razdeljeno na dva ločena koraka: pridobitev podatkov vnaprej podpisanega URL-ja ([Zahteva 1 ali R1](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/55.-nalozi-zip-datoteke-nad-6-mb.md#step1)) in dejansko nalaganje datoteke ([Zahteva 2 ali R2](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/55.-nalozi-zip-datoteke-nad-6-mb.md#step2)). Ta mehanizem povečuje varnost in omogoča nalaganje velikih datotek nad 6 MB.

Naslednja faza vključuje poslušanje GraphQL naročnin, posebej za `VSTAVI` in `SPREMENI` dogodke ([Zahteva 3 ali R3](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/1.-narocnina-pridobi-dogodke.md)). Ti dogodki služijo kot obvestila o statusih obdelave podatkovnega niza.

V primeru napake pri obdelavi ali nepopolne dostave dogodka sistem nudi robustno rešitev za obnovitev statusov obdelave. To je mogoče doseči z uporabo GraphQL poizvedbe z imenom `getPlatformContext` ([Zahteva 4 ali R4](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/83.-poizvedba-zberi-kontekst-platforme.md)).

Na koncu lahko potrošnik GeoPard API pridobi vse podrobnosti naloženega podatkovnega niza, ki vključujejo statistiko atributov, obsežne podrobnosti atributov, URL-je in druge podrobnosti upodabljanja, povezave z uporabljeno mehanizacijo in drugo. To zagotavlja celovit nabor podatkov za popolno razumevanje SoilDatasets ([Zahteva 5 ali R5](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/17.-poizvedba-pridobi-soildatasets.md)), AsAppliedDataset ([Zahteva 5 ali R5](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/59.-poizvedba-pridobi-asapplieddatasets.md)), and YieldDataset ([Zahteva 5 ali R5](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/16.-poizvedba-pridobi-yielddatasets.md)).

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FUnT2OjixydK4bwGvTQMw%2Fimage.png?alt=media&amp;token=28a334ce-4d8d-4b41-90e9-5e0d1a8f804c" alt=""><figcaption><p>Sekvenčni diagram: Naloži podatkovni niz</p></figcaption></figure>


---

# 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/dokumentacija-api/diagrami-osnovnih-tokov/4.-nalozi-podatkovne-nize-za-tla-or-kot-aplicirano-or-pridelek.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.