Skip to content
geolith

Solution · Routing · In development

Delivery route planning from one routing file

A delivery run needs the time and distance between every pair of stops (/sources-to-targets) and the driving route for the chosen order (/route). geolith Routing answers both in Valhalla’s bodies.

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

Delivery route planning

Routes and time matrices for delivery runs.

Berlin, byte-identical to Valhalla 3.9.1: 60/60 matrices; 100/100 auto, 30/30 pedestrian, 30/30 bicycle.

Detail

Where routing fits

Geocode the addresses with geolith Search (live), then route.

Order intake: /v1/search turns each address into coordinates (geolith Search, live today).
Planning: /sources-to-targets gives the time matrix between depot and stops (in development).
Order: your optimizer, or an open-source solver, picks the visiting order from the matrix. geolith does not solve the order.
Driving: /route returns the route and turn-by-turn maneuvers for that order (in development).

Solutions · In development

More solutions

ETAs and service areasArrival times and isochrone delivery zones.Fleet GPS map matchingSnap vehicle GPS traces to the roads they drove.Cab dispatch with live speedsDispatch on speeds from your own drivers’ pings.

Questions

Delivery route planning: questions

Sources

  1. Routing API (planned), 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