Solution · Routing · In development
Cab dispatch on your own drivers’ speeds
Dispatch asks which free driver reaches a rider first. /sources-to-targets answers it, with drivers as sources, the rider as the target and live speeds that you supply.
Status · In development
In development, not deployed: there is no routing endpoint to call yet, on geolith.app or api.geolith.app, and no routing plan, price or key.
Cab dispatch with live speeds
Dispatch on speeds from your own drivers’ pings.
Berlin, byte-identical to Valhalla 3.9.1: 50/50 historical (predicted) speeds, 30/30 live speeds, 5/5 closures.
Detail
Where routing fits
Your pings, your speeds, your router.
Pings to speeds: map-match each driver’s recent pings and aggregate a speed per road (your code).
Speeds to router: pass the live speeds and closures to the router you run, beside the .glx file.
Dispatch: /sources-to-targets from free drivers to the rider, with a date_time so live speeds apply.
geolith does not collect, share or sell your pings; a hosted live overlay is planned, not built.
Solutions · In development
More solutions
Sources
- Routing: traffic and live data, geolith docs (read 2026-11-08)
- Routing API (planned), geolith docs (read 2026-11-08)
Routing · In development
Follow routing progress.
Read how the router works today and what has to pass before it is deployed.