Advanced configuration

Custom stop timeout

A trip being analyzed is automatically stopped after a period of inactivity (which begins when the vehicle has stopped). The DriveQuant SDK allows to set the end-of-trip duration.
By default, the trip analysis is stopped after 240 seconds. This value can be tuned according to your need and you can choose any integer values between 120 and 480 seconds by calling the following method:
DriveKitTripAnalysis.shared.setStopTimeOut(timeOut: 180)
If a value greater than 480 is set, the value will be forced to 480.
If a value lower than 120 is set, the value will be forced to 120.

Sharing data during the trip

The Trip Analysis SDK records the trip locally while it is in progress. The data are recorded with a period of one point per second. At the end of the trip, the SDK requests the driving analysis service and then retrieves the driving indicators.
In addition to this feature, the SDK is also able to share data with the server before the journey is completed. The data is transmitted at a lower frequency with a time interval of one point per minute.
The system for sharing information during the trip can be used in a vehicle fleet management system. This feature requires access to specific APIs. For more information, contact DriveQuant.
Sharing information with the server allows you to store the trip data even if it's been interrupted and the data post could not be performed at the end of the trip. This can happen in very rare cases such as the destruction of the mobile phone for instance.
By default, this setting is disabled but you can enable it by calling the following method:
DriveKitTripAnalysis.shared.enableSharePosition(enable: true)
To disable this setting, call the same method with the parameter set to false
DriveKitTripAnalysis.shared.enableSharePosition(enable: false)
Here is the list of data shared every minute by the SDK:
  • Date of trip start.
  • Duration of the trip in seconds.
  • Distance traveled in km.
  • Longitude of the current location.
  • Latitude of the current location.
  • Smartphone battery level.
  • Start-Mode for trip recording: manual, GPS-based or beacon-based.
  • Beacon parameters: uuid, major, minor.

Access the trip trigger events

Why use trip triggers?

DriveKit's automatic start mode detects a trip and launches its recording immediately. This operating mode may not be appropriate for all use cases.
Your application may require other information or business logic before enabling the trip recording. For example, it may be appropriate to check that:
  • A connected device is near to the smartphone.
  • The trip recording is acceptable in a given time slot.
In this case, you may want to subscribe to the events that are indicative of the trip start but not necessarily launch the GPS sensor and the trip analysis.
This is why DriveKit allows you to subscribe to trigger events that indicate that a trip has probably started.

How does it work?

By default, this feature is disabled.
To enable this feature, DriveKit Trip Analysis should not be configured in automatic mode but in manual mode.
If DriveKit Trip Analysis is set to automatic mode, the trip will be recorded.
If DriveKit Trip Analysis is set to manual mode and you follow the instructions below, you will be able to listen for trip start trigger events but the trip analysis will not be started automatically.
To listen to trigger events that indicate a start of trip, even if the autostart is disabled, you can call the following method:
DriveKitTripAnalysis.shared.monitorPotentialTripStart = true
Once the feature is enabled, events will be available in the TripListener potentialTripStart() where you initialize the TripAnalysis component:
DriveKitTripAnalysis.shared.initialize(tripListener: MyTripListener(), appLaunchOptions: launchOptions)
struct MyTripListener : TripListener {
func potentialTripStart(startMode: StartMode) {
The potentialTripStart() method can return all StartMode values ; except MANUAL.
Indeed, a trip manually started is considered as confirmed.