Guides
Guides
  1. HERE Anonymizer Self-Hosted User Guide
  2. Concepts
  3. Anonymization features

Route tracking

Route tracking allows using the vehicle's planned route to improve privacy protection and unlock additional insights.

When route tracking is enabled, HERE Anonymizer Self-Hosted can perform the following actions:

  • Track the vehicle's progress against the supplied planned route.
  • Detect deviations from the planned route, which include missed waypoints and waypoints where the vehicle arrived early or late.
  • Apply configurable anonymization strategies when deviations from the planned route are detected.

This feature is supported only in the streaming mode.

Key concepts

Planned route

A planned route is imported into the Anonymizer, from sources such as:

  • Fleet / T&L (Transport and Logistics) optimization software
  • In‑vehicle navigation
  • Mobile navigation apps

Planned routes used with route tracking typically contain:

  • Path the vehicle is expected to follow
  • Waypoints
  • Optional ETAs (Estimated Time of Arrival) for each waypoint
  • Buffer distances around the route and waypoints to account for GPS inaccuracies and minor deviations

Waypoint

Waypoints are locations the planned route must traverse. They can be used to track the progress of the journey and to determine if the vehicle follows the planned route.

A waypoint definition typically includes:

  • Geographical coordinates (latitude and longitude)
  • ETA (Estimated Time of Arrival)
  • Buffer distance (to account for GPS inaccuracies and minor deviations)

Route corridor

A route corridor is a geographical buffer around the planned route.

When the vehicle stays in the route corridor, it's considered "on route". When the vehicle leaves the route and the route corridor, the system detects a deviation and applies the configured anonymization strategy for the traces generated outside of the route corridor.

Deviation detection

Deviation detection is the process of checking the vehicle's current position against the provided planned route.

  • Has the vehicle left the route corridor and how far has it gone?
  • Has the vehicle returned to the route corridor after a deviation?
  • Has a waypoint been reached? Has it been reached on time, early, or late?
  • Have any waypoints been skipped?

A stream of probe points is consumed and evaluated against:

  • The route corridor (the linestring geometry and its allowed spatial tolerance)
  • The configured waypoints (the point geometries with their ETAs)

Deviation detection is typically invoked for each incoming probe point. Based on the results of the evaluation, zero or more deviation events per point can be emitted. These events are consumed by downstream components.

Route deviation event

The event emitted by Deviation detection is RouteDeviationEvent. All deviation events share a common type "routeDeviation". Specific situations are specified through subtypes:

  • SUBTYPE_LEFT_THE_CORRIDOR (leftTheCorridor)
  • SUBTYPE_BACK_TO_CORRIDOR (backToCorridor)
  • SUBTYPE_WAYPOINT_REACHED_ON_TIME (wayPointReachedOnTime)
  • SUBTYPE_WAYPOINT_REACHED_LATE (wayPointReachedLate)
  • SUBTYPE_WAYPOINT_REACHED_EARLY (wayPointReachedEarly)
  • SUBTYPE_WAYPOINTS_SKIPPED (wayPointsSkipped)

Every RouteDeviationEvent contains the following key fields and attributes:

  • coordinates: The location where the event was raised.
  • timestamp: The time when the event was raised.
  • reachedOrSkippedWaypoints: A list of waypoints that were reached or skipped as part of this event.
  • extendedAttributes:
    • Route ID: The identifier of the route associated with the event.
    • Maximum Spatial Deviation: Maximum deviation from the route corridor, expressed in meters.
    • Reached or Skipped Waypoints : A list of waypoints that were reached or skipped as part of this event.

Configuration

To learn how to enable and configure this feature, see Route tracking configuration and Route GeoJSON file format.

📘

Note

Probe points must contain a reached timestamp and a routeId defined in their extended attributes. This routeId must match the routeId defined in the route GeoJSON file. These fields are necessary for evaluating probe points against a route for any deviation.

Updated 11 hours ago