> 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/api-docs/diagrams-with-basic-flows/4.-upload-soil-or-asapplied-or-yield-datasets.md).
# 4. Upload Soil | AsApplied | Yield Datasets
The given diagram visually details the upload process for Soil, AsApplied, and Yield datasets within the GeoPard system.
The file upload occurs via S3 pre-signed URLs and is divided into two distinct steps: receiving pre-signed URL details ([Request 1 or R1](/geopard-tutorials/api-docs/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md#step1)) and actual file upload ([Request 2 or R2](/geopard-tutorials/api-docs/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md#step2)). This mechanism offers increased security and allows the upload of large files over 6MB.
The next stage involves listening to GraphQL subscriptions, specifically for `INSERT` and `MODIFY` events ([Request 3 or R3](/geopard-tutorials/api-docs/geopard-api-requests-overview/1.-subscription-get-events.md)). These events serve as notifications about the dataset processing statuses.
In the event of a processing failure or incomplete event delivery, the system provides a robust solution to restore the processing statuses. This can be achieved using a GraphQL query named `getPlatformContext` ([Request 4 or R4](/geopard-tutorials/api-docs/geopard-api-requests-overview/83.-query-collect-platform-context.md)).
Finally, the GeoPard API consumer can fetch all details of the uploaded dataset, which include attribute statistics, comprehensive attribute details, URLs and other rendering details, connections to utilized machinery, and others. This ensures a full spectrum of data available for a comprehensive understanding of the SoilDatasets ([Request 5 or R5](/geopard-tutorials/api-docs/geopard-api-requests-overview/17.-query-get-soildatasets.md)), AsAppliedDataset ([Request 5 or R5](/geopard-tutorials/api-docs/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)), and YieldDataset ([Request 5 or R5](/geopard-tutorials/api-docs/geopard-api-requests-overview/16.-query-get-yielddatasets.md)).
Sequence diagram: Upload Dataset
---
# 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/api-docs/diagrams-with-basic-flows/4.-upload-soil-or-asapplied-or-yield-datasets.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.
