Can I call geolith Routing today?

No. There is no routing endpoint on geolith.app or api.geolith.app, no routing plan and no routing key. The hosted API offers geocoding and vector tiles (India tile set today; planet tiles in development) only.

Will my Valhalla client work?

That is the design: the request and response bodies are Valhalla’s. Two things change: the base URL, and the paths, which are kebab-case (/sources-to-targets, /trace-route, /trace-attributes).

Routing · In development

Routing from one file, with a Valhalla-compatible API

Q: When will it be offered?

There is no date. 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. Progress is tracked at https://docs.geolith.app/routing/status.

geolith Routing is a routing engine with Valhalla-compatible endpoints: /route, /sources-to-targets, /isochrone, /trace-route, /trace-attributes, for auto, pedestrian and bicycle. It answers from the routing part of a .glx file that geolith's builder writes, read in ranges, so it needs no database. On Berlin its JSON responses are byte-identical to the reference engine (Valhalla 3.9.1) on every measured request.

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 docs See status and roadmap

Definition

What is geolith Routing?

geolith Routing is a routing engine in development. The geolith builder turns OpenStreetMap into a road graph and writes it as the routing part of a .glx file; the router reads only the parts of that file a request touches and answers in Valhalla’s request and response shapes, on kebab-case paths. It is not deployed: there is no hosted endpoint, plan or key for it.

Detail

Status

Where routing stands on geolith/routing main. Nothing below is deployed.

Done: the builder. geolith --output-format routing writes the routing part of a .glx file from OpenStreetMap, with historical speeds from --routing-predicted-speeds.

Done: the router answers /route, /sources-to-targets, /isochrone, /trace-route, /trace-attributes for auto, pedestrian and bicycle, byte-identical to the reference on Berlin.

Done: traffic. Historical (predicted) speeds from the file, and live speeds and closures supplied by the program that runs the router.

In progress: a test Cloudflare Worker runs the router on a geolith-built Berlin file. It is not public and not ready to offer.

In progress: spoken (verbal_*) instructions.

Not started: a public deploy, a hosted API, plans and prices. 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

Endpoints

Valhalla’s request and response bodies, on kebab-case paths (Valhalla’s /sources_to_targets is /sources-to-targets here).

/route: A route between two or more points.

/sources-to-targets: A matrix of times and distances between sources and targets.

/isochrone: The area reachable within a time or a distance.

/trace-route: Map matching: a GPS trace snapped to roads, as a route.

/trace-attributes: Map matching: the road attributes along a GPS trace.

Detail

How it works

One file, no database. The router keeps the tile index in memory and fetches only the blocks a request touches.

The geolith builder turns OpenStreetMap into routing graph tiles and writes them as the routing part of a .glx file.

Each graph tile is cut into 64 KiB blocks, each its own zstd frame, so a router reads only the blocks a search touches.

The router is pure Rust with no I/O of its own: built to WebAssembly for a Cloudflare Worker reading from R2, or run next to a local file.

The router and tile format are ported from Valhalla 3.9.1 (MIT).

Detail

How it fits with search and tiles

The same builder writes all three. A .glx file holds parts: a search part for geolith Search and a routing part for routing. Vector tiles ship as .pmtiles. Search and tiles (India tile set today; planet tiles in development) are live at api.geolith.app today; routing is not.

geolith Search answers from the search part of a .glx file (live).

Vector tiles are served from a .pmtiles file (live; India tile set today; planet tiles in development).

geolith Routing answers from the routing part of a .glx file (in development, not deployed).

Routing · In development · not deployed

Request shapes

Valhalla request bodies. ROUTER_HOST stands for a router you run; there is no hosted endpoint.

curl -X POST "https://ROUTER_HOST/route" \
  -H "Content-Type: application/json" \
  -d '{
    "locations": [
      { "lat": 52.5163, "lon": 13.3777 },
      { "lat": 52.5079, "lon": 13.3376 }
    ],
    "costing": "auto",
    "units": "kilometers"
  }'

curl -X POST "https://ROUTER_HOST/sources-to-targets" \
  -H "Content-Type: application/json" \
  -d '{
    "sources": [{ "lat": 52.5163, "lon": 13.3777 }],
    "targets": [
      { "lat": 52.5079, "lon": 13.3376 },
      { "lat": 52.5200, "lon": 13.4050 }
    ],
    "costing": "auto"
  }'

curl -X POST "https://ROUTER_HOST/isochrone" \
  -H "Content-Type: application/json" \
  -d '{
    "locations": [{ "lat": 52.5163, "lon": 13.3777 }],
    "costing": "bicycle",
    "contours": [{ "time": 10 }, { "time": 20 }],
    "polygons": true
  }'

curl -X POST "https://ROUTER_HOST/trace-attributes" \
  -H "Content-Type: application/json" \
  -d '{
    "shape": [
      { "lat": 52.5163, "lon": 13.3777 },
      { "lat": 52.5150, "lon": 13.3690 },
      { "lat": 52.5120, "lon": 13.3550 }
    ],
    "costing": "auto",
    "shape_match": "map_snap"
  }'

Routing · In development

Endpoints, traffic, self-hosting and accuracy

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

Solutions · In development

What routing is for

Delivery route planningRoutes and time matrices for delivery runs.Read →ETAs and service areasArrival times and isochrone delivery zones.Read →Fleet GPS map matchingSnap vehicle GPS traces to the roads they drove.Read →Cab dispatch with live speedsDispatch on speeds from your own drivers’ pings.Read →

Questions

Routing: questions

Sources

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

Read the routing docs See status and roadmap