MAP
One map for
the whole stack.
A MapLibre wrapper that starts with the global Planet PMTiles archive, adds E2 feature tiles when they exist, and puts search, routes, and spatial compute in the same interface.
Planet by default
The global PMTiles archive is the starting layer, served directly with MapLibre range requests.
Features where they exist
Published E2 feature snapshots with a tile URL become vector layers automatically.
Routes and compute inside
Use the same E2 client to draw routes and visualize GeoJSON analysis results.
A MAP IS A WORKSPACE
Render freely. Keep the geographic logic connected.
E2 keeps MapLibre in control of sources, layers, styling, and interaction state. The difference is what happens when a user clicks a feature, changes a viewport, or draws an area: those ordinary map interactions can become a structured request to search the world, calculate a route, or inspect the data within a boundary.
The result remains normal data and geometry that your application can render, store, or send to another interface. This lets a web map, mobile client, operational console, and agent workflow share geographic behavior instead of rebuilding it in each surface.
OPEN MAP STACK
- 01MapLibre-compatible client rendering
- 02Feature and basemap layers your team can style
- 03Search, routes, and compute connected to selections
- 04Portable geographic outputs for every surface