> 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/geo-map-visualization.md).

# Geo map visualization

Geo maps show a geographic summary of your data using size and color. This visualization type plots a pin on a map, based on the location attribute you used. You can add a measure to specify the size of the pinpoints, then use the properties panel to change the color of the pinpoints. Double-clicking on a pinpoint drills-down into your data. If your data model has geographic annotations, then the location information will be retrieved by the geoservice automatically. Geo maps are especially useful for retail or sales data.

You must have a [license](https://developers.google.com/maps/terms?hl=en) from Google if you choose to use Google Maps with any Pentaho software.

![Geo map](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-66350cfc4c810879d2605ddf02cb71b8de6eab82%2FAnalyzerVisualizationGeoMap.png?alt=media)

| Property                     | Definition                                                             | Available In          |
| ---------------------------- | ---------------------------------------------------------------------- | --------------------- |
| **Pattern**                  | Lets you choose from **Gradient**, **3 Step**, or **5 Step** patterns. | Geo map visualization |
| **Color**                    | Choose from different mixes of colors for your report.                 | Geo map visualization |
| **Reverse Colors** check box | Reverses the order of colors in the report.                            | Geo map visualization |


---

# 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/geo-map-visualization.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.
