For the complete documentation index, see llms.txt. This page is also available as Markdown.

Driving Score Validity

Score range

Driving Scores are represented on a scale from 0 to 1. A higher score indicates safer driving behavior.

In some situations the score cannot be determined and the result will be of a null value: null / nil depending on the platform.

Minimum trip requirements

As a general guideline, a trip should be at least 2 km long and last at least 3 minutes, and the user's geofence must be breached for active data collection can begin.

Scores are calculated once the transport has been completed, based on the driving events detected during the trip.

If the trip is too short in duration, and/or the sensor or location data is missing or unreliable, the scores cannot be calculated. In that case, they'll be indicated with null / nil.

Score is null or nil

A score of null or nil means the SDK was unable to compute the score for that trip.

This typically happens when:

  • The trip was too short in duration or distance to collect enough data for a reliable score.

  • The location or sensor data was poor quality, for example because of a weak GPS signal or excessive noise in the sensor data.

Summary

Value
Meaning

0 - 1

Valid score, with 0 indicating least safe driving detected and 1 being the highest.

null / nil

Score could not be computed due to

  • Trip too short in duration

  • missing/unreliable sensor or location data

Last updated