Stanford CS448B 03 Visdesigns
· 2 min read
TLDR
This article contains my notes from Stanford's CS448B (Data Visualization) course, specifically focusing on the third lecture about visualization designs. I'll discuss the principles of effective data visualization, including the importance of guides, expressiveness, effectiveness, support for comparison and pattern perception, grouping and sorting data, transforming data, reducing cognitive overhead, and consistency. I'll also cover various chart types, such as line charts, bar charts, stacked area charts, and others, providing examples and discussing their design considerations.
Original
Notes
Forward-Thinking
- When can data visualizations be the wrong solution? (When should we opt for text over a graphic?)
- How have data viz design principles changed over time, and why, especially as it seems like accessibility is more highly prioritized today? (e.g. Minard's chart is very info-dense, vs. simplercharts seen more often on outlets today)
- What are some safeguards to reduce / prevent misleading visualizations, and / or ensure that a visualization is unbiased (or as Tufte says, "fail to tell the truth")?
Design Considerations
- Guides: Title, labels, legend, captions, source!
- Expressiveness and Effectiveness
- Express the facts and only the facts
- Avoid unexpressive marks (lines? gradients?)
- Use perceptually effective encodings that match data type
- Don’t distract: faint gridlines, pastel highlights/fills
- The “elimination diet” approach – start minimal
- Support comparison and pattern perception
- Between elements, to a reference line, or to counts
- Use reader-friendly units and labels
- Group / sort data by meaningful dimensions
- Transform data (e.g., filter, log, normalize)
- Are model choices (regression lines) appropriate?
- Reduce cognitive overhead
- Minimize visual search, minimize ambiguity
- Appropriate size, aspect ratio, legible text
- Avoid legend lookups if direct labeling works
- Avoid color mappings with indiscernible colors
- Be consistent!
- Visual inferences should consistently
- support data inferences
Notes
The rest are chart case.