> For the complete documentation index, see [llms.txt](https://www.xrdev.app/mixed-reality-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.xrdev.app/mixed-reality-docs/lessons/lesson-5/project/what-is-clustering-map-pins-means.md).

# How to cluster map pins for larger data-sets?

An advantage to using the **MapPinLayer** is that it **supports clustering**. If a **ClusterMapPin prefab** is specified on the layer, MapPins will be **clustered automatically.** When MapPins are clustered, the ClusterMapPin is shown in the place of the many MapPins that associate to it.

{% hint style="info" %}
**Clustering** is highly **recommended** for **large data sets** as this will reduce the number of MapPin instances that need to be rendered for zoomed out views.
{% endhint %}

Besides this rendering performance benefit, it is often preferable to cluster MapPins from a **usability** perspective since dense, cluttered views will make it more difficult for the user to interact with individual MapPins because the map pins might **overlap** with each other.

Clusters are **created at every zoom level**, so as the zoom level of the MapRenderer changes, the visible clusters and MapPins may change as well.

![Clustering allows you to show accumulated data points on the map.](https://1227696974-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoMjAI1irMPA8c0ezFQ%2Fuploads%2Fgit-blob-c894dd0c16eee2468a41fd73e81e89d20f250793%2FMtFujiZoom.gif?alt=media)


---

# 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://www.xrdev.app/mixed-reality-docs/lessons/lesson-5/project/what-is-clustering-map-pins-means.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.
