Labs / Chapter 14
Chapter 14 treats animation as a high-risk representational method. This lab asks students to decide when motion earns its place and how to constrain it when it does.
Chapter 14 argues that animation earns its place only when motion explains temporal change better than static alternatives. This lab teaches you to justify animation, specify temporal controls, make time visible, and constrain motion so it serves interpretation.
Choose one scenario where time matters. It may be real or hypothetical.
Temporal map scenario Phenomenon: Place: Audience: Temporal unit: hours / days / years / decades / events Data type: discrete snapshots / continuous process / route / projection Primary temporal pattern to reveal: Static alternative that might work: Motion risk: Accessibility concern:
Evaluate whether this temporal map should be animated, shown as small multiples, controlled by a time slider, or presented as static snapshots. Explain what animation would reveal that static design might obscure, and what animation could distract from or misrepresent. Scenario: [PASTE]
Create a temporal design brief using animation variables: duration, rate of change, order, display date, frequency, and synchronization. For each variable, specify the design decision and how it supports interpretation. Scenario: [PASTE]
| Temporal variable | Specification | Interpretive purpose | Risk if wrong |
|---|---|---|---|
| Duration | Example: Last 30 days | Example: Show recent change | Example: Could overstate certainty |
| Rate of change | Example: Last 30 days | Example: Show recent change | Example: Could overstate certainty |
Starter examples only; expand this in your own notes or submission document.
Decide whether this map should use stop-frame transitions or smooth transitions. Explain whether the underlying data represent discrete snapshots or a continuous process. Identify what false temporal structure the wrong transition type would imply.
Design temporal controls and a temporal legend for this map. Include play/pause, slider or scrubber behavior, speed controls if needed, loop behavior, reset behavior, date/year display, progress indicator, and where the temporal legend should sit relative to the map. Do not allow autoplay unless you justify it.
Write non-negotiable motion constraints. Include: no autoplay on page load, no automatic looping, animation only on explicit state change, maximum total runtime, one major moving element at a time, pause/stop controls, and prefers-reduced-motion behavior that replaces motion with instant state changes.
Compile my decisions into a production-ready Animation Specification. Include: 1. animation justification 2. static alternative considered 3. data temporal structure 4. stop-frame or smooth transition choice 5. duration, rate, order, display date, frequency, synchronization 6. controls 7. temporal legend 8. motion constraints 9. reduced-motion fallback 10. legend updates and class consistency 11. human review checklist 12. default animation behaviors to avoid Write this as a concise professional specification.
Critique this Animation Specification. Answer: - Does motion explain something static maps cannot? - Can a first-time user understand what changes without instructions? - Is the temporal legend visible and synchronized? - Does motion stop when it should? - Would the animation fatigue a user after three views? - What should be removed or simplified?
Can you tell Ian thinks this is really, really important yet? Good. Keep going.
Do the tiny-but-mighty judgment check. If these answers are fuzzy, revise the map idea before polishing the prompt.
For use with Prompt Cartography: Interactive Web Map Design with LLMs, CRC Press. www.promptcartography.com
Prompt Cartography