foliplus

foliplus: the missing piece between "see the map" and "use the map". GeoPandas handles data, Folium renders it, foliplus brings it to life.

Scope

Layer data passed to foliplus is read-only: no editing, upload, or deletion.

Data processing happens upstream. foliplus handles the map, not the data.

Features

Beyond Plugins

Traditional map component libraries treat each tool as an independent plugin. foliplus was designed as one system from the start:

• Components communicate with each other, instead of working in isolation
• Layers are managed centrally, instead of each tool owning its own stack
• Conflicts are resolved automatically, instead of tools interfering with each other
• Third-party components can plug into the system, instead of being locked out

Built-in Coordination

Layer-producing tools register their canvas or layer through LayerControl, which manages z-order, visibility, and lifecycle centrally. This means they share a single layer stack — no z-index clashes, no orphaned DOM elements.

On top of this shared layer foundation, tools coordinate further:

• While measuring, search and locate are blocked to prevent map interaction conflicts
• During export, measurement pauses, heatmap renders in full resolution, and layer order is synced for a complete screenshot
• When a layer is removed from the layer panel, the component that owns it (e.g. measurement) auto-cleans its state
• When layers change, the heatmap refreshes automatically

All of this happens without manual wiring — foliplus handles it internally.

Compatibility

Requires folium>=0.14.0. Leaflet is not a Python dependency — the TypeScript controls run against the Leaflet Folium injects into the page.

CI runs the full suite on Folium's Leaflet (1.9.3) and a bring-up smoke on Leaflet 1.0.0 for pages that load a different pin.