​

HERE Reverse Geocoding

Reverse geocoding converts coordinates into the nearest address. It is conceptually the simplest endpoint on the platform and, for fleet and telematics products, the most reliably mis-implemented. The reason is structural: GPS pings arrive at a fixed rate whether anyone needs an address or not.

​

What problem this guide solves

A vehicle emits a position every ten seconds. Over a nine-hour shift that is 3,240 pings. Across 200 vehicles, 648,000 pings a day. If your platform reverse-geocodes each one, you are billing 648,000 transactions daily to answer a question almost nobody asked. The address is needed when a human looks at a screen, when a stop is detected, or when a report is generated. Not on arrival of every packet.

​

When to use reverse geocoding

• Rendering a human-readable location for a selected vehicle
• Labelling detected stops, arrivals, and departures
• Enriching telematics events for reports or compliance records
• Geofence entry and exit annotation
• Turning a map click into an address

​

When NOT to use it

• Every telematics ping. Geocode on demand, or on stop detection. Not on ingest.
• Snapping a trace to the road network. That is Route Matching, a different API. Reverse geocoding gives you an address, not a road segment. If an auditor asks which road the vehicle travelled, reverse geocoding cannot answer.
• Coordinates you already resolved. Vehicles idle. A hundred pings at the same depot resolve to the same address.
• Determining whether a point is inside a zone. That is a spatial containment problem, solved in your own database with a polygon, not by resolving an address and comparing strings.

​

The endpoints

Both belong to Geocoding & Search v7. For batch workloads with no latency requirement, the Batch API v7 supports reverse geocoding as a job — cheaper per record than real-time.

​

Key concepts

A returned address is a nearest match, not a truth. The coordinate sits somewhere. HERE returns the closest addressable feature. In a rural area that may be several hundred metres away and on a different property. Drive direction improves street matching. HERE supports considering the vehicle’s heading when snapping to a street. On a divided highway, a coordinate 15 metres from the centreline can resolve to either carriageway. Heading disambiguates. For fleet products this materially reduces “the truck is on the wrong side of the interstate” support tickets. Micro Point Address snapping improves accuracy where that data exists. HERE documents this as a distinct capability. Spatial filters limit results. A circular filter constrains candidates to a radius. Without one, a coordinate in the ocean returns something eventually. Result types are filterable. A coordinate near a shopping centre may resolve to the place, not the street address. If you need a street address, filter for one. Political views apply here too. Disputed territory labelling is a product and legal decision.

​

Production architecture

Detect stops, then geocode. The event worth an address is “vehicle stationary for four minutes,” not “vehicle emitted a packet.” One address per stop, not 24 per stop. Geocode lazily on view. A dispatcher watching one vehicle needs one address. Do not pre-resolve the other 199. Cache by rounded coordinate. Round to roughly 5 decimal places — about one metre — and cache. A vehicle idling at a depot generates hundreds of pings within a metre of each other. One lookup. Cache depot and customer locations permanently. They are known, fixed, and finite. Resolve them once at onboarding. Batch the historical backfill. Enriching six months of trip history is a job, not a stream of real-time calls. Pass heading where telematics provides it. Free accuracy.

​

Cost and usage considerations

Each reverse-geocode request is one billable transaction. POST /multi-revgeocode resolves a list in one request — check how your entitlement meters it before assuming it is one transaction for the whole list. Where teams overspend:

• Geocoding every ping on ingest. The dominant cost, by an order of magnitude.
• Looping /revgeocode instead of using /multi-revgeocode.
• No coordinate rounding or caching. Idle vehicles bill continuously.
• Real-time calls for historical backfill. Use the Batch API.
• Re-resolving fixed depot coordinates.

This is the workload where geocoding-heavy savings versus Google reach their maximum — but only after the call pattern is fixed. Migrating an ingest-time reverse geocoder to HERE reduces the bill without fixing the architecture. Fix the architecture first; the platform decision is easier afterwards. See HERE Pricing Explained.

​

Common mistakes

Reverse-geocoding on packet ingest. Geocode events, not packets. Looping single-coordinate calls over a list. Use /multi-revgeocode. No coordinate rounding before cache lookup. Sub-metre GPS jitter defeats an exact-match cache. Ignoring heading. Wrong carriageway, wrong street, support ticket. Using reverse geocoding to snap a GPS trace to roads. That is Route Matching. Using reverse geocoding for geofence containment. That is a spatial query. Storing the nearest address as the vehicle’s true location. It is a nearest match. Store the coordinate too. Real-time endpoints for historical enrichment. Batch it.

​

Best practices

• Trigger on stop detection, not on ping arrival
• Use POST /multi-revgeocode for lists
• Round coordinates to ~5 decimal places and cache
• Resolve depots and customer sites once, permanently
• Pass drive direction when available
• Apply spatial filters and result-type filters
• Batch all historical enrichment
• Persist the original coordinate alongside the resolved address

​

API reference

• Reverse geocode endpoint
• Multi-reverse geocode
• Batch API reverse geocoding
• Drive-direction and Micro Point Address snapping are documented within the Geocoding & Search v7 developer guide

​

Related guides

Also: Authentication · Choosing the Right HERE APIs

---

Need production HERE API keys or implementation support? Placematic is an official HERE Technologies reseller and implementation partner helping companies choose the right HERE APIs, estimate usage, migrate from Google Maps and build production-ready geospatial solutions. Talk to us.