> 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/diagrams-with-basic-flows/4.-upload-soil-or-asapplied-or-yield-datasets.md).

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

Prikazani diagram vizualno podrobno prikazuje postopek nalaganja naborov podatkov Soil, AsApplied in Yield v sistem GeoPard.

Datoteka se naloži prek vnaprej podpisanih URL-jev S3, postopek pa je razdeljen na dva ločena koraka: pridobitev podrobnosti vnaprej podpisanega URL-ja ([Zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md#step1)) in dejansko nalaganje datoteke ([Zahteva 2 ali R2](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md#step2)). Ta mehanizem zagotavlja večjo varnost in omogoča nalaganje velikih datotek, večjih od 6 MB.

Naslednja faza vključuje spremljanje naročnin GraphQL, zlasti dogodkov `INSERT` in `MODIFY`  ([Zahteva 3 ali R3](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/1.-subscription-get-events.md)). Ti dogodki so obvestila o stanju obdelave nabora podatkov.

V primeru napake pri obdelavi ali nepopolne dostave dogodkov sistem ponuja zanesljivo rešitev za obnovitev stanj obdelave. To lahko storite z uporabo poizvedbe GraphQL z imenom `getPlatformContext` ([Zahteva 4 ali R4](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/83.-query-collect-platform-context.md)).

Nazadnje lahko odjemalec API-ja GeoPard pridobi vse podrobnosti naloženega nabora podatkov, vključno s statistiko atributov, izčrpnimi podrobnostmi o atributih, URL-ji in drugimi podrobnostmi za prikaz, povezavami z uporabljeno mehanizacijo in še več. Tako je na voljo celoten nabor podatkov za celovito razumevanje naborov podatkov SoilDatasets ([Zahteva 5 ali R5](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/17.-query-get-soildatasets.md)), AsAppliedDataset ([Zahteva 5 ali R5](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)) in YieldDataset ([Zahteva 5 ali R5](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/16.-query-get-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>Diagram zaporedja: nalaganje nabora podatkov</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/diagrams-with-basic-flows/4.-upload-soil-or-asapplied-or-yield-datasets.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.
