Mobility. Behavior. Intelligence.
Open Location and Mobility API/SDK for Rich Driver Behavior Analytics

TL KIT/OPEN API supports apps to automatically detect the start of a drive, and accurately monitors the driving behavior from any smart phone. Our patented mobility and sensor fusion technology allows reliable drive-data collection with minimal battery impact. The rich mobility data will be pre-computed on the device and uploaded into our backend, allowing for data analytics and comprehensive driver-risk scoring.

Driver Behavior Analytics App

Data points gathered include:

  • Start: date, time, place
  • Braking
  • Acceleration
  • Turning
  • End: date, time, place
  • Direction: North, East, South, West
  • Route
TL Open SDK/API Overview
Mobility SDK location drive analytics
Powerful Features in TL Open SDK/API

Here at Tourmaline Labs™, we build powerful, smart, and comprehensive features into our TL Open SDK/API platform. Here you can see how each app delivers total performance features.

TL Trip
  • 24/7 Location awareness
  • Distance/hours driven/time of day
  • Mobility detection & recording
  • Reverse geocoding - address
  • Start/stop time
  • Trip & activity dashboards
  • Turn-by-turn route
TL Behavior
  • 30-dimensional driver behavior (output)
  • Advanced calibration & normalization
  • Driver behavior events & scoring
  • Driver & phone usage alerts
  • Fleet & driving behavior dashboard
TL Insight
  • Contextual mobility behavior intelligence (N)
  • Crash detection intelligence
  • Driver & mobility behavior - benchmarking
  • Intelligence modules & dashboards
  • Mobility environment intelligence
TL KIT/OPEN API Example #1: Automatic Drive Detection

Do you have an app that would benefit from accurately detecting that your users are driving, what time of day and to where?

Extracting this location and time data from from different devices using different platforms is difficult, costly and typically consumes a lot of battery power.

Driver Behavior Analytics App

TL KIT/OPEN API provides SDK APIs to receive location and drive information:

  • after the start of a ride (backdated to the startpoint of the ride)
  • after the end of a ride (backdated to the start­ and endpoint of the ride)
  • with route information, including date and time travelled
TL KIT/OPEN API Example #2: Always On Location

You think location matters? We think so too! Apps often rely on location information to the benefit of the user experience. However, retrieving location data comes at a price - typically it comes with heavy battery consumption. Regardless of the brand and model of the device, minimizing location sampling while providing accurate positioning is difficult, time-consuming, and costly to develop.

Drive Detection App

TL KIT/OPEN API provides SDK APIs to receive location information

  • Upon request
  • At specified time intervals
  • Once a predefined distance has been travelled
  • Once a predefined time interval has passed with no movement
Why Us and Not Native Location API?

Our SDK is always on, and consumes a fraction of the battery power compared to other products. Power consumption is minimized by using our patent pending sensor calibration. Benefit from our analysis tool and get insights into your user data.

TL KIT/OPEN API Example #3: Activity Recognition

Automatically recognize and record any driving, walking and periods of no movement done by your users. This ultra low power consumption tool is ready to be integrated in your app. View start and end times; place, duration and route for each activity. The SDK is always on, so there’s no need to start and stop it. End users of your app will benefit from enhanced activity recognition and location data features.

Always On Location SDK

Data points gathered include:

  • Start: date, time, and place
  • End: date, time, and place
  • Route taken
How It Works

Our patent pending technology detects activities within moments of beginning. Setting the smartphone in motion triggers the accelerometer sensors built in the device and the SDK starts recording the activity right away. When the activity ends, the SDK falls back to hibernation waiting to be reawoken. Activity-detection information and location sampling will enable functions and services within your own app.

Why Our SDK?

Our SDK is always on, provides accurate, reliable data, and consumes 80% less battery power compared to other products. You can benefit from our analysis tool and get insights into your user data.

Use Case
Fleet Management
The TL KIT/OPEN API is the perfect hardware-free, easy-to-integrate solution for fleet management. The ready to use SDK can be integrated in any iPhone or Android app and is ready to operate. Driving activities are automatically recognized and accurate data is uploaded to the backend. This phone based solution helps maximize your vehicle efficiency. Safer, more efficient driving means less miles, less fuel and less downtime. Know where your workers are located for effective work order management. Boost ROI with better utilization, improved security and maintenance.
Technology Approach:
Artificial Intelligence and Sensor Fusion
  • Which sensor should we use to learn what?
  • How noisy is the data, are the sensors calibrated?
  • Which sensor chipset is used, how is it different?
  • Which sensor to use, when and for how long?
  • How much power is consumed by each sensor?
  • How to detect vehicle vs. phone motion?
Platform Model

(Self-learning phone-specific models to enhance battery and accuracy)

Mobility SDK location drive analytics
Uncertainty-based, information gain, decision process (Artificial intelligence, model-based reasoning)
Calibration within & across sensors
Feature Classifiers
(Signal processing, machine learning)
Performance: Phone vs. OBDII Dongle

We compared mobile phone mobility data (from our SDK) with OBDII dongle data.

Test Setup:
  • Phones: 13 different Android smartphones & iPhones 5 and 6
  • App / SDK: Betterways App (available on Goggle-play and Itunes)
  • Dongle: OBDII
  • Vehicles: 9 different vehicles (Ford F150, Sprinter Van, Volvo S40, Range Rover HSE etc).
  • Phone positions: cup holder, center concoul, passenger seat, glove box, pockets etc (normal user behavior simulation)
  • Miles: 6,000 miles with 5 drivers in cities & highways
Mobility SDK location drive analytics
Test Results:
Phone vs. Hardware
Mobility SDK location drive analytics