This vignette demonstrates an optional downstream bridge from
XGeoRTR into ggWebGL.
The ownership split stays fixed:
XGeoRTR owns xgeo_state, embeddings, and
explainable-geometry semanticsggWebGL owns widget construction, shaders, panel
layout, hover, pan, and zoomNo XGeoRTR code is modified here. The bridge lives
entirely inside the ggWebGL example layer.
The representative and multiscale scenes show how optional
XGeoRTR-style renderer inputs can combine coloured explanation-state
points with sparse contribution-direction arrows. Those arrows are true
ggwebgl_layer_vectors() primitives rather than line
segments plus decorative anchors, so the vignette exercises the same
renderer-owned vector path that downstream packages can target.
XGeoRTR is a suggested package for ggWebGL.
When it is unavailable, the package still builds and this vignette
degrades to documentation-only mode.
This scene demonstrates class-coloured explanation points with sparse vector arrows summarising local contribution direction.
This two-panel view keeps the same vector grammar while contrasting the global embedding with a local explanation panel whose viewport is the exact data-coordinate zoom of the rectangle marked in the global panel.