> 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.md).

# Radar chart

A radar chart, also known as a spider chart or web chart, is a graphical method of displaying multivariate data in the form of a two-dimensional chart. It is used to represent three or more quantitative variables on axes that start from the same central point. Each variable is mapped onto an axis, and these axes are evenly spaced, radiating out from the center. The length of each axis is proportional to the value of the corresponding variable. A line is drawn connecting the values for each variable, creating a shape that provides a visual overview of all data points. This type of chart is especially useful for comparing multiple variables and identifying patterns, trends, or outliers in the data. Radar charts are commonly used in fields such as performance analysis, competitive analysis, and customer satisfaction surveys, among others. 

<figure><img src="https://1632500807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ARtwElTSzdwWxw4t1pi%2Fuploads%2F1vdoBtcJGcjboLw8cZdu%2FRadarchart1%20.png?alt=media&amp;token=463db4bf-dced-45e7-b057-cc0698ab1e91" alt=""><figcaption></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.infotopics.com/showmemore/features/radar-chart.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.