Skip to content
geolith

Solution · Routing · In development

Fleet GPS, snapped to the road

GPS from a moving vehicle is noisy and sparse. /trace-route returns the route the vehicle drove; /trace-attributes returns the roads under the trace with their attributes.

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

Fleet GPS map matching

Snap vehicle GPS traces to the roads they drove.

Berlin, byte-identical to Valhalla 3.9.1: 160/160 trace requests.

Detail

Where routing fits

Map matching sits between the raw pings and your reports.

Distance driven: the matched route’s length, not the zigzag between noisy points.
Trip labels: the road names and classes a trip used, from /trace-attributes.
Traffic from your own fleet: matched pings give per-road speeds you can pass to the router (see Traffic and live data).

Solutions · In development

More solutions

Delivery route planningRoutes and time matrices for delivery runs.ETAs and service areasArrival times and isochrone delivery zones.Cab dispatch with live speedsDispatch on speeds from your own drivers’ pings.

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