Drivers
Experience steadier, more credible map position and rerouting.
AutoBuild your programEmbedded software
Location Runtime
A confidence-aware vehicle position that survives difficult roads and signals.
Fuse GNSS and approved dead-reckoning inputs, distinguish raw and matched position, expose quality, and recover through tunnels, urban canyons, flyover overlap and weak-signal conditions.
Value by stakeholder
Built around measurable operating outcomes.
Each product is shaped around the team that buys, integrates, operates or experiences it—not an isolated feature checklist.
ADAS/navigation engineers
Consume explicit confidence instead of a black-box dot.
Support
Replay the same sensor/map/runtime combination.
Capability system
What the product is designed to do.
Final scope, data, territory, vehicle interfaces, performance and availability are confirmed for each OEM program.
Sensor ingestion
Normalize GNSS, IMU, wheel/speed and approved vehicle inputs.
Fusion & confidence
Estimate position, motion and uncertainty with source/quality state.
Map matching
Associate position to road/lane candidates using vehicle/profile context.
Route positioning
Locate progress on the active route without corrupting raw evidence.
Recovery
Handle cold/warm start, signal loss, ambiguity and reacquisition.
Replay & diagnostics
Record privacy-safe evidence for deterministic issue reproduction.
Delivery choices
Fit the OEM ownership model.
- ✓Portable C++/Rust runtime
- ✓Platform and sensor adapter kit
- ✓Replay/conformance tools and calibration service
Program guardrails
Claims stay attached to evidence.
- !Raw, fused, matched and displayed positions remain distinct
- !Timeout and invalidity rules follow the signal contract
- !Performance is validated by scenario and territory
OEM program workshop
Define the production shape of Location Runtime.
Capture the vehicle line, territory, users, surfaces, interfaces, deployment, validation and lifecycle. The result becomes a focused OEM discovery brief.