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

# 4. Upload jord-, som udført- og udbyttedatasæt

Diagrammet viser uploadprocessen for jord-, AsApplied- og udbyttedatasæt i GeoPard-systemet.

Filen uploades via forudsignerede S3-URL'er og processen består af to separate trin: modtagelse af oplysninger om den forudsignerede URL ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md#step1)) og selve filuploaden ([Anmodning 2 eller R2](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md#step2)). Denne mekanisme øger sikkerheden og gør det muligt at uploade store filer på over 6 MB.

Næste trin er at lytte efter GraphQL-abonnementer, specifikt efter `INSERT` og `MODIFY` -hændelser ([Anmodning 3 eller R3](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/1.-subscription-get-events.md)). Disse hændelser fungerer som meddelelser om datasættets behandlingsstatus.

Hvis behandlingen mislykkes, eller en hændelse ikke bliver leveret, tilbyder systemet en robust løsning til at gendanne behandlingsstatusserne. Det kan gøres med en GraphQL-forespørgsel med navnet `getPlatformContext` ([Anmodning 4 eller R4](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/83.-query-collect-platform-context.md)).

Til sidst kan GeoPard API-forbrugeren hente alle oplysninger om det uploadede datasæt, herunder attributstatistik, detaljerede attributoplysninger, URL'er og andre oplysninger til gengivelse samt forbindelser til det anvendte maskineri. Dermed er alle data tilgængelige, så SoilDatasets ([Anmodning 5 eller R5](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/17.-query-get-soildatasets.md)), AsAppliedDataset ([Anmodning 5 eller R5](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)) og YieldDataset ([Anmodning 5 eller R5](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/16.-query-get-yielddatasets.md)).

<figure><img src="https://1581835146-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>Sekvensdiagram: Upload af datasæt</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/dnk/api-dokumentation/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.
