Automatic Detections with Forced Trips
This document refers to deprecated parts of the platform and has been left intact to help customers with legacy integrations. In order to access the latest platform features and documentation, please go to https://docs.sentiance.com.
While in automatic detection mode, the SDK can be forced to start a trip. Doing so will prevent the SDK from detecting stationary moments and force it to continue collecting trip data until the trip is explicitly stopped.
Once the forced trip is stopped, the SDK will resume automatic detections.
Starting a Trip
You can start a trip as follows:
The metadata
is an NSDictionary
representing a map of string to string types. You can use it to attach any piece of information to this trip. The transportModeHint
is a hint you can give the SDK about the type of transport the trip is (e.g. car, bicycle, etc.).
In case starting a trip fails, you can check the SENTSDKStatus
object to determine the reason.
Stopping a Trip
To stop a trip that you've started, call stopTrip
as follows:
If stopping the trip fails, you can check the SENTSDKStatus
to determine why. Note that if no trip was ongoing, failure
will be called as well.
To check if a trip is ongoing before calling stopTrip
, see this guide.
Last updated