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

# Treemap

A Treemap data visualization technique is used to display hierarchical data using nested rectangles; the treemap chart is created based on this technique of data visualization.

The treemap chart is used for representing hierarchical data in a tree-like structure. Data, organized as branches and sub-branches, are represented using rectangles, the dimensions and plot colors of which are calculated.

{% hint style="info" %}
You can find a more in depth explanation about the treemap on [this](<https://apexcharts.com/docs/options/plotoptions/treemap/  >) page: [https://apexcharts.com/docs/options/plotoptions/treemap/  ](<https://apexcharts.com/docs/options/plotoptions/treemap/  >)
{% endhint %}

![Tree Map](https://1449034948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-L_NpOsk0sjotPXNy29Q%2Fuploads%2F8qNSbK2mqLzoNdr1f8Nc%2Fimage.png?alt=media\&token=16af2355-fb79-40cc-9666-6de2e40915a4)

**Properties of Tree Map Chart**

| **Property Name** | **Data type** | Type       | **Description**                                                          |
| ----------------- | ------------- | ---------- | ------------------------------------------------------------------------ |
| Data source       | List          | Data Model | Data list source for the widget.                                         |
| Series            | Text          | Expression | This field is used to create different groups from the same data source. |
| Categories        | Text          | Expression | This field is used to create different groups by series values.          |
| Values            | Number        | Expression | The values of the chart.                                                 |
| Chart Title Size  | Text          | Dropdown   | To set the size of the font for the title. (H1, H2, H3, H4, H5).         |
| Chart Title       | Text          | Expression | To set the title of the chart.                                           |
| Height            | Number        | Expression | Can be set to number, percentage of container or pixels.                 |
| Width             | Number        | Expression | Can be set to number, percentage of container or pixels.                 |
| Prefix            | Text          | Expression | Display a prefix for values on tooltip.                                  |
| Postfix           | Text          | Expression | Display a postfix for values on tooltip.                                 |
| Label Decimals    | Number        | Expression | Set number of decimals displayed.                                        |
| Tick Amounts      | Number        | Expression | Number of visual ticks for the scale on the vertical axis.               |


---

# 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/treemap.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.