Hello KNIME team,
I would like to request an enhancement for the Kepler.gl Geoview node.
Problem
Currently, the configuration done inside the interactive Kepler.gl UI is not saved as part of the node settings. After reopening a workflow, resetting the node, or executing the workflow on another machine, the map configuration must be recreated.
This includes settings such as:
-
Basemap / map style / Custom Mapbox style URL
-
Layer configuration and styling
As a result, the visualization is not fully reproducible and requires manual reconfiguration.
Requested Feature
Allow the node to persist the Kepler.gl configuration state so that settings created within the UI are stored with the workflow and restored automatically.
Ideally the following should be saved:
1. Map Style / Basemap
-
Selected basemap
-
Custom Mapbox style URL (e.g.
mapbox://styles/...or style JSON URL)
2. Map Layers
-
Layer definitions (point, heatmap, hexbin, etc.)
-
Selected data columns
-
Visual styling (color scale, opacity, radius, etc.)
-
Layer ordering and visibility
4. Filters / interactions (if applicable)
-
Filters configured within the Kepler UI
-
Tooltip configuration
Possible Implementation (suggested by ChatGPT)
Kepler.gl already exposes a JSON configuration/state object, so the node could potentially store this JSON as part of the node configuration and restore it when the node view is reopened.
Optional additions that could be useful:
-
Button: “Save current map configuration”
-
Option to export/import Kepler configuration JSON
-
Automatically restore configuration when the input schema matches
Benefits
-
Improved reproducibility of visualizations
-
Easier workflow sharing and collaboration
-
Avoids rebuilding map layers and styles after reopening workflows