Electronic horizon
Probable path and structured road-ahead attributes for an approved consumer ECU or function.
Use route-ahead map attributes to extend awareness beyond line of sight and support predictive driver-assistance, energy and vehicle-control functions within the OEM safety architecture.
Capability labels below describe public or configurable scope. The status note makes program dependence visible before a technical commitment.
Probable path and structured road-ahead attributes for an approved consumer ECU or function.
Map inputs for display, warnings, ISA and traffic-sign assistance as allocated by program.
Preview for curve-speed warning, lighting, predictive cruise, gearing and energy management.
Road type, lane structure, transitions, tunnels, tolls and special structures.
Incident, queue, work-zone and closure information where an entitled live feed exists.
High-precision lane geometry, connectivity, merges, splits and selected attributes.
Surveyed road furniture and map objects usable by approved localization or perception systems.
LiDAR, camera and high-accuracy GNSS collection with extraction, conflation and validation.
Industry map and eHorizon interface families, profile and release validated per integration.
Custom map and scenario assets for virtual validation and regression workflows.
Route-ahead context and a versioned map interface inside the function architecture.
Predictive curve, slope and road-state inputs for comfort and efficiency.
Traceable corridor, version, freshness and scenario evidence.
ODD, corridor coverage, freshness and failure behavior are explicitly declared.
Responsibility is allocated across Mappls, OEM, Tier 1, sensor and cloud providers.
Safety use may require ISO 26262, SOTIF and cybersecurity evidence.
Safety-relevant content needs provenance, anomaly handling and rollback.
Capture the vehicle, territory, surfaces and adjacent modules. The output becomes the starting point for a capability and interface workshop.