Differences from stock kepler.gl

The panel embeds the real kepler.gl and swaps out exactly one component. Everything else you see is upstream. This page is the complete list of what is different, and why — it is the content kepler's own documentation cannot cover.

At startup

The panel calls kepler's official embedding hook once, before any component mounts, with three settings:

The Flow layer is enabled explicitly

enableFlowLayer: true

The Flow layer is why this plugin pins kepler.gl 3.3.0-alpha.11 rather than the 3.2.6 stable release: it exists nowhere else. Stating it explicitly rather than relying on the upstream default means a change in that default cannot silently remove the feature the plugin is partly built around.

Assets are served from the plugin, not a CDN

cdnUrl: <the plugin's own asset path>

By default kepler fetches its icon library at runtime from a hosted CDN. That does not work here on two counts: Grafana's strict Content-Security-Policy blocks the request under connect-src and it surfaces as an unhandled "Failed to fetch", and an air-gapped install has no route to it at all.

So kepler's icon library is vendored with the plugin and served from Grafana. The path is read from the runtime asset base rather than hardcoded, because Grafana can serve plugin assets from a sub-path or from a CDN of its own.

The knock-on effect is covered under base maps below.

No release banner

showReleaseBanner: false

A "new release" notice has no place inside a dashboard panel.

The map control

kepler ships the entire effects feature but its stock map control never mounts the button, and nothing in the core mounts the manager panel — both are wired by the host application. The panel replaces MapControlFactory with one that adds the effects button and hosts the manager beside the toolbar.

That is the only component injected. kepler's demo app also mounts a SQL data explorer and an AI assistant; neither is included here.

Effect thumbnails are vendored along with the icons, so the picker needs no outbound request.

Base maps

The panel replaces kepler's list of base map styles rather than adding to it.

Five of kepler's nine defaults are Mapbox styles — Satellite With Streets, Dark, Light, Muted Light, Muted Night — and each is a mapbox:// URL that cannot load without an account. Left in place they sit in the picker as choices that blank the map when clicked.

What replaces them:

• kepler's three Carto styles, re-registered from kepler's own definitions rather than copied, so an upstream rename fails a test instead of producing an inert entry.
• kepler's "No Basemap" entry, re-added deliberately — replacing the list would otherwise drop it.
• Esri satellite and topographic, and two relief styles, as the plugin's own style documents.
• A self-hosted style.json, when configured.

Thumbnails are real tiles from each service rather than kepler's bundled images, because pointing cdnUrl at the plugin left every base map thumbnail requesting a file the plugin does not ship.

Full detail on Base maps and relief.

The coordinate interaction is managed

When a Coordinates cross-filtering mapping is configured, the panel switches kepler's coordinate interaction on — and switches it back on if the user turns it off, because the mapping is built on kepler's pinned coordinate and would otherwise stop publishing silently.

Turning it off in kepler's menu is therefore not a way to disable the channel. Remove the mapping instead. See Interactions.

Layers the panel builds that kepler does not

kepler auto-detects layers from column names, but not all of them:

Layer	Why the panel builds it
Trip	kepler's own heuristic insists on a column literally named id
Flow	kepler does not auto-detect flows at all
Flow field	a layer type kepler does not have — the panel registers it, and it traces its own streamlines through a grid of velocities
Raster tile	kepler builds one from its own tileset form, but not from a query — the panel turns a raster_url column into the dataset it needs
WMS	likewise, from a wms_url and wms_layer pair

See How a query becomes a map.

Two layer types kepler does not ship

Zarr and Flow field are registered by the panel into kepler's own layer registry, so they appear in the layer list and in the type selector alongside the rest. Nothing upstream corresponds to either: kepler's remote tile formats are MVT, PMTiles and WMS, none of which is a store of compressed arrays; and a velocity grid has no layer at all, because what it draws is in none of its rows.

The flow field also carries a settings panel of its own — density, stroke, trail, cycle, smoothing and the vertical exaggeration of a stack of levels — which kepler renders through a layer configurator the panel extends. See Velocity fields.

A WMS gets a clock it does not have upstream

kepler draws a WMS, but has no notion of its time dimension: a time-aware service is asked without a TIME and answers with its default slice for ever. The panel reads the layer's calendar — from the query, or from the service's own GetCapabilities — puts it on the map's time widget, and carries the selected date onto every request, the click that asks GetFeatureInfo included.

See Imagery over time.

Scene changes happen on the layer, not to it

Walking a series of rasters could be done by replacing the dataset for each date, and that is what the obvious implementation does — at the cost of a new layer with default styling every time the date changes. The panel re-points the layer that is already drawing instead, so its id, its name and everything you styled survive the change, and deck.gl keeps the previous image on screen until the new tiles have drawn.

A window that contains no scene hides the layer rather than removing it, for the same reason: playback crosses gaps, and a rebuild on the far side of one would reset the styling every loop.

A colour ramp is imposed, when you ask for one

kepler's default raster ramp is cfastie, which is built for drone NDVI and is not monotonic. The panel leaves it alone unless the Raster colour ramp option names another, in which case the ramp is applied to the rasters your queries produce. See Rasters.

Refresh behaviour

On a query refresh the panel replaces the data underneath the existing datasets rather than removing and re-adding them, so the layers, filters and styling you configured survive.

This is a deliberate departure from how such panels usually work. Remove-then-add on every refresh is the simpler implementation, and it discards the user's layer configuration each time the query re-runs.

Where upstream documentation is behind this plugin

kepler.gl's public documentation describes the 3.2 stable line. This plugin bundles 3.3.0-alpha.11. Two consequences when you follow an outbound link:

• Upstream lists fifteen layer types. The bundled pre-release registers twenty-one — the Flow layer among them, which upstream does not document at all.
• Some layer attributes exist in the UI without an upstream entry. Trail Length on Trip layers is the one you are most likely to want; it is deck.gl's trailLength, covered in Under the hood.

See Upstream documentation for the pinned versions in one place.

Split maps: the layers here read the pane they are drawn for

Splitting the view is kepler's own feature and works as its documentation describes — the map control's first button offers Single, Dual and a Swipe curtain you drag. What did not work were the layers this panel builds.

renderDeckGlLayer decides whether the pane being drawn shows a layer, working it out from splitMaps[i].layers, and passes the answer to renderLayer for each layer to apply — which the stock layers do inside getDefaultDeckLayerProps. The tileset layers here build their deck props by hand and never read it, so every pane drew every layer: a split screen came up with both halves identical and the legend's per-pane eyes changed the state without switching anything off.

They now apply it, through shownInPane. That verdict has three shapes rather than two, which is where the one deliberate difference lives. Kepler gives the left pane every layer and, in its own words, leaves the right one empty; it then reads the list back as !mapLayers || mapLayers[layer.id], so a layer the empty pane never listed comes out undefined rather than false, and deck reads undefined as its default, visible. Upstream, the pane meant to open empty therefore draws everything and its eyes need two clicks before the first one bites. The layers here read it as written — not listed, not drawn — so Dual opens with the layers on the left and an empty right, one click per eye. Swipe is unaffected either way: it duplicates the list into both panes, so both halves start with everything and one click hides a layer on one side of the curtain.

What is not different

Worth stating plainly, because the list above can give the wrong impression. The layer types and their attributes, colour palettes and scales, filters, the tooltip and brush interactions, map settings, 3D and globe, playback, the draw tool, the legend, saving and exporting — all of that is stock kepler.gl, behaving as its own documentation describes.