Match before you score
Snap up to 50 000 points per request with a confidence value, so a trace through an urban canyon is flagged rather than silently mis-scored.
Insurance & telematics
A speeding event needs to know the speed limit.
Telematics scoring falls apart without road context. Map matching snaps the trace to a link and hands back the limit, the functional class and the name — which is what turns a raw accelerometer spike into an underwriting signal.
How it is usually put together
Attach the context
Speed limit, functional class and name come back with the matched link. The event is then explainable to a customer disputing it.
Geocode the claim
Reverse geocoding with an access position resolves where the incident actually happened, not the nearest rooftop.
A modelled month
$91,556.04 you keep
Illustrative volumes for a business of this shape, priced with the same calculator as the pricing page. Both columns apply the free allowances first.
| Service | Monthly volume | On HERE's list price | On ApiNavi |
|---|---|---|---|
| Geocoding & search | 2.4M | $2,085.60 | $1,042.80 |
| Routing | 800K | $1,192.50 | $596.25 |
| Matrix routing | 1.8M | $8,987.50 | $4,493.75 |
| Traffic | 1.2M | $2,993.75 | $1,496.88 |
| per month | $15,259.35 | $7,629.68 |
These volumes are modelled, not measured from a customer. They exist so the arithmetic is visible — put your own numbers into the calculator.
What to watch
- Map matching bills from the matrix meter — model it as requests, not as points
- Speed limits are attribute data, not observation: coverage varies by country and the coverage page lists it
- Retaining raw traces has data-protection consequences; the DPA covers what we process and for how long
Run your own numbers
The calculator takes your call volumes and prints both columns.