> 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="/files/BGR9R5Q7tLZlXam5PbGc" 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 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.infotopics.com/showmemore/features/radar-chart/legend.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.