> 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/line-area-and-dot-charts.md).

# Line, area, and dot charts

Line and area chart visualizations show data on a graph by connecting plotted points with a line. Each point represents a single value in your data. You can drill down in all three chart types by double-clicking on a data point.

A line chart shows just the line connecting the dots on the graph and works well if you have a large amount of data to analyze.

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

An area chart shows an aggregate of your data and helps you spot trends quickly, by showing totals and how they are moving relative to each other.

![Area Chart](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-2d7a03b479fe0b66562cc298ed400e2c377c16aa%2FAnalyzerTimeAxis_AreaChartExample.png?alt=media)

A dot chart displays the distribution of a data set as plotted points on a graph.

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

Optional Properties for Line, Area, and Dot Charts

| Property         | Definition                                                                                                                                             | Available In               |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------- |
| **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. | Line, area, and dot charts |
| **Bullet Style** | Choose the shape that you want to use for your bullets.                                                                                                | Line charts                |
| **Line Width**   | Specify the width lines on your report.                                                                                                                | Line charts                |
| **Trend Type**   | Shows a trend type of none or linear. If you choose linear, you can name your trend line and set the width of it.                                      | Line 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/line-area-and-dot-charts.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.
