> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/radar-chart/legend.md).

# Legend

To have a legend in your Radar Chart, tick the ‘Show legend’ button. When having a large selection of dimensions, it may be of benefit to using a color legend to display.

#### Legend position

Choose where your legend will be. Left, Right, Top & Bottom. Every Radar Chart could be different, change to give your dashboard the best look.

<figure><img src="https://1632500807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ARtwElTSzdwWxw4t1pi%2Fuploads%2FmNlSbOiBd4CkraGdDmj2%2FRadar-legend.png?alt=media&amp;token=fa751f2b-384f-496a-8a50-958792700dcd" alt="" width="375"><figcaption></figcaption></figure>

#### Number of columns

Decide how many columns the color legend should show in your view. This will help with the look of your Radar Chart.

#### Horizontal shift

Use the slider to adjust the position horizontally of your Legend. Use this to get it in the perfect position.

#### Vertical shift

Use the slider to adjust the position vertically. This could allow you to have more text shown in your view.&#x20;

&#x20;

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/showmemore/features/radar-chart/legend.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.