Blazor Treemap

    The Ignite UI for Blazor Treemap chart displays hierarchical (tree-structured) data as a set of nested nodes. Each branch of the tree is given a treemap node, which is then tiled with smaller nodes representing sub-branches. Each node’s rectangle has an area proportional to a specified dimension on the data. Often the nodes are colored to show a separate dimension of the data.

    Blazor Treemap Example

    In the following example, the IgbTreemap demonstrates the 30 largest countries in the world by total area.

    Treemap Recommendations

    Are Blazor Treemaps right for your project?

    When the color and size dimensions are correlated in some way with the tree structure, one can often easily see patterns that would be difficult to spot in other ways. A second advantage of treemaps is that, by construction, they make efficient use of space. As a result, they can legibly display thousands of items on the screen simultaneously.

    • Treemaps are more effective than pie charts and other forms of area charts that often do a poor job of classifying data points and communicating the relative differences of their values.
    • Treemaps are designed for drill down scenarios. You can continuously drill down into the data set that is represented by smaller rectangles for more efficient data analysis.
    • Treemaps are not designed to convey numerical quantities; the intent is to show relative rankings.

    Like any other data visualization, a Treemap chart visualization should be used in specific scenarios. It does not solve the same problem that a visualization like a Bar Chart or a Line Chart would. It is really meant for a more complex, richer data display.

    Treemap Use Cases

    There are several common use cases for choosing a Treemap. When you:

    • Have drill-down hierarchical data (data organized as a tree, with branches and sub-branches).
    • Want to illustrate hierarchies of relative weight and comparative values between categories (branches) and subcategories (sub-branches).
    • Want to display large data sets that need a compact, space-efficient visualization.
    • Want to deliver at-a-glance, quick data analysis without precise values. The relative size of the rectangles help identify patterns and/or outliers very quickly.
    • Want to make efficient use of space. Treemaps can legibly display thousands of items on the screen simultaneously.

    When not to Use a Treemap

    • You are telling a data story that requires precise values
    • You have negative data values
    • You have flat, non-hierarchical data
    • Your data is similar in size

    Treemap Data Structure

    • The data source must be an array or a list of data items
    • The data source must contain at least one data item otherwise the map will not render any nodes.
    • All data items must contain at least one data column (e.g. string) which should be mapped to the LabelMemberPath property.
    • All data items must contain at least one numeric data column which should be mapped using the ValueMemberPath property.
    • To categorize data into organized tiles you can optionally use ParentIdMemberPath and IdMemberPath.

    Blazor Treemap Configuration

    In the following example, the treemap demonstrates the ability of changing it's algorithmic structure by modifying the LayoutType and LayoutOrientation properties.

    Layout Types

    The Treemap chart displays the relative weight of data. It uses a variety of algorithms to help it determine how the layout of its data items should occur:

    • SliceAndDiced - layout algorithm aims to preserve the initial order at the expense of the aspect ratio.
    • Squarified - layout tiling algorithm has a better aspect ratio than the SliceAndDice and keeps a better order than Squarified.
    • Stripped - layout type algorithm obtains the best aspect ratio but the objects are arranged by size.

    The Treemap allows you to choose the algorithm that is best for your requirements, defaulting to use the Squarified method. It also includes the ability to allow you to colorize nodes using two mechanisms:

    • A group-based mechanism that colors items with like values
    • A scale-based mechanism similar to a map choropleth, which maps node colors based on their value.

    Layout Orientation

    LayoutOrientation property enables the user to set the direction in which the nodes of the hierarchy will be expanded.

    Note that the LayoutOrientation property works with the layout types SliceAndDice and Strip.

    • Horizontal – the child nodes are going to be stacked horizontally(SliceAndDice).
    • Vertical – the child nodes are going to be stacked vertically (SliceAndDice).

    Blazor Treemap Styling

    In the following example, the treemap demonstrates the ability of changing the look and feel of the nodes achieved by styling through the NodeStylingScript event.

    Blazor Treemap Highlighting

    In the following example, the treemap demonstrates the ability of node highlighting. There are two options for this feature. Each node can individually brighten, by decreasing its opacity, or cause all other nodes to trigger the same effect. To enable this feature, set HighlightingModeto Brighten or FadeOthers.

    Blazor Treemap Percent based highlighting

    • HighlightedDataSource: Specifies the datasource to read highlighted values from. If null, then highlighted values are read from the ItemsSource property.
    • HighlightedValueMemberPath: Specifies the name of the property in the datasource where the highlighted values are read.
    • HighlightedValueOpacity: Controls the opacity of the normal value behind the highlighted value.
    • HighlightedValuesDisplayMode: Enables or disables highlighted values.
      • Auto: The treemap decides what mode to use.
      • Overlay: The treemap displays highlighted values over top the normal value with a slight opacity applied to the normal value.
      • Hidden: The treemap does not show highlighted values.

    Additional Resources

    You can find more information about related chart types in these topics:

    API References

    The following is a list of API members mentioned in the above sections: