> For the complete documentation index, see [llms.txt](https://docs.myjuicebox.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myjuicebox.io/building-reports/story-designer/slices/charts/map.md).

# Map

The map chart displays a [place](/building-reports/story-designer/ingredients/the-ingredient-editor.md#place-column-editor) as a bubble on a map. Optionally, the bubble can be sized and colored by measures. Adding a slice with a map chart (i.e., a map slice) is a good choice when users want to see geographic information.

## Adding a map slice

To add a map slice:

* select **Map** from the chart list

![Select Map from the dropdown](https://872636700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmfYn9Ab4YpIl0ZZFm-%2Fuploads%2F8d4qE4vq9dWkJ0jQy3KN%2Fimage.png?alt=media\&token=9021810e-3948-4642-8cd2-8a07daf2d0b1)

* select the [place column](/building-reports/story-designer/ingredients/the-ingredient-editor.md#place-column-editor) you want to display as a bubble on the map
* select a measure to use for the bubble size (optional)
* select a measure to use for the bubble color (optional)
* select a map style
* add slice text (optional)

![A map slice](https://872636700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmfYn9Ab4YpIl0ZZFm-%2Fuploads%2FWxZK0LGSJgC0TBpsz0t0%2Fimage.png?alt=media\&token=2682222b-f772-4e17-8dd5-8aee78a9ceca)

{% hint style="info" %}
The map slice requires that you have a [place column](/building-reports/story-designer/ingredients/the-ingredient-editor.md#place-column-editor). A place column is a special type of column that has associated latitude and longitude fields.
{% endhint %}

{% embed url="<https://www.loom.com/share/ca34647fa6e646d0a8c90c4d4c28cb12>" %}
Adding a map slice
{% endembed %}

## Using a map slice

You can hover over a map bubble to see details. Selections made in the map slice will filter downstream slices.

### Place column editor

A place column is a special kind of column that has an associated geographic location (i.e., latitude and longitude). A place column is required by the [map](/building-reports/story-designer/slices/charts/map.md) chart, and you create a place column when you add a map chart to your data story.

![Place columns are created when you add a map chart](https://872636700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmfYn9Ab4YpIl0ZZFm-%2Fuploads%2FzZOhRMXnAUiRBlaHrVaH%2Fimage.png?alt=media\&token=dc7aed6d-58e7-463c-b2df-b28fb195f672)

To create a place column, your data will need three fields:

1. A field that represents the name of the geographic location (e.g., city, state, country)
2. A field with the latitude value for each location
3. A field with the longitude value for each location

{% hint style="info" %}
The latitude and longitude fields in your data must be numbers, not strings. In other words, your latitudes should look like `38.8977` rather than `38.8977° N`. Likewise, your longitudes should look like `-77.0365`, rather than `77.0365° W`.
{% 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.myjuicebox.io/building-reports/story-designer/slices/charts/map.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 `build a script that syncs our docs to a CMS` 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.