# 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, not deployed: there is no routing endpoint to call yet, on geolith.app or api.geolith.app, and no routing plan, price or key.

## Route (/route) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Auto | 100 | 100/100 |
| Pedestrian | 30 | 30/30 |
| Bicycle | 30 | 30/30 |

## Matrix (/sources-to-targets) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Matrices | 60 | 60/60 |

## Isochrones (/isochrone) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Isochrones | 45 | 45/45 |

## Map matching (/trace-route and /trace-attributes) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Trace requests | 160 | 160/160 |

## Traffic (/route with a date_time) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Historical (predicted) speeds | 50 | 50/50 |
| Live speeds | 30 | 30/30 |
| Closures | 5 | 5/5 |

## 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.

## 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.

## 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.

## Sources

1. [Routing: status and roadmap](https://docs.geolith.app/routing/status), geolith docs (read 2026-11-08)
2. [Valhalla turn-by-turn API reference](https://valhalla.github.io/valhalla/api/turn-by-turn/api-reference/), Valhalla (open source, MIT) (read 2026-11-08)

Routing is in development and not deployed; there is no endpoint to call yet, and no routing plan, price or key. Read the routing docs: https://docs.geolith.app/routing