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

Situational events describe what a user is doing. Events are derived from time, location and motion data. They are available as a timeseries of stationaries and transports with duration.

Is the user in transport? In a car? Or a train? Walking? What route? Is the user stationary? What store or business is at that location? Is the location a home or work location?\

Stationary Events

When a user is stationary for a few minutes at a certain location, a Stationary Event will be available.

This Stationary Event is enriched with:

  • The significance of what this place means to the user based on historical data. Values: home, work, regular, non-regular, poi (point of interest), new.

  • Place/venue information like name and categories

  • Basic address information like country, city and city_type


Lookup the Stationary event in the data model reference.

  "type": "Stationary",
  "start": "2017-02-22T08:34:50.785+01:00",
  "end": "2017-02-22T16:24:55.244+01:00",
  "event_id": "6dbc1960-03ef-429a-b6f5-befb7607ae46",
  "latitude": 51.19666,
  "longitude": 4.40816,
  "location": {
    "significance": "work",
    "place": {
      "name": "Sentiance HQ",
      "category_hierarchy": [
  "address": {
    "country": "België - Belgique - Belgien",
    "city": "Antwerpen",
    "city_type": "city"

Transport Events

When a user is not stationary at a location, the user is in transport. For each of these transports a Transport Event will be available.

Additional data derived from sensor data--distance, transport mode, advanced map-matching--is computed to build an accurate trajectory and driving behavior analysis.

Transport Modes can include car, walking, biking, train, bus, tram, flight, etc. (check the full list here).

Depending on SDK configuration, additional features are derived from the sensor data. Only available in full SDK configuration:

  • behavior_scores

  • behavior_features

  • behavior_annotations


Lookup the Transport event in the data model reference.

  "type": "Transport",
  "start": "2017-02-19T15:13:00.000+01:00",
  "end": "2017-02-19T17:05:00.000+01:00",
  "event_id": "830a3534edca6c0eb24faa19f0c137dc7877592384409de43a30586643272f65",
  "mode": "car",
  "distance": 158773,
  "waypoints": [
      "type": "Waypoint",
      "latitude": 52.35004,
      "longitude": 4.87475,
      "timestamp": "2017-02-19T15:13:31.968+01:00",
      "accuracy": 25
  "trajectory": {
    "type": "TransportTrajectory",
    "encoded": "quo~Hmaw\\ACW{... polyline encoding}",
    "waypoints": [
        "type": "TrajectoryWaypoint",
        "latitude": 52.35049,
        "longitude": 4.87463,
        "timestamp": "2017-02-19T15:13:29.967+01:00",
        "road_type": "tertiary",
        "speed": 0,
        "distance": 1.4,
        "speed_limit": 50
  "behavior_scores": {
    "type": "CarBehaviorScores",
    "overall": 0.67,
    "smooth": 0.91,
    "legal": 0.79,
    "anticipative": 0.3
  "behavior_annotations": [
      "type": "AccelerationBehaviorAnnotation",
      "start": "2017-02-19T15:43:32.161+01:00",
      "end": "2017-02-19T15:43:38.851+01:00",
      "duration": 6690,
      "acceleration": "accelerate",
      "magnitude": 0.096
      "type": "AccelerationBehaviorAnnotation",
      "start": "2017-02-19T15:50:42.146+01:00",
      "end": "2017-02-19T15:50:55.042+01:00",
      "duration": 12897,
      "acceleration": "brake",
      "magnitude": 0.261
  "behavior_features": {
    "type": "CarBehaviorFeatures",
    "phone_handling": 70000,
    "distance_during_annotations": 27455

Last updated