> 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/diagrammer-med-grundlaeggende-forlob/4.-upload-jord-som-udfort-og-udbyttedatasaet.md).

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

Det viste diagram viser visuelt uploadprocessen for Soil-, AsApplied- og Yield-datasæt i GeoPard-systemet.

Filuploaden sker via S3 pre-signed URLs og er opdelt i to separate trin: modtagelse af pre-signed URL-oplysninger ([Forespørgsel 1 eller R1](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/55.-upload-zip-filer-over-6-mb.md#step1)) og selve filuploaden ([Forespørgsel 2 eller R2](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/55.-upload-zip-filer-over-6-mb.md#step2)). Denne mekanisme giver øget sikkerhed og tillader upload af store filer over 6MB.

Næste trin omfatter at lytte til GraphQL-subscriptioner, specifikt for `INDSÆT` og `ÆNDR` hændelser ([Forespørgsel 3 eller R3](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/1.-abonnement-hent-haendelser.md)). Disse hændelser fungerer som notifikationer om datasættets behandlingsstatus.

I tilfælde af en behandlingsfejl eller ufuldstændig levering af hændelser tilbyder systemet en robust løsning til at gendanne behandlingsstatusserne. Dette kan opnås ved hjælp af en GraphQL-forespørgsel kaldet `getPlatformContext` ([Forespørgsel 4 eller R4](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/83.-foresporgsel-indsaml-platformkontekst.md)).

Endelig kan GeoPard API-forbrugeren hente alle detaljer om det uploadede datasæt, som inkluderer attributstatistik, omfattende attributdetaljer, URL'er og andre gengivelsesdetaljer, forbindelser til anvendt maskineri og andet. Dette sikrer et fuldt spektrum af data til en omfattende forståelse af SoilDatasets ([Forespørgsel 5 eller R5](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/17.-foresporgsel-hent-soildatasets.md)), AsAppliedDatasæt ([Forespørgsel 5 eller R5](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/59.-foresporgsel-hent-asapplieddatasets.md)), og YieldDataset ([Forespørgsel 5 eller R5](/geopard-tutorials/dnk/api-dokumentation/overblik-over-geopard-api-anmodninger/16.-foresporgsel-hent-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 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/diagrammer-med-grundlaeggende-forlob/4.-upload-jord-som-udfort-og-udbyttedatasaet.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.
