> 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/data-source-model-editor-cp/edit-multidimensional-data-source-models/assign-geographic-properties.md).

# Assign geographic properties

Analyzer lets you visualize data on a geographic map. For common geography types, such as country, state, city, or postal code, the Data Source Wizard automatically populates geographic parent-dimensions and subsequent child-levels to use in Analyzer.

To refine the use of **Geography Map** visualizations in Analyzer, you can associate custom data fields with a particular geography type. After you identify the fields that represent a geography type, you can use Analyzer to visualize this geographic information on a map.

These steps show you how to assign geographic properties to a level with the User Console.

1. Within the Data Source Model Editor, click the **Analysis** tab.
2. Select each of the geographical levels individually and assign each level a **Geography Type** in the **Properties** pane.

   This classifies the data with the correct geography type.

The geography type is now defined for that level.


---

# 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.pentaho.com/pba/data-source-model-editor-cp/edit-multidimensional-data-source-models/assign-geographic-properties.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.