# How to plot dimensions on a Y-axis

> *All user data presented on this page is made up for example purposes.*


Looker visualizations automatically determine which values to plot on a y-axis
based on what field types are present in a query. For example, if an Explore
that breaks down **Users First Name** and **Users Age** for
the top 10 highest **Orders Count** is visualized as a column chart,
the 10 dimension values for **Users First Name** and **Users Age**
are automatically concatenated and separated by a dash (--) on the x-axis.


What if you want to separate **Users Age** and **Users First Name** so that **Users Age** is
plotted on the y-axis, and **Users First Name** and **Orders Count** appear on the x-axis?


The two following solutions outline how to transform a dimension, such as **Users Age**, into a measure so that it can be visualized on the y-axis:

- [Using a table calculation](https://docs.cloud.google.com/looker/docs/best-practices/how-to-plot-dimensions-on-the-y-axis#using_a_table_calculation) --- Create a one-off solution directly from an Explore without developing LookML.
- [Creating a measure](https://docs.cloud.google.com/looker/docs/best-practices/how-to-plot-dimensions-on-the-y-axis#creating_a_measure_in_lookml) --- Develop LookML to be able to reuse an expression in future Explores without needing to create a table calculation.

<br />

## Using a table calculation


A [table calculation](https://docs.cloud.google.com/looker/docs/table-calculations) is the fastest and easiest way to plot a dimension on the y-axis. A calculation is typically plotted as a dimension if no measures are involved in the expression. You can make a table calculation behave as a measure by including a measure in the calculation's expression. The key is making sure the measure won't affect the value of the original dimension.

To use a table calculation to plot a measure on the y-axis, perform the following steps:

1. If there is no measure in your Explore query, add any measure (such as a count), and then [hide](https://docs.cloud.google.com/looker/docs/creating-visualizations#specifying_lookml_fields_to_include_in_the_visualization) it from the visualization. If there is already a measure in your query that you want to include in the visualization, there's no need to hide it.
2. Next, create a table calculation:
   - For a **numerical field** , the calculation will be as follows:

     <br />

     ```
     ${mydimension} + (0 * ${mymeasure})
     ```
     *The calculation preserves the original dimension value by multiplying the
     measure by 0.*
   - For a **string field** , the calculation will involve two [logical functions,](https://docs.cloud.google.com/looker/docs/functions-and-operators#logical_functions,_operators,_and_constants) `if()` and `is_null()`, instead:

     ```
     if(is_null(${mymeasure}),${string_dimension},${string_dimension})
     ```
     This expression tells Looker to *always* display the value of the string dimension in place of the measure values.
3. Hide the original dimension --- **Users Age** in this case --- from the visualization, since the table calculation --- **Age** measure --- now represents the dimension's values in the visualization.


To distinguish between values in a visualization --- in this example, the **Age** measure table calculation and **Orders Count** measures --- you can use [multiple vis types](https://docs.cloud.google.com/looker/docs/creating-visualizations#including_multiple_visualization_types_on_a_single_chart) in a single chart.


For example, you can visualize **Orders Count** values as a line and **Users Age** values as
a column to distinguish them once **Users Age** is plotted on the y-axis.


## Creating a measure in LookML


If you plan to plot a specific dimension on a y-axis again in the future, a more sustainable option is to create a
[`sum` measure](https://docs.cloud.google.com/looker/docs/reference/param-measure-types#sum) or [`number` measure](https://docs.cloud.google.com/looker/docs/reference/param-measure-types#sum)
in LookML that makes the dimension you want to plot into a measure. Instead of recreating the same table calculation in an Explore multiple times, you can add the field to a query from the field picker.

The measure will look similar to this:

```
    measure: measure_for_age { ## replace with a new name
        description: "Use this age field for displaying age on the y-axis"
        type: number ## or sum
        sql: ${age} ;; ## replace with your dimension
    }
```
> *Adding a [`description`](https://docs.cloud.google.com/looker/docs/reference/param-field-description) to the measure can help users understand the intended use of a field.*


In this case, `measure_for_age` is a `number` type measure, since `number` type measures do not perform any actual aggregation. This means **Measure for Age** will display the same values as **Users Age** because it is a `number` type measure that does not perform any aggregation.


Once you create the measure, include both the dimension *and* the new measure in the Explore query. For this example, include the dimensions **Users First Name** and **Users Age** , and include the measures **Orders Count** and **Users Measure for Age**. Finally, hide the dimension that the measure is based on.


With the **Users Age** dimension hidden from the Explore visualization and [custom visualization settings applied](https://docs.cloud.google.com/looker/docs/best-practices/how-to-plot-dimensions-on-the-y-axis#custom_visualization), the resulting Explore visualization displays the **Users Measure for Age** on the y-axis and **Users First Name** on the x-axis, and the **Orders Count** values as a line.