|
| 1 | +--- |
| 2 | +title: Add a heat map layer to the Azure Maps visual for Power BI | Microsoft Azure Maps |
| 3 | +description: In this article, you will learn how to use the heat map layer in the Microsoft Azure Maps visual for Power BI. |
| 4 | +author: stevemunk |
| 5 | +ms.author: v-munksteve |
| 6 | +ms.date: 10/11/2021 |
| 7 | +ms.topic: how-to |
| 8 | +ms.service: azure-maps |
| 9 | +services: azure-maps |
| 10 | +manager: eriklind |
| 11 | +ms.custom: |
| 12 | +--- |
| 13 | + |
| 14 | +# Add a heat map layer to the Azure Maps visual for Power BI |
| 15 | + |
| 16 | +In this article, you will learn how to add a heat map layer to an Azure Maps visual in Power BI. |
| 17 | + |
| 18 | +:::image type="content" source="media/power-bi-visual/heat-map.png" alt-text="Heat map layer in Azure Maps Visual for Power BI."::: |
| 19 | + |
| 20 | +Heat maps, also known as density maps, are a type of overlay on a map used to represent the density of data using different colors. Heat maps are often used to show the data “hot spots” on a map. Heat maps are a great way to render datasets with large number of points. Displaying a large number of data points on a map will result in a degradation in performance and can cover it with overlapping symbols, making it unusable. Rendering the data as a heat map results not only in better performance, it helps you make better sense of the data by making it easy to see the relative density of each data point. |
| 21 | + |
| 22 | +A heat map is useful when users want to visualize vast comparative data: |
| 23 | + |
| 24 | +- Comparing customer satisfaction rates or shop performance among regions or countries. |
| 25 | +- Measuring the frequency which customers visit shopping malls in different locations. |
| 26 | +- Visualizing vast statistical and geographical data sets. |
| 27 | + |
| 28 | +## Prerequisites |
| 29 | + |
| 30 | +- [Getting started with the Azure Maps visual for Power BI](/power-bi-visual-getting-started.md). |
| 31 | +- [Understanding layers in the Azure Maps visual for Power BI](/power-bi-visual-understanding-layers.md). |
| 32 | + |
| 33 | +## Add the heat map layer |
| 34 | + |
| 35 | +1. In Power BI Desktop, select the Azure map that you created. |
| 36 | +1. In the **Format** pane, switch the **Heat map** toggle to **On**. |
| 37 | + |
| 38 | +Now you can adjust all the Heat map layer settings to suit your report. |
| 39 | + |
| 40 | +## Heat map layer settings |
| 41 | + |
| 42 | +The **Heat map** section of the **Format** pane provides flexibility to customize and design the heat map visualizations to meet your specific requirements. The **Heat map** section enables you to: |
| 43 | + |
| 44 | +- Configure the radius of each data point using either pixels or meters as unit of measurement. |
| 45 | +- Customize the opacity and intensity of the heat map layer. |
| 46 | +- Specify if the value in size field should be used as the weight of each data point. |
| 47 | +- Pick different colors from color pickers. |
| 48 | +- Set the minimum and maximum zoom level for heat map layer to be visible. |
| 49 | +- Decide the heat map layer position amongst different layers, e.g., 3D bar chart layer and bubble layer. |
| 50 | + |
| 51 | +The following table shows the primary settings that are available in the **Heat map** section of the **Format** pane: |
| 52 | + |
| 53 | +| Setting | Description | |
| 54 | +|----------------------|------------------| |
| 55 | +| Radius | The radius of each data point in the heat map.<br /><br />Valid values when Unit = ‘pixels’: 1 - 200. Default: **20**<br />Valid values when Unit = ‘meters’: 1 - 4,000,000| |
| 56 | +| Units | The distance units of the radius. Possible values are:<br /><br />**pixels**. When set to pixels the size of each data point will always be the same, regardless of zoom level.<br />**meters**. When set to meters, the size of the data points will scale based on zoom level, ensuring the radius is spatially accurate.<br /><br /> Default: **pixels** | |
| 57 | +| Opacity | Sets the opacity of the heat map layer. Default: **1**<br/>Value should be a decimal between 0 and 1. | |
| 58 | +| Intensity | The intensity of each heat point. Intensity is a decimal value between 0 and 1, used to specify how "hot" a single data point should be. Default: **0.5** | |
| 59 | +| Use size as weight | A boolean value that determines if the size field value should be used as the weight of each data point. If on, this causes the layer to render as a weighted heat map. Default: **Off** | |
| 60 | +| Gradient |Color pick for users to pick 3 colors for low (0%), center (50%) and high (100%) gradient colors. | |
| 61 | +| Min zoom |Minimum zoom level the layer is visible at. Valid values are 1 to 22. Default: **0** | |
| 62 | +|Max zoom |Maximum zoom level the layer is visible at. Valid values are 1 to 22. Default: **22**| |
| 63 | +|Layer position |Specify the position of the layer relative to other map layers. Valid values include **Above labels**, **Below labels** and **Below roads** | |
| 64 | + |
| 65 | +## Next steps |
| 66 | + |
| 67 | +Change how your data is displayed on the map: |
| 68 | + |
| 69 | +> [!div class="nextstepaction"] |
| 70 | +> [Add a bar chart layer](power-bi-visual-add-bar-chart-layer.md) |
| 71 | +
|
| 72 | +Add more context to the map: |
| 73 | + |
| 74 | +> [!div class="nextstepaction"] |
| 75 | +> [Add a reference layer](power-bi-visual-add-reference-layer.md) |
| 76 | +
|
| 77 | +> [!div class="nextstepaction"] |
| 78 | +> [Add a tile layer](power-bi-visual-add-tile-layer.md) |
| 79 | +
|
| 80 | +> [!div class="nextstepaction"] |
| 81 | +> [Show real-time traffic](power-bi-visual-show-real-time-traffic.md) |
| 82 | +
|
| 83 | +Customize the visual: |
| 84 | + |
| 85 | +> [!div class="nextstepaction"] |
| 86 | +> [Tips and tricks for color formatting in Power BI](/power-bi/visuals/service-tips-and-tricks-for-color-formatting) |
| 87 | +
|
| 88 | +> [!div class="nextstepaction"] |
| 89 | +> [Customize visualization titles, backgrounds, and legends](/power-bi/visuals/power-bi-visualization-customize-title-background-and-legend) |
0 commit comments