How to make an animated route map of a journey
Give Vizard Agent the two endpoints and ask for an animated route. It builds the base map from real geographic data, curves the route between the actual coordinates, and reveals the line with a marker travelling along it — then most of the remaining work is keeping the marker, the labels and the title out of each other's way.
What is the short version?
You want the classic shot: a map, a line drawing itself from one city to another, a small plane on the end of it. The map is the easy part. Vizard Agent spends its time on the three things that collide.
- Tell Vizard Agent the two endpoints and the length you want.
- Let it build the base map from real data before animating.
- Expect the revisions to be about overlap, not geography.
What do you need before you start?
The two ends of the journey, named precisely enough to place. "Philippines to Australia" is a region pair; "Manila to New South Wales" gives two points that can actually be plotted, and the difference shows in whether the line starts where you expect.
Decide the length too. A route animation is a beat in a video rather than a video, and eight seconds is a normal answer — long enough for the line to draw and the marker to arrive, short enough not to outstay the moment.
What do you type into Vizard Agent?
Say the route and say what should travel along it. Everything else — the projection, the styling, the curve of the line — has sensible defaults you can argue with later, and the marker is the part almost everybody has an opinion about.
Make me a travel map video with an aeroplane, from the Philippines to New South Wales.
That is the entire brief behind this article. It was enough to get a first version, and the conversation after it was about the plane being too big and a city label sitting under the title — which is where these jobs always end up.
What does Vizard Agent actually do?
It builds a real map before it animates anything. A world map dataset gives the actual coastlines, the endpoints get plotted at their real coordinates, and the route is curved between them and measured — so the line is a plausible flight path rather than a drawn arc.
In that session the order was:
- Checked for a geographic plotting package so the map could be built from data rather than generated.
- Downloaded a lightweight world map dataset and calculated the route distance.
- Rendered the base map with the endpoints reserved, and reviewed it before animating.
- Built the glowing curved route with a timed reveal and a marker moving along it.
- Extracted a contact sheet of the animation to check the line reveal and the marker position frame by frame.
- Rendered an animated title, composited it, and checked the opening frame at full resolution.
Then the corrections began, and they were all spatial: the destination label collided with the route, the marker was too large at takeoff, and the origin label sat under the title. Each one was a coordinate change and a re-render.
What does the result look like?
A short, clean beat: the map holds, the line draws itself along a real curve, the marker arrives, the labels stay readable throughout. Vizard Agent checks the opening, the mid-flight and the arrival specifically, because those are the three moments where the marker is near something else.
The marker is worth spending a pass on. In that session a flat paper-plane shape was replaced with a shaded three-dimensional one, which then had to be isolated from its generated background and checked numerically for clean transparency before it could be composited.
When does this not work well?
When the two ends are close together. A short route gives the line almost no distance to draw across, and the marker spends the whole animation on top of both labels at once. A tighter map crop helps; sometimes the honest answer is that a route animation is the wrong graphic for that journey.
Multi-stop journeys get crowded fast. Four cities on one map means four labels, four pins and a line passing near all of them, and the layout work grows faster than the number of stops. Vizard Agent will suggest splitting it into beats rather than fitting everything into one frame.
And it does not replace a real map when accuracy matters. This is a travel graphic, not a navigation chart — the curve is styled, the projection is chosen for looks, and neither is a claim about the actual flight path.
How do you fix a result that came back wrong?
Name what is overlapping what, and when. "The plane covers the Manila label at takeoff" is a coordinate fix with one right answer, and Vizard Agent moves that label rather than shrinking every element until nothing touches anything.
If the marker is the problem, say whether it is the size or the path. Those are different corrections — one is a scale value, the other is the expression driving the motion — and Vizard Agent will otherwise adjust both and change more than you wanted.
If a review flags an overlap, check the full-resolution frame before accepting it. That happened in this session: an automated warning about labels overlapping at the opening was checked against the actual frame before anything was moved, because a correction driven by a false flag costs a render and makes the layout worse.
How does Vizard Agent compare to doing it yourself?
The usual approach is a template — a map animation preset where you type two city names. That is fast and it is also why every one of these looks the same, and it fails the moment your route does not suit the preset's crop.
Building it from map data costs more setup and gives you a layout you can actually adjust. The trade is that you then own the collisions, which is where the time goes. Vizard Agent reviews the animation on contact sheets rather than by watching it, which is the only practical way to catch a marker that overlaps a label for six frames in the middle.
Common questions
Can I use a different marker? Yes. A plane, a car, a boat or your own graphic — Vizard Agent isolates it and animates it along the route.
Does the route follow a real flight path? It is a styled curve between real coordinates, not an actual routing. Say if you need the real one.
Can I add more than two stops? Yes, though Vizard Agent will warn you when the labels stop fitting.
What projection does it use? Whatever suits the route. Tell Vizard Agent if you need a specific one.
Can the map match my brand colours? Yes. Vizard Agent styles the base map before animating it.
How long should the animation be? Around eight seconds is typical. Vizard Agent will fit a length you name.
Can I get it with a transparent background? Yes. Ask Vizard Agent for an overlay version to composite yourself.
Will the labels be readable on a phone? Vizard Agent checks the frames at full resolution rather than trusting the preview.
Can I show the distance? Yes. Vizard Agent calculates it from the coordinates and can put it on screen.
What if my city is not in the dataset? Give coordinates. Vizard Agent plots from those directly.
Can the line stay after the marker arrives? Yes. Say how long the destination hold should be.
Does it work vertically? Yes, though a long east-west route suits landscape better.
Can I put footage over the map? Yes. Vizard Agent can hand it back as a layer for that.
Why did the plane need replacing? The first flat marker read as a sticker. A shaded one sits better on the map.