|
| 1 | +--- |
| 2 | +title: Path Layer in an Azure Maps Power BI visual |
| 3 | +titleSuffix: Microsoft Azure Maps Power BI visual |
| 4 | +description: This article describes the path layer in an Azure Maps Power BI visual. |
| 5 | +author: deniseatmicrosoft |
| 6 | +ms.author: limingchen |
| 7 | +ms.date: 11/11/2024 |
| 8 | +ms.topic: how-to |
| 9 | +ms.service: azure-maps |
| 10 | +ms.subservice: power-bi-visual |
| 11 | +--- |
| 12 | + |
| 13 | +# The Path Layer in Azure Maps Power BI visual |
| 14 | + |
| 15 | +The Path Layer feature in the Azure Maps Power BI Visual enables the visualization of connections between multiple geographic points. |
| 16 | + |
| 17 | +The Path Layer feature can be used in multiple scenarios, such as: |
| 18 | + |
| 19 | +- **Route Visualization**: Showing vehicle, ship, or flight paths between locations. |
| 20 | +- **Network Analysis**: Examines connections between nodes in a network, like supply chain routes or communication networks. |
| 21 | +- **Movement Tracking**: Monitoring assets or individuals over time and space. |
| 22 | + |
| 23 | +This guide explains how to use this feature effectively. |
| 24 | + |
| 25 | +## Add a Path Layer |
| 26 | + |
| 27 | +This section describes how to add data and configure the Path Layer. Before starting, you need to open your Azure Maps Visual in Power BI. For more information on adding an Azure Maps Visual to your Power BI report, see [Use the Azure Maps Power BI visual]. |
| 28 | + |
| 29 | +| Setting | Description | |
| 30 | +|-------------------|--------------------------------------------| |
| 31 | +| Apply Settings to | Path you want the settings to apply to | |
| 32 | +| Color | The color of the line | |
| 33 | +| Transparency | The transparency of the line | |
| 34 | +| Width | The width of the line | |
| 35 | +| Maximum Zoom | Maximum zoom level the layer is visible at | |
| 36 | +| Minimum Zoom | Minimum zoom level the layer is visible at | |
| 37 | + |
| 38 | +### Add Data to the Path Layer |
| 39 | + |
| 40 | +To draw paths, provide data for "Path ID" and "Point Order": |
| 41 | + |
| 42 | +1. Add the column that best identifies each path to the **Path ID** field. The Path ID is used to identify which line each geospatial data point belongs to. If there are multiple paths, each path requires a unique Path ID. |
| 43 | +1. Add the column that specifies the order of points along the path to the **Point Order** field. The Point Order dictates the sequence of points to form a path. |
| 44 | + |
| 45 | + :::image type="content" source="media/power-bi-visual/path-layer.png" alt-text="A screenshot showing the path layer properties."::: |
| 46 | + |
| 47 | +### Configure a Path Layer |
| 48 | + |
| 49 | +After adding your data, you can adjust the Path Layer's color, line width, and opacity. Apply settings by legend or path ID, coloring paths, and locations with the same legend identically. |
| 50 | + |
| 51 | +After adding your data, you can configure the Path Layer according to your requirements. The style of the paths can be customized by adjusting the line color, width, and opacity. These settings can be applied based on legend or path ID. If a legend is provided, paths and locations associated with the same legend share the same color. |
| 52 | + |
| 53 | +:::image type="content" source="media/power-bi-visual/path-layer-configuration.png" alt-text="A screenshot showing the path layer configuration properties, including line color, transparency, and width as well as minimum and maximum zoom."::: |
| 54 | + |
| 55 | +### Interact with a Path Layer |
| 56 | + |
| 57 | +The Path Layer feature offers several interactive options: |
| 58 | + |
| 59 | +- **Hover and Select**: Hover over a path to select points; clicking on a path selects the nearest point. The selected point will also select other reports by legend, path ID, location, and point order. |
| 60 | +- **Tooltips**: Tooltips show information for the nearest point when hovering over a line. |
| 61 | + |
| 62 | + :::image type="content" source="media/power-bi-visual/path-layer-map.png" alt-text="A screenshot showing a map using the path layer."::: |
| 63 | + |
| 64 | +### Explore and customize a Path Layer |
| 65 | + |
| 66 | +Examine the connections and insights revealed by the Path Layer visualization. Further customize the settings to suit your specific requirements and derive more profound insights from your geospatial data. |
| 67 | + |
| 68 | +#### Legends in a Path Layer |
| 69 | + |
| 70 | +Adding a field to the legend field well creates a higher level of grouping. Consequently, paths and locations associated with the same legend are colored identically. Here's the process: |
| 71 | + |
| 72 | +- **Grouping by Legend**: When a legend is provided, the paths and locations are grouped based on the legend. For instance, if visualizing flight paths with the airline as the legend, all paths and locations associated with the same airline share the same color. Moreover, if there are two rows, one with legend "Contoso" and path ID "A123", and another with legend "MSAirline" and path ID "A123", the Path Layer interprets these as two distinct paths: "Contoso-A123" and "MSAirline-A123". |
| 73 | +- **Styling by Legend**: Configure the style (color, line width, opacity) using the legend to visually differentiate path groups. |
| 74 | +- **Interaction by Legend**: When interacting with the Path Layer, selecting a path or point will also select other reports based on legend, path ID, location, and point order. This ensures all related data points are highlighted together. |
| 75 | + |
| 76 | +#### Handle Origin-Destination Data |
| 77 | + |
| 78 | +To use origin-destination data in the Path Layer, you must first transform it, as Azure Maps Visual doesn't directly support such data. Use the [Unpivot function in Power Query] to do this. Here’s how: |
| 79 | + |
| 80 | +1. **Import Data**: Import your origin-destination data into Power BI. |
| 81 | +1. **Apply Unpivot Function**: Use the following Power Query to transform the data: |
| 82 | + |
| 83 | + ```C# |
| 84 | + let |
| 85 | + // Importing the source. |
| 86 | + Source = … |
| 87 | + // Create "path_id" to set in the "Path ID" field well later in the visual. |
| 88 | + // Since each row represents a line here, we can simply use the row index as path ID |
| 89 | + #"Added Index" = Table.AddIndexColumn(Source, "path_id", 0, 1, Int64.Type), |
| 90 | + // This is the key point of the transformation. |
| 91 | + // We transform the original rows into two: one for the origin and one for the destination. |
| 92 | + #"Unpivoted Other Columns" = Table.UnpivotOtherColumns(#"Added Index", {"path_id"}, "point_order", "city"), |
| 93 | + // We only support timestamp and number for the point order. So, convert the "origin" as 0 and "destination" as 1 |
| 94 | + #"Replaced Values" = Table.ReplaceValue(Table.ReplaceValue(#"Unpivoted Other Columns", "origin", "0", Replacer.ReplaceText, {"point_order"}), "destination", "1", Replacer.ReplaceText, {"point_order"}) |
| 95 | + in |
| 96 | + #"Replaced Values" |
| 97 | + ``` |
| 98 | + |
| 99 | +**Before Transformation** |
| 100 | + |
| 101 | +| origin | destination | |
| 102 | +|-----------|---------------| |
| 103 | +| New York | Los Angeles | |
| 104 | +| Chicago | Houston | |
| 105 | +| Miami | Atlanta | |
| 106 | +| Seattle | Denver | |
| 107 | +| Boston | San Francisco | |
| 108 | + |
| 109 | +**After Transformation** |
| 110 | + |
| 111 | +| path_id | point_order | city | |
| 112 | +|----------|--------------|---------------| |
| 113 | +| 0 | 0 | New York | |
| 114 | +| 0 | 1 | Los Angeles | |
| 115 | +| 1 | 0 | Chicago | |
| 116 | +| 1 | 1 | Houston | |
| 117 | +| 2 | 0 | Miami | |
| 118 | +| 2 | 1 | Atlanta | |
| 119 | +| 3 | 0 | Seattle | |
| 120 | +| 3 | 1 | Denver | |
| 121 | +| 4 | 0 | Boston | |
| 122 | +| 4 | 1 | San Francisco | |
| 123 | + |
| 124 | +## Current limitations |
| 125 | + |
| 126 | +- The path layer is only compatible with specific map data layers, including the Bubble, Reference, Traffic, and Tile layers. |
| 127 | +- The data-bound reference layer is not available when the path layer is enabled. |
| 128 | +- Location hierarchy (drill down) is disabled when a Path ID is provided. |
| 129 | + |
| 130 | +## Conclusion |
| 131 | + |
| 132 | +The Path Layer feature in Azure Maps Visual is a tool for visualizing and analyzing spatial connections. This new capability can be utilized to enhance reports. |
| 133 | + |
| 134 | +[Use the Azure Maps Power BI visual]: power-bi-visual-get-started.md#use-the-azure-maps-power-bi-visual |
| 135 | +[Unpivot function in Power Query]: /power-query/unpivot-column |
0 commit comments