> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/maps/layers/point/heatmap-point-aggregation.md).
# Heatmap point aggregation
Heatmap point aggregation allows you to dynamically display your point data as a heatmap visualization, even when working with large-scale data. This type of visualization is ideal for simplifying complex datasets, identify hotspot patterns and gain insights from your data.
## Visualization
In the Visualization section you can specify the Opacity setting at layer source. Additionally, within the **Advanced visualization options** , you can access **Zoom Visibility** to define the range at which your layer should be visualized.
## Area of influence
The area of influence for heatmap layers defines the radius around each point that contributes to the heatmap. A smaller radius results in a smoother heatmap with lower detail, whereas a larger radius shows more distinct variations. This radius can either be uniform or vary according to a specific property.
## Color
You can style your heatmap choosing the desired palette in the Color section. For more information about color palettes supported in Builder check this [section](/carto-user-manual/maps/layers.md#fill-color).
---
# 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.carto.com/carto-user-manual/maps/layers/point/heatmap-point-aggregation.md?ask=&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.
, you can access **Zoom Visibility** to define the range at which your layer should be visualized.
