> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-management/explorations/dimensions/create-a-dimension.md).

# Create a dimension

In order to view our data, we will create a first dimension. In order to do so, click on the "+ " next to contact in the measure section and click on "add a dimension".

<figure><img src="/files/lseteaFXFTlF0tVSEpXl" alt=""><figcaption><p>Creating a dimension</p></figcaption></figure>

### Select an dimension type

When creating a dimension you must select a type. Whaly supports the following type:

* Standard : to create categories (such as name, color, ...)
* Geolocation : to create location dimensions based on two columns, latitude and longitude

### Select the column(s)

Select the columns you need for your dimension

### Give a name and description to your dimension

Finally, you should give a name and a description to your dimension. This is useful to keep your work clean and understandable for the viewers.

Click on save. There you go you have created your dimension.

{% hint style="info" %}
Don't forget that dimensions are like labels, so they work best when the number of values is relatively low (few dozens rather than few hundreds)
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.whaly.io/data-management/explorations/dimensions/create-a-dimension.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.