Skip to content
geolith

Routing · Accuracy · In development

Routing accuracy: the same answers as Valhalla on Berlin

On Berlin, with the same data and the same requests, geolith’s router returned JSON byte-identical to the reference engine (Valhalla 3.9.1) on every measured request: routes, matrices, isochrones, map matching and traffic. The tables below give the count for each set.

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.

Read the routing docsSee status and roadmap

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.

Route · /route · Berlin, byte-identical to Valhalla 3.9.1
SetRequests Byte-identical
Auto100100/100
Pedestrian3030/30
Bicycle3030/30
Matrix · /sources-to-targets · Berlin, byte-identical to Valhalla 3.9.1
SetRequests Byte-identical
Matrices6060/60
Isochrones · /isochrone · Berlin, byte-identical to Valhalla 3.9.1
SetRequests Byte-identical
Isochrones4545/45
Map matching · /trace-route and /trace-attributes · Berlin, byte-identical to Valhalla 3.9.1
SetRequests Byte-identical
Trace requests160160/160
Traffic · /route with a date_time · Berlin, byte-identical to Valhalla 3.9.1
SetRequests Byte-identical
Historical (predicted) speeds5050/50
Live speeds3030/30
Closures55/5

Detail

What "matching" means

A response matches when its JSON is byte-identical to the reference’s for the same request on the same data. Spoken (verbal_*) instructions are in progress and not part of the check.

Detail

What has to happen before routing is offered

Nothing is offered until a deployed server answers real requests from files geolith builds and passes the 100-route gate: route length within 2% and duration within 5% on at least 95 of 100 routes, and no route the reference finds that geolith does not.

Detail

What is not measured

No speed, latency or cost figures are published. They will be measured on a deployed server, the same way for geolith and the reference, before anything is offered.

Routing · In development

More on routing

Routing overviewA Valhalla-compatible router that answers from a .glx file.Route APIValhalla-compatible /route for auto, pedestrian and bicycle.Matrix/sources-to-targets: times and distances between many points.Isochrones/isochrone: the area reachable within a time or a distance.Map matching/trace-route and /trace-attributes: GPS traces snapped to roads.Traffic & live dataHistorical speeds in the file; live speeds and closures from you.Self-hostingOne .glx file, in a Worker on R2 or next to a local file.Routing guidesBuild a routing .glx, self-host the router, migrate a Valhalla client.

Sources

  1. Routing: status and roadmap, geolith docs (read 2026-11-08)
  2. 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.

Read the routing docsSee status and roadmap