D3 Sunburst Tutorial: Hierarchical Values and Radial Partitions

A sunburst maps hierarchy depth to radial layers and partition extent to angular space. D3 can calculate the layout from a properly prepared hierarchy, while the developer defines what each value means. Avoid double-counting parent and child quantities before interpreting the visible segments as proportions.

Here's a popular D3 Sunburst video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use D3 Sunburst Tutorial: Hierarchical Values and Radial Partitions

Frequently Asked Questions

Does nesting alone supply each segment's quantity?

A hierarchy describes relationships, while quantitative values need a defined aggregation. Supply the appropriate value calculation before partitioning instead of expecting parent-child structure to infer the measurement automatically.

Why can parent values be counted twice?

If parent records already summarize their descendants, adding those summaries to descendant values can inflate totals. Define whether values belong to leaves or internal nodes before computing the hierarchy's aggregate amounts.

What does radial depth represent?

It commonly corresponds to hierarchy levels rather than a second independent measurement. Explain the encoding so readers do not assume a deeper ring automatically means a larger quantity than an inner segment.

How should very small arcs be labeled?

Labels need enough room to remain legible. Hide, abbreviate, or reveal details through another supported interaction rather than forcing every long name into a segment too narrow to display it.

Does a zoomed view change the original underlying quantities?

Zooming can change the displayed context and scale while leaving source values intact. Keep that distinction clear so a focused subtree is not mistaken for a new measurement of the entire dataset.