Part-to-Whole
Voronoi Treemap
Partitions space into irregular polygons whose areas represent values, offering an organic alternative to rectangular treemaps.
GitHub Repositories by Language
Organic proportional layout
View data (8 rows)
| Repos | Language |
|---|---|
| 320 | JavaScript |
| 280 | Python |
| 210 | TypeScript |
| 180 | Java |
| 120 | Go |
| 90 | Rust |
| 75 | C++ |
| 50 | Ruby |
Use a voronoi treemap when…
- When an organic, visually distinct layout is desired over grid treemaps
- Showing proportions within a non-rectangular boundary
Avoid when…
- When precise size comparisons are important (irregular shapes are hard to judge)
- When the audience expects conventional chart types
Data it needs
| Property | Value |
|---|---|
| Min Rows | 4 |
| Min Columns | 2 |
| Column Types | stringnumber |
Visual anatomy
Marks
polygon
Channels
area (value)color (category)
Axes
-
Guiding principles
Consider instead
Common mistakes
Not labelling cells, making identification impossible
Using too many cells, creating visual chaos
History
Voronoi treemaps were introduced by Balzer and Deussen in 2005 to avoid the rigid rectangularity of standard treemaps.
Accessibility notes
Provide a value table and label each polygon with name and percentage. Skip labels on cells below a minimum area threshold (typically <5% of the canvas) — rotated text in tiny polygons is illegible and should fall back to tooltip-only.
Related reading
Got data? Let's see what works.
Drop your CSV. You'll get a Voronoi Treemap plus four alternatives - ranked by which one actually fits your data best.