> 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+/19.-analytics/trend-line.md). # Trend line As the name indicates, the primary purpose of trend lines is to visualize and highlight trends within the data. They provide a clear representation of the general direction (upward, downward, or flat) of a dataset over time or across categories. Let's explore the options available in Analytics+ to plot trend lines. #### 1. Type Plot linear, exponential, logarithmic, and polynomial trend lines from the type dropdown.

#### 2. Line Choose from solid, dashed, and dotted line styles. You can set the thickness and color of the trend line.

#### 3. Measure Select the measure to plot the trend line. Trend lines can be plotted based on the variance as well.

#### 4. Display line equation Enable this toggle to view the underlying equation that drives the trend line.

* **Font color:** Set the font color of the underlying equation. * **Rotation**: Rotate the equation clockwise or anti-clockwise * **Offset**: Set the position of the equation with respect to the x-axis and y-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.inforiver.com/analytics+/working-with-analytics+/19.-analytics/trend-line.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.