Fly-over plugin
RouteFlyover flies the camera along a route. It aims at the junctions ahead, frames them, keeps
clear of the terrain, and holds the followed position, marked with an arrow, where you want it on screen.
npm install @tomtom-org/maps-sdk maplibre-gl @tomtom-org/maps-sdk-plugin-flyover@tomtom-org/maps-sdk, maplibre-gl and @turf/turf are peer dependencies. @turf/turf is one of the SDK’s
own, so it installs with the SDK.
import { calculateRoute } from '@tomtom-org/maps-sdk/services';import { RouteFlyover } from '@tomtom-org/maps-sdk-plugin-flyover';
const routes = await calculateRoute({ locations, guidance: { type: 'coded' } });const flyover = new RouteFlyover(map, { route: routes.features[0], camera: { speedKMH: 300, pitch: 76 }, onProgress: ({ traveledDistanceInMeters }) => showProgress(traveledDistanceInMeters),});
flyover.start();By default, MapLibre caps the pitch at 60°. To tilt further, set mapLibre: { maxPitch: 85 } on the map.
Use cases
- Preview a drive, such as a scenic route, a delivery round or a race stage.
- Present a corridor (roadworks, a new line, an itinerary) without authoring a camera path.
- Show a long route in a short loop. The flight wraps at the destination and never lands.
- Replay a trip once, from the departure to the destination, next to your own trip controls.
What it needs from the route
- The line and its
progress, which a calculated route carries by default. - Optionally, guidance. To use the
instructionaim and theinstructionszoom, ask forguidance: { type: 'coded' }. Without it, the aim falls back to itsfallbackMetersAhead, and the zoom falls back to a fixed level.
The camera
Every field has a default. Change any of them mid-flight with setCamera(). getCamera() returns the camera in use, defaults included.
| Field | What it does | Default |
|---|---|---|
speedKMH | ground speed of the camera | 200 |
pitch | camera tilt in degrees, up to the map’s maxPitch | 70 |
aim | what the camera looks at down the road | { mode: 'instruction', fallbackMetersAhead: 250 } |
zoom | what sets the camera’s height | { mode: 'instructions', instructionsAhead: 2 } |
anchor | where the followed position sits on screen | follows the pitch |
Aim: what the camera looks at
The camera points ahead of itself, so it turns into a bend before reaching it.
{ mode: 'instruction', fallbackMetersAhead }- The next guidance instruction, the junction it is heading for. The default.{ mode: 'distance', metersAhead }- A fixed distance down the road.{ mode: 'points', pointsAhead }- A number of route vertices. They are denser through bends, so the aim shortens where the road turns.
Zoom: how high it rides
{ mode: 'instructions', instructionsAhead }- Fits the road up to the Nth junction ahead (at least one) in view, so hairpins pull back and straights close in. The default.{ mode: 'speed' }- Rises with the ground speed, one zoom level per doubling.{ mode: 'fixed', zoom }- One zoom.
The two automatic modes stay between zoom 11 and 15. In every mode, the camera pulls back further where terrain would block its view of the road.
Anchor: where the position sits on screen
A level map is a plan, so the position belongs in the middle. A tilted map shows mostly what lies
ahead, so the position belongs low. Without an anchor, the position slides down with the pitch, to
two thirds at 60°. A top-down pass needs no mode of its own.
import { anchorForPitch } from '@tomtom-org/maps-sdk-plugin-flyover';
flyover.setCamera({ anchor: { x: 0.5, y: 0.67 } }); // fractions of the viewportconst anchor = anchorForPitch(76); // what a pitch would choose: { x: 0.5, y: 0.667 }- It holds over terrain at any pitch and zoom, because the camera looks at the road on the ground.
- The camera eases into a changed anchor rather than jumping to it.
- The plugin applies it as viewport padding, kept 5% clear of the edges.
remove()restores the padding the map had.
The marker
An arrow lies on the road at the followed position, facing along it. Restyle, replace or hide it
with marker. Change it mid-flight with setMarker(), which replaces the whole marker setting.
// The arrow, recoloured with the SDK's SVG icon options.new RouteFlyover(map, { route, marker: { image: { type: 'arrow', fillColor: '#e2231a', outlineColor: 'white' } } });
// An image of your own, drawn pointing up: a URL, raw SVG markup, a data URI or a loaded <img>.flyover.setMarker({ image: { type: 'custom', image: '/icons/car-top-down.png' }, size: 56 });
flyover.setMarker({ visible: false });| Field | What it does | Default |
|---|---|---|
visible | whether the marker is shown | true |
image | { type: 'arrow', fillColor?, outlineColor?, outlineOpacity? } or { type: 'custom', image } | the arrow in the SDK’s default route outline colour, outlined in white |
size | width and height in pixels, before the pitch foreshortens it | 44 |
- The map draws it in a custom layer restored after style changes.
MapEffects, depth of field included, and captures take it along. - It is placed as each frame is drawn, on the terrain under its route point. So it never trails the camera the way a symbol layer, updated through a worker, would.
- It isn’t themed. A map theme’s accent recolours the route, not the arrow. To
match a themed route, pass
fillColor: map.mapColors.accent. - It needs the Mercator projection. A custom image on another origin needs CORS, because it becomes a WebGL texture.
Terrain
- Where a ridge behind the road would block the view, the camera zooms out along the same line of sight until it is 200 m above the ground. Pitch and anchor stay put.
- While running, the flight sets the altitude of the point it looks at to the ground under the road,
easing it so the camera doesn’t step as elevation tiles load. For this,
start()turns MapLibre’s centre clamping off, andstop()restores your setting, so a paused map behaves as usual. - Without
TerrainModule, which raises the terrain, there is nothing to clear, and the camera looks at sea level.
Smoothness, and what it costs
- Critically damped springs move the heading, zoom, pitch, anchor and altitude. They don’t overshoot or kick when a target changes, and a start ramps the speed up. Each step is solved exactly, so a flight looks the same at 30, 60 or 120 fps.
- The flight decides the heading five times a second. It ignores changes under 2.5°, which come from the line’s sampling rather than the road, and caps real turns at 22°/s.
- The expensive route lookups, framing and terrain queries run on that tick. Per frame, the flight only steps its springs and moves the camera, so cost doesn’t grow with the refresh rate.
Controlling the flight
flyover.start(); // or resume, ramping up to speedflyover.stop(); // freeze where it isflyover.seek(0.5); // jump to half way along, clamped to 0..1flyover.seek({ traveledTimeInSeconds: 1800 }); // or to a time, a distance or a clock timeflyover.setRoute(nextRoute); // fly a different route, from its startflyover.setCamera({ pitch: 45 });flyover.running; // whether the flight is advancingflyover.remove(); // stop, take the marker off, and restore your paddingonProgressreports the distance and time travelled on the five-times-a-second tick, and on everyseek.seektakes the sametraveledTimeInSeconds,traveledDistanceInMetersorclockTimethatgetCoordinateAtRouteProgressreads. A point before the departure or past the destination moves the flight to that end, and a clock time on a route without a departure time moves it to the departure.- While the flight runs, it controls the camera. A
jumpTooreaseToof yours fights it, so callstop()first. - Until the flight first places the camera with
start()orseek(), the page keeps the view. So you can show a whole route before anyone flies it.
Flying once to the destination
By default, the flight loops. Set loop: false to stop it at the destination instead. It calls
onArrive there, and onProgress reports the destination last.
const flyover = new RouteFlyover(map, { route, loop: false, onProgress: ({ traveledTimeInSeconds }) => showTripClock(traveledTimeInSeconds), onArrive: () => showPlayButton(),});start() after the arrival flies the route again from its departure.
Try it in the route planner: open Directions and press play. The trip flies once, and the slider and the turn list follow the flight:
API reference
For complete documentation see the RouteFlyover API Reference and anchorForPitch.
Related guides and examples
- Route fly-over playground - Every camera setting on one panel, with a depth of field holding the road ahead in focus
- React route planner - A planned trip flown from its directions, the slider and the turn list following the flight
- Depth of field - The lens that keeps the road ahead sharp
- Terrain - The relief the camera clears