Map effects plugin

The Map Effects plugin adds practical post-processing to a TomTomMap. Its effects are computed from the rendered map’s pixels, not its style, so they work on every style and survive style releases. MapLibre itself has no post-processing. The playground below puts every effect on one panel:

Each effect is named after the problem it solves, is off by default and has its own guide:

Installation

1
npm install @tomtom-org/maps-sdk maplibre-gl @tomtom-org/maps-sdk-plugin-map-effects

@tomtom-org/maps-sdk and maplibre-gl are peer dependencies.

Usage

1
import { resetKnob, setKnob, setKnobs, TomTomMap } from '@tomtom-org/maps-sdk/map';
2
import { effectKnobCatalogue, MapEffects } from '@tomtom-org/maps-sdk-plugin-map-effects';
3

4
const map = new TomTomMap({
5
    style: 'streetDark',
6
    mapLibre: {
7
        container: 'map',
8
        // Bloom, the depth of field, your own passes and capture read the map canvas back.
9
        canvasContextAttributes: { preserveDrawingBuffer: true },
10
    },
11
});
12

13
const effects = new MapEffects(map); // or new MapEffects(map, config)
14

15
effects.updateConfig({ grade: { saturation: 0.4, brightness: 0.85 }, tint: { opacity: 0.15 } }); // a quiet base
16
setKnob(effects, effectKnobCatalogue, 'bloom.intensity', 0.5);                     // one knob
17
setKnobs(effects, effectKnobCatalogue, { 'bloom.radius': 14, 'bloom.threshold': 0.6 }); // several, the rest kept
18

19
resetKnob(effects, effectKnobCatalogue, 'bloom.intensity'); // one effect off
20
effects.resetConfig();                                      // everything off

• Bloom, the depth of field, your own passes and capture read the map canvas back, so they need preserveDrawingBuffer: true. The plugin warns once if it is missing.
• The configuration (MapEffectsConfig) nests each knob along its id, so bloom.intensity is bloom: { intensity }. getConfig() returns the knobs set, and resetConfig() turns everything off.
• MapEffects follows the same rules as a map module. For values your code writes, use applyConfig(config), which replaces them all, or updateConfig(config), which replaces each effect you name and keeps the others. Note that updateConfig({ bloom: { threshold: 0.3 } }) drops the bloom’s other knobs. TypeScript checks these values, and nothing checks them at run time.
• For values held as data, from a control, storage or a language model, use the SDK’s setKnob and setKnobs with effectKnobCatalogue. They check every value before anything changes, then set each knob by its id and keep every other one, including the rest of its effect. A refused value throws RangeError, and an unknown id throws Error. getKnob returns the value set, otherwise the catalogue default, and resetKnob unsets one.
• remove() detaches the effects, removes their elements from the page and releases the chain’s WebGL context. This matters because browsers cap the contexts per page.
• The chain takes that context only when it first has something to run: your own pass or the depth of field. Bloom and the CSS overlays need none, so a MapEffects with neither on holds no context. Once taken, it’s held until remove().

How it renders

No effect knob writes the MapLibre style. Every effect reads the map’s rendered pixels, so the knobs change the frame rather than what the map draws. The one link to the style is bloom.only, which keys on the colours the style paints for the style colour knobs it names, whichever module holds them:

The effects draw in three kinds of layer, in this order:

1. The GPU chain is a WebGL2 canvas under everything else. It runs your passes and the depth of field on the map’s pixels. Each pass reads the previous pass’s output without the picture leaving the GPU.
2. Bloom is a small canvas blended in screen mode over that result.
3. Overlays are CSS layers over both: grade, fog, edge blur, tint and vignette.

As a result:

• Bloom reads the chain’s output, not the raw map. A defocused highlight glows as the wide soft disc a photograph gives it, and a hue-shifting pass of yours runs before bloom’s colour key.
• The overlays work on the glow too. A grade, a tint or a vignette changes the bloom along with the map under it.
• Capture runs the same chain at the requested pixel ratio, then composites the same overlays, so what you capture is what was on screen.
• The chain and bloom redraw on the map’s render event, at most once per animation frame. The CSS overlays need no redrawing.
• Nothing takes pointer events. The effects sit below the map’s controls and leave hit-testing and SDK events alone.

The catalogue

effectKnobCatalogue lists every knob as static data, which you can read without a map. Each entry has an id, a kind (number, color or colors), a description, a default and a useCase. A number knob adds a range, and bloom.only lists its accepted names in options. It shares the entry shape of the SDK’s knob catalogues, and the playground above builds its panel from it. effectKnobIds lists the ids, EffectKnobId is their union and EffectKnobValueOf<ID> is the value one takes.

Each effect’s guide lists its ranges and defaults:

Capture

capture({ pixelRatio }) renders the current view, map and effects, into one canvas. The plugin re-renders the map at the requested ratio rather than resampling it, reads it back once every tile is drawn, and then sets it back to its previous ratio. MapLibre clamps to its maxCanvasSize, so measure the ratio you got from the returned canvas.

1
const canvas = await effects.capture({ pixelRatio: 3 });
2
canvas.toBlob((blob) => upload(blob), 'image/png');

Relation to the Styling Foundations module

The Styling Foundations module changes the style (what the map draws), and effects change the frame (how the drawn map looks). The two combine. The data-viz map preset quiets the map’s content, and grade.saturation and tint.opacity mute what remains.

API reference

For complete documentation see the MapEffects API Reference and effectKnobCatalogue.

Related guides and examples

Related guides

• Map styling - The styling knobs, and the map-wide colour ids bloom.only names
• Map modules - The knob kinds the effect catalogue shares with the SDK’s own catalogues

Related examples

• Map effects playground - Every effect on one panel
• Bloom playground - Every bloom knob, the colour scope included
• Traffic flow with bloom - Live traffic glowing over a dark map
• Mixed map effects - A watercolour pass of your own, with bloom, grade and vignette over it
• 3D terrain playground - A depth of field over a valley
• Route fly-over playground - A depth of field holding the road ahead in focus