Protocols

Engine responsible for detecting arrival at the destination.

Responsible for generation of Guidance and LaneGuidance related to upcoming road maneuvers.

The protocol for a Guidance Instruction.

Contains a set of attributes common to all GuidanceInstructions. It contains a set of default attributes common to all GuidanceInstruction‘s.

e.g., 'Turn right’, ‘Keep left’, ‘Take the ferry’, ‘Take the motorway’, ‘Arrive’.

Different types of GuidanceInstruction‘s will implement this, and may add extra attributes specific to the Instruction type.

e.g., TurnInstruction will contain turnAngleInDegrees and turnDirection.

The LocationContextProviderEngine protocol provides functionality related to information about a matched location.

The ManageableEngine protocol provides functionality related to engine data management.

The MapMatchingEngine provides an interface for map matching functionality.

The RouteProgressProviderEngine protocol provides functionality related to the calculation of progress along the route.

The RouteProjectionEngine is responsible for projecting the input route to obtain map references if they are not provided.

Selector responsible for choosing the routes according to protocol’s adoptee expectations

Engine responsible for replanning a route.

The RouteTrackingEngine protocol provides functionality to determine if the driver is tracking the routes.

Defines the interface to horizon elements.

Protocol that defines a horizon attribute data for onboard, online and hybrid implementations

Protocol that defines a horizon path osition for onboard, online and hybrid implementations

Defines the interface to the horizon engine. The horizon engine generates vehicle horizon data based on previously registered horizon subscription options, which define the length of the horizon paths and what map data is collected for these paths. The client of the horizon engine can register multiple sets of horizon subscription options and request the engine to provide horizon data for all or some of these sets of options. The client of the engine can also update the subscription by registering a new set of subscription options or unregistering a previously registered set.

Interface to the path search policy. The path search policy specifies whether the horizon engine must search along the entire route or within a user-defined distance.