> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/10.2-analytics/pentaho-analyzer-cp/creating-analyzer-reports/visualizations-for-analyzer/radar-chart-analytics-analyzer-visualizations.md).

# Radar chart

A radar chart is a graphical representation used to compare multiple categories across several variables. Unlike traditional charts with lines, radar charts use a series of connected points to form a polygon, creating a visual representation of the data. This type of chart is particularly useful for comparing multiple categories across multiple variables, highlighting relationships between different data points. Radar charts are often used in business and marketing to compare the performance of different products or services across various metrics, such as sales, customer satisfaction, and market share. You can drill down into the data by double-clicking on any data point within the chart. Radar charts are implemented using Apache Echarts and do not support exporting to PDF.

![Radar chart](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-b86a51d096f05a583692941689f93711da55dd1e%2FPAZ%20Radar%20chart.png?alt=media)

Optional Properties for Radar Charts

| Property                  | Definition                                                                                                                                             | Available In |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ |
| **Bullet Style**          | Use this property to choose the shape that you want to use for your bullets.                                                                           | Radar charts |
| **Line Width**            | Use this property to specify the width of lines connecting bullets on your report.                                                                     | Radar charts |
| **Radar Shape**           | Use this property to display the radar in circular or polygonal shape.                                                                                 | Radar charts |
| **Show Areas**            | Use this property to adjust the transparency of the area under the radar chart lines.                                                                  | Radar charts |
| **Show Axis Tick Labels** | Use this property to display axis ticks on the radar chart.                                                                                            | Radar charts |
| **Data Labels**           | Use this property to label the data features of your report and specify where you want them to appear. You can also choose not to display data labels. | Radar charts |


---

# 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.pentaho.com/pba/10.2-analytics/pentaho-analyzer-cp/creating-analyzer-reports/visualizations-for-analyzer/radar-chart-analytics-analyzer-visualizations.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.
