Motion Prompt LabAnimated map prompts: 5 tested templates (routes, convoys, frontlines)
Animated maps are the documentary genre everyone wants and nobody can prompt in one line — a map is geography, timing and labels all at once. So we built the whole family the slow way: five map templates, written as structured prompts, rendered by us in HyperFrames + GSAP on real Natural Earth geography, and logged with everything that broke along the way. Two of the five tell fictional stories (a tank exercise and a battle), and they are labelled fictional inside the films themselves, in the kicker and the footer, because a template that teaches labelling honestly is worth more than one that hopes nobody asks.
Every template is free to copy, with its project files attached. The pattern underneath all five is the same: real map data, one timeline, and a vehicle or line whose motion is driven by a single progress value that everything else reads.
1. The route explainer — one arc, two cities, three numbers
The base pattern: a world map pushes in on the Atlantic, New York pulses, an orange arc draws itself to London with a white dot riding its head, and three stat chips land under the map. It took four renders, and two of the failures are now rules for us. First, drawing the map projection naively streaked lines across both oceans — the ±180° seam, where a country's outline jumps from one edge of the world to the other; the generator now breaks the path at every jump. Second, the marker dots were animated by scaling a group, which silently moved them off their coordinates and left hollow rings behind; dots now animate their radius attribute and stay exactly where geography put them. The animated map explainer, its prompt and run log.
2. The flight tracker — a jet that steers
Tokyo to Sydney, with a jet glyph riding the arc rotated to its tangent, so it banks along the route instead of sliding sideways. The first render taught the zoom lesson: we computed the push-in from the route's midpoint alone, and at 2.05× Sydney ended up off-stage with its label clipped. The zoom has to be solved from both endpoints — recomputed to 1.42× around a centre that keeps Tokyo's label and Sydney's marker in frame at the same time. Flight paths are the friendliest member of the family to build, and the one where framing errors are least forgiving. The flight tracking map template.
3. The convoy tracker — checkpoints that cannot drift
Los Angeles to Phoenix on a regional map with real US state borders: a truck drives the route, the trail draws behind it, and Barstow, Las Vegas and Flagstaff each fill in at the exact frame the truck arrives. The sync is not keyframed — the truck, the trail and the checkpoint triggers all read one eased progress value, so a checkpoint cannot fire early. Its failure was a colour lesson: on arrival, Arizona fills orange, and everything orange inside it — the destination marker, a stretch of the trail, nearly the state label — simply vanished. The fix is a class rule now: design for the arrival state, not the empty map. Anything that ends up inside a highlight fill needs a white body or a dark edge. The convoy tracking map template.
4. The unit tracker — frame the operation, not the continent
Three tank units advance in two phases across a France–Germany sector, an operation clock ticks DAY 1 to DAY 3, and objectives turn orange as they are secured. The first cut drew the whole region, which put the entire battle in one corner of the stage as a knot of overlapping labels — the automated checker raised real text-overlap and contrast errors, not warnings. Cropping into the sector fixed the geometry; staggering the objective labels into open ground and retiring the unit name tags before the final phase fixed the rest. A map film's label layer has to be planned for the end state, when everything has arrived and the stage is at its most crowded. The unit tracking map template.
5. The frontline animation — a line that morphs through dates
The war-map signature: a frontline that bulges eastward through four dated states over 21 days, territory shading in behind it, towns flipping to TAKEN as it passes them. Path morphing only works when every state has identical structure, so all four fronts are generated by one smoothing function with per-point offsets — hand-drawing four variants would have broken the morph. The first cut also closed the territory at an interior line, which read as a floating rectangle pasted on the map; the shaded zone now runs off the frame edge, the way the documentary maps it models actually work. Town captures are timed from the geometry — the moment the front's line crosses the town at its latitude — not eyeballed. The frontline advance animation template.
What five map renders taught us
One progress value drives everything. Vehicle, trail, checkpoint, capture: if two things must agree, they read the same number. Every sync bug we have ever shipped came from two clocks; every fix was merging them into one.
Design for the arrival state. Highlights fill, labels gather, units arrive — the last frame is the most crowded and the most screenshot. The convoy's invisible marker and the unit tracker's label knot were both end-state failures in films whose first frames were perfect.
Frame the operation, not the continent. A world map is for world routes. The moment the story is regional, crop until the action fills the stage — the checker will find your label collisions if you don't.
Real geography is free; fictional stories must say so. All five films draw on Natural Earth data (via world-atlas, plus US state boundaries for the convoy), which is why the coastlines are right. The two invented operations carry FICTIONAL in the kicker and the footer for the whole film. The full set lives on the maps tag page, alongside the explainer collection; the photo-side sibling from the same production week is the parallax photo animation.
Method note: all five templates were written, rendered and logged by us on Nov 2, 2026 (HyperFrames 0.8.188 + GSAP, local renders, zero credits). Render counts: route explainer four, flight tracker two, convoy two, unit tracker three, frontline two. Every entry page carries its full prompt, its project files and its own "what broke" — this post is the summary, not the source.