> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemtipsandtricks/widgets/advanced-charts/radial-bar-chart.md).

# Radial Bar Chart

Radial bar is simply a Bar Chart plotted on a polar coordinate system, rather than on a Cartesian one.

While they look cool, the problem with Radial Bar Charts is that the bar lengths can be misinterpreted. Each bar on the outside gets relatively longer to the last, even if they represent the same value.

{% hint style="info" %}
&#x20;You can find a more in depth explanation about the radial bar on [this ](<https://apexcharts.com/javascript-chart-demos/radialbar-charts/ >)page:[https://apexcharts.com/javascript-chart-demos/radialbar-charts/ ](<https://apexcharts.com/javascript-chart-demos/radialbar-charts/ >)
{% endhint %}

![Radial Bar Chart](https://1449034948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-L_NpOsk0sjotPXNy29Q%2Fuploads%2FmbAiYwf7L8HVmBHvm257%2Fimage.png?alt=media\&token=ba570e61-2e45-4f97-852f-a3deb0a3b2d5)

**Properties of Radial Bar Chart**

<table data-header-hidden><thead><tr><th width="189"></th><th width="150"></th><th width="150"></th><th></th></tr></thead><tbody><tr><td><strong>Property Name</strong></td><td><strong>Data type</strong></td><td><strong>Type</strong></td><td><strong>Description</strong></td></tr><tr><td>Data source</td><td>List</td><td>Data Model</td><td>Datalist where the data is stored.</td></tr><tr><td>Label</td><td>Text</td><td>Expression</td><td>To set the labels of the chart.</td></tr><tr><td>Value</td><td>Number</td><td>Expression</td><td>To set the value of the chart.</td></tr><tr><td>Chart color</td><td>Text</td><td>Expression</td><td>Colors to be used for each series.</td></tr><tr><td>Height</td><td>Text</td><td>Expression</td><td>Can be set to auto, percentage of container or pixels.</td></tr><tr><td>Width</td><td>Text</td><td>Expression</td><td>Can be set to percentage of container or pixels.</td></tr><tr><td>Angle style</td><td>Text</td><td>Dropdown</td><td>Defines the angle style for the radialbar (Full, Half, Half inverse, 3 Quarters).</td></tr><tr><td>Show legend</td><td>Boolean</td><td>Expression</td><td>If true, it will show a legend explaining the data on the chart.</td></tr><tr><td>Legend position</td><td>Text</td><td>Dropdown</td><td>Determines the position of the legend. (Left, right, top, bottom).</td></tr><tr><td>Legend font size</td><td>Number</td><td>Expression</td><td><p>number of the fontsize in px.</p><p> </p><p>default 16px</p></td></tr><tr><td>Legend offset y</td><td>Number</td><td>Expression</td><td><p>Use for more specific positioning of the legend after using legend position.</p><p> </p><p>Sets the top offset for legend container</p><p>in pixels. can use negative or positive and depending on the number it may cause the legend to have clipping issues with the chart. (Default is 0)</p></td></tr><tr><td>Legend offset x</td><td>Number</td><td>Expression</td><td><p>Use for more specific positioning of the legend after using legend position.</p><p> </p><p>Sets the left offset for legend container</p><p>in pixels. can use negative or positive and depending on the number it may cause the legend to have clipping issues with the chart. (default is 0)</p></td></tr><tr><td>Hollow size</td><td>Number</td><td>Expression</td><td>Percentage of the chart that is the hollow section. (Default 30%)</td></tr><tr><td>Data label font size</td><td>Number</td><td>Expression</td><td><p>Defines the fontsize of the labels that appear when hovering a given track.</p><p>may cause clipping if too big.</p><p>number of the fontsize in px.</p><p> </p><p>default 16px</p></td></tr></tbody></table>


---

# 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.wem.io/platform/wemtipsandtricks/widgets/advanced-charts/radial-bar-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.
