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

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

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

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

## Sources

1. [Routing API (planned)](https://docs.geolith.app/routing/api), 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