> 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/geo-endpoints-for-spatial-data-access/wms-get-raster-pictures-of-spatial-data-layers/12.-yielddatasetsmap.md).

# 12. YieldDatasetsMap

Every "YieldDataset" consists of objects with prefixes such as `default`, `raw_`, and `processed_` within the `field` -> `yieldDatasets` -> `geoMaps` attribute. The attribute `geoMaps` -> **`url`** is utilized to display maps as a WMS layer. The style carries the `default` prefix offers insight into the locations or distributions of the geometries. On the other hand, styles with the `raw_` prefix represents the original, untouched geometries (as they are), while `processed_` refers to the interpolated rasterized representation, creating a smooth surface.

Among the supported geometries are points and polygons. The type used depends on the specific geometries stored within the uploaded Yield Dataset.

### Yield URL GeoMap sample (for Raw Dry Yield attribute):

{% hint style="info" %}
You don't need to generate a URL, GeoPard has already prepared it for you (read above how to get it from the GraphQL API)
{% endhint %}

{% code overflow="wrap" fullWidth="false" %}

```url
https://api.geopard.tech/geo/map?WIDTH=512&HEIGHT=512&exceptions=application/vnd.ogc.se_inimage&REQUEST=GetMap&SRS=EPSG:3857&BBOX=3200591.760857104,6321371.206203958,3202575.9372663186,6322354.217755303&VERSION=1.1.1&SERVICE=WMS&TRANSPARENT=true&LAYERS=yield_raw_map_view&STYLES=yield_raw_point&VIEWPARAMS=uuid:339d9f27-c79a-4b7a-ae3e-38e50f3e8b95;attribute:VRYIELDMAS;total:45261&env=v1:3.427;v2:6.637;v3:9.847;v4:12.776;v5:15.705&FORMAT=image/png&
```

{% endcode %}

{% hint style="info" %}
Points and polygons are supported as input data.
{% endhint %}

{% hint style="info" %}
"YieldDataset" has to be uploaded in advance. 
{% endhint %}

<figure><img src="https://lh5.googleusercontent.com/tst2_Da84NX8KuYoGuibLagVU-R_f1IlD6qRoejQblOpY05PCPwpUy93eKskaxuwjuoUzoCQg3C6WiS0-bNeHQ562UdksIsQvsOcRp8Xr5w0zARoS1oxvgSaGEcnEz4QAhKEU0vA4maLkPPFNeX3qQ" alt=""><figcaption><p><em>Raw yield volume attribute as polygons (default view)</em></p></figcaption></figure>

<figure><img src="https://lh3.googleusercontent.com/WBCud2rGye_1uB6xctlFKBsfXaqKEgM2H8ro5mdMsn_P8hrfzMVTEdydBM-FIh9q3332LMHk1pOpoeNclsVKTqf8uQ-ccHW9ChbpSOXcgHKZ1AalLJYAf7LMkbVrrFCRkuIwVrKh3QcRJcJ9aV1FWQ" alt=""><figcaption><p><em>Raw yield volume attribute as points (Raw)</em></p></figcaption></figure>

<figure><img src="https://lh6.googleusercontent.com/NvPkyHraSDSSWSumJ7YY-fGk3w2NkWkQEQ6ONidfT1eFVOY4ttYaJRVjy-pxaOPzI3Xla8owdAg8rKb7DeCxt9Wb6oZ-vKpO4pyngtZY__8tWsLoclKxIoyGteXFinh4iRuaJ2sZt4P2nl6WB4Tv7g" alt=""><figcaption><p><em>Processed yield volume attribute as polygons (Processed)</em></p></figcaption></figure>

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geopard.tech/geopard-tutorials/api-docs/geo-endpoints-for-spatial-data-access/wms-get-raster-pictures-of-spatial-data-layers/12.-yielddatasetsmap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.