The treemap screenshot doesn't look correct. Nearly all charting libs (like Apache Echarts) will group nodes with a heading name, so not sure why they claim it would be hard to notice the "drivers" node. I guess in that screenshot, sure, but that looks like just a bad implementation of a treemap. Maybe this was the case back in 2017? Flame graphs I have a love/hate relationship with. The hierarchy is very useful, but…
At an old startup attempt we once created a nested hierarchy metrics visualization chart that I later ended up calling Bookshelf Charts, as some of the boxes filled with with smaller boxes looked like a bookshelf (if you tilted your head 90 degrees). Something between FlameGraphs and Treemaps. We also picked “random” colors for aesthetics, but it was interactive enough so you could choose a heat map color for the plo…
Flame Graphs vs Tree Maps vs Sunburst (2017)
31–38 of 38 posts
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#32I've been using WinDirStat for a tree visualization of Windows disk space for a very long time. Great software. https://windirstat.net/
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#33The treemap screenshot doesn't look correct. Nearly all charting libs (like Apache Echarts) will group nodes with a heading name, so not sure why they claim it would be hard to notice the "drivers" node. I guess in that screenshot, sure, but that looks like just a bad implementation of a treemap. Maybe this was the case back in 2017? Flame graphs I have a love/hate relationship with. The hierarchy is very useful, but…
At an old startup attempt we once created a nested hierarchy metrics visualization chart that I later ended up calling Bookshelf Charts, as some of the boxes filled with with smaller boxes looked like a bookshelf (if you tilted your head 90 degrees). Something between FlameGraphs and Treemaps. We also picked “random” colors for aesthetics, but it was interactive enough so you could choose a heat map color for the plo…
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#34Earlier quoted context omitted.
Why do treemaps suck?
It's not as straightforward to compare area as sorted length. Look at the example in the link and try to make sense of it.
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#35The treemap screenshot doesn't look correct. Nearly all charting libs (like Apache Echarts) will group nodes with a heading name, so not sure why they claim it would be hard to notice the "drivers" node. I guess in that screenshot, sure, but that looks like just a bad implementation of a treemap. Maybe this was the case back in 2017? Flame graphs I have a love/hate relationship with. The hierarchy is very useful, but…
Like, one just has to look at the qdirstat screenshot at https://github.com/shundhammer/qdirstat. On the bottom-right corner, there are visually distinct boxes of sub-boxes that guide the eye towards a logical set of files.
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#36It's not that hard to fix the area problem with sunburst charts, by decreasing the radius for outer rings. E.g. https://github.com/vasturiano/sunburst-chart
Treemaps are indifferent to "unknown" or "unlabeled" nodes. Area is disk space.
Whereas the simple act of labelling a node adds another outer ring arc to the sunburst (thus more coloured area), even though the underlying truth hasn't changed.
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#37I've been using WinDirStat for a tree visualization of Windows disk space for a very long time. Great software. https://windirstat.net/
Re: Flame Graphs vs Tree Maps vs Sunburst (2017)
#38It's not that hard to fix the area problem with sunburst charts, by decreasing the radius for outer rings. E.g. https://github.com/vasturiano/sunburst-chart