> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/analytics+/working-with-analytics+/3.-charts.md). # 3. Charts Analytics+ comes packaged with a diverse library of over 100+ chart types that can be applied to visualize varied use cases. * Analytics+ charts are IBCS-compliant and fully customizable with a wide variety of styling, number, and conditional formatting options. * Extensive support is provided for hierarchical datasets, with nested sorted and ranking options and the ability to render a trellis with hierarchical dimensions. * The small multiples mode facilitates the rendering of dimensions in rows, columns, and legends - giving you a multi-dimensional perspective of your data. * Analytics+ supports hybrid trellises that contain a combination of charts, cards, and tables.

Analytics+ chart types

In the next section, we'll see how we can build a dashboard with Analytics+. --- # 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.inforiver.com/analytics+/working-with-analytics+/3.-charts.md?ask=&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.