Routing · Matrix · In development
Matrix: times and distances from every source to every target
/sources-to-targets returns the travel time and distance from each source to each target in Valhalla’s body. It is the input a dispatch or route-planning tool needs. On Berlin the responses were byte-identical to Valhalla 3.9.1 on 60/60 matrices.
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 |
|---|---|---|
| Matrices | 60 | 60/60 |
Detail
Request
sources and targets are lists of points; costing is auto, pedestrian or bicycle. The path is kebab-case: Valhalla’s /sources_to_targets is /sources-to-targets here.
Detail
Response
Valhalla’s sources_to_targets: one row per source, one cell per target, each with time, distance, from_index and to_index.
Detail
What it is not
The matrix gives the costs; it does not choose a visiting order. A route optimizer (your own, or an open-source solver) takes the matrix and returns the order.
Routing · In development
More on routing
Sources
- Routing API (planned), 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.