Reduce the number of displayed items in temporal trend views

Reduce the number of displayed items when many temporal traces share one view. For example, avoid filling an animation or trace overlay with so many items that paths blur together, and avoid a small-multiples grid so large that each trace becomes hard to read.

Higher item counts make all three approaches harder to read, but in different ways. Dense animations and trace overlays create clutter and tracking loss, while dense small-multiples grids shrink each trace until it is hard to inspect.

Mechanism: Fewer displayed items reduce overlap in shared views and keep separate panels large enough to show each path clearly.

Evidence: Participants were significantly more accurate with the small dataset than with the large dataset, and the paper also reports that viewers often lost track of moving points and that higher item counts create clutter in animation and traces while shrinking small-multiple panels (Robertson et al., 2008).

Notes: The paper describes all three techniques as failing to scale much beyond about 200 displayed items.

• User Goal: Find anomalies or compare item-level trends.
• Task: Read or present many temporal traces accurately.
• Data: Many items changing over time in a shared trend view or a grid of trend panels.
• Chart Setting: Animation, trace overlays, or small multiples are being used to show item-level temporal paths.
• Audience: Analysts or presentation viewers.
• Success Criterion: Better accuracy and less crowding.

Break it when: The only way to reduce crowding is to aggregate items, and the task depends on seeing item-level anomalies. Why: The paper notes that aggregation can reduce clutter and occlusion but may hide anomalies of interest.

Sacrifice: You may give up full item coverage in one view. Risk: If you collapse items together, important anomalies can disappear. Mitigation: Keep item-level views for anomaly detection and avoid aggregation when the anomaly itself is the target.

Mistake: Solving crowding only by aggregating items into larger groups. Why it fails: The reduced view may hide the very anomalies the reader needs to detect.

Failure Sign: Paths blur together in shared views, panels become tiny, or viewers report losing track of moving points. Quick Check: Compare one representative task with the full item set and with a reduced item set; if the dense view causes misses or tracking complaints, keep the reduced view. Stronger Test: Verify that each remaining path can be individually tracked without replay or squinting.

• Show a smaller set of items in the temporal view.
• Do not rely on aggregation when the task is to spot item-level anomalies.
• Keep a small-multiples grid only while each panel remains large enough to show its trace clearly.
• If a shared view is still crowded after reduction, move the analysis to a small-multiples layout.