Routing · Traffic · In development
Traffic: historical speeds in the file, live speeds from you
A request with a date_time uses historical (predicted) speeds by time of week, built into the file, and live speeds and closures that you supply. geolith does not collect or sell traffic data. On Berlin every measured response was byte-identical to Valhalla 3.9.1.
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.
Berlin · same data, same requests
Against the reference engine
Measured on geolith/routing main. Only sets that were run are shown; no speed or cost is measured.
| Set | Requests | Byte-identical |
|---|---|---|
| Historical (predicted) speeds | 50 | 50/50 |
| Live speeds | 30 | 30/30 |
| Closures | 5 | 5/5 |
Detail
Historical speeds
Pass a directory of CSV files, one per graph tile, in the format of Valhalla’s valhalla_add_predicted_traffic tool. Data that already targets Valhalla works unchanged.
Detail
Live speeds and closures
Live speeds and closures are passed to the router by the program that runs it, beside the .glx file, never inside it, so the file stays immutable. A live speed counts fully at the start of the route and fades out over the first hour of travel time. A request without a date_time uses neither.
Routing · In development
More on routing
Sources
- Routing: traffic and live data, geolith docs (read 2026-11-08)
- Valhalla turn-by-turn API reference, Valhalla (open source, MIT) (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.