> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/work-with-views/maps-view.md).

# Maps view

Display locations on a map based on a Location field.

Use a Maps view to display records on a map based on a Location field. Each record appears as a marker on the map.

<figure><img src="https://3739718108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwCp7NT87JGgngrkhfHT%2Fuploads%2FFONVxbM38TWFrmITxlyL%2FMap%20view.png?alt=media&amp;token=dfeebdb4-4dcb-4258-96f8-7d65cf428c2d" alt=""><figcaption></figcaption></figure>

In **Maps view** you can:

* Click **Fields** and choose:
  * the field for the marker position in **Location field**
  * the text field for the marker title in **Title field**
  * the field for the marker color in **Color field**
* Use [**Filter**](#filter-records-in-a-view) to show only the records you need.

To use a Maps view, first create a **Location** field in the table.

To use record-based colors, first create a **Color** field in the table. Ninox then applies the stored color to each map marker.

You can open records directly from the map by clicking a marker.


---

# 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.ninox.com/builder-hub/visualize-and-organize-your-data/work-with-views/maps-view.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.