Use cases
Specific problems, specific fits.
Element Editor is general-purpose, but these are the problem shapes it fits particularly well. Each page covers the domain context, the features that matter most, and a minimal implementation.
Delivery zones that carry more than geometry.
Draw, edit, and manage delivery zones with a typed schema and a data table. Every zone carries a pickup/drop SLA, service status, and vehicle class.
A map editor that fits field-team workflows.
Field teams collecting geographic data need typed forms, offline-friendly data out, and a map that works with any tile source. That's Element Editor.
Draw geofences with real data behind them.
Draw geofences in the browser, export standard GeoJSON, trigger your backend when devices enter or exit. Typed properties per fence.
A GIS editor for the rest of the team.
A browser-based GIS editor for the rest of the team. Typed attribute schemas, boolean operations, geometry processing, GeoJSON in and out.
Property boundaries that line up, with the data attached.
A property-boundary editor for parcel data, cadastral work, and real-estate tools. Snap to adjacent parcels, attach typed owner/area data, export clean GeoJSON.
Route planning that follows actual roads.
Plan routes on web maps — road-snapped LineStrings, typed waypoint data, measurable distance. Works with MapLibre, Mapbox, and Leaflet.