Raw Telematics Data Format

Tracks that are uploaded from user devices arrive in this format.

Raw Telematics Data is a JSON object that contain information about a specific track.

High Level structure of JSON

{
  "Track": {
    "StartDate": "2020-01-24T12:03:33+0300",
    "EndDate": "2020-01-24T12:20:27+0300",
    "Points": [...],
    "LastKnownPoints": [...],
    "Events": [...],
    "StartReason": "ManualStart",
    "StopReason": "LowSpeedTimeout",
    "DeviceToken": "9a8c56da-348a-4e45-9f6a-699613e8e8ba",
    "CompanyId": 5625,
    "TrackToken": "2482b7f7-b009-4b2e-9537-f68ff26df53d"
  }
}

We prepared a sample track to download and review.

Description of Track

Field

Description

StartDate
(ISO 8601 string)

Date, on which recording of this track started.

EndDate
(ISO 8601 string)

Date, on which recording of this track ended. (string in ISO 8601 format)

Points
(array of objects, see below

An array of geographic points, which make up the route of the track.

LastKnownPoints
(array of objects, see below

Last known GPS points before track start.

Events
(array of objects, see below

An array of objects that describe notable event while the track was recorded (e.g., harsh braking, speeding)

StartReason
(string)

There are different reasons why SDK determines that a track has started, and recording begins:
ManualStart

StopReason
(string)

There are different reasons why a track is determined to be over:
LowSpeedTimeOut
ManualStop
Other

DeviceToken
(string containing 16 bytes in ASCII hex format)

Unique Identifier of the user submitting this track.

CompanyID
(number)

Unique Identifier of the Company

TrackToken
(string containing 16 bytes in ASCII hex format)

Unique Identifier of this track.

Events

Events is array of JSON objects,

:page-facing-up: Dataset

Field

Short description

Additional information

Id

unique id of event

incomingtrackid

id of incoming track

eventtype

type of event

cornering/braking/acceleration

timestart

time of event start

durationms

Event duration in ms (including all gaps between acceleration points - time from start to end)

packedvalues

JSON of events characteristics

:point-right: Described in richtrackevents​

Points

:point-right: Description
:page-facing-up: Dataset

Field

Short description

Additional information

Id

unique point id within the trip

IncomingTrackId

Incoming track id

Number

an order number of point in within the track

Starts from 0

TotalMeters

Calculated number of Meters made to this point from the start

Speed

Speed at this *timestamp (km/h)

PointDate

Timestamp of point

TickDate

TickDate

Latitude

Latitude in degrees

Longitude

Longitude in degrees

Height

Height above sea level in centimeters

Course

Course of device in degrees GPS

Yaw

Maneuvres data

Lateral

Maneuvres data

Acceleration

Acceleration in m/s2

Deceleratio

Deceleration in m/s2

TickTimestamp

Timestamp

DeviceToken

an unique user Id t

CompanyId

Id of user's company

AccelerationX

Acceleration after calc, m/s2

AccelerationY

Acceleration after calc, m/s2

AccelerationZ

Acceleration after calc, m/s2

GyroscopeX

Value after calibration

GyroscopeY

Value after calibration

GyroscopeZ

Value after calibration

AccelerationXOriginal

Original value, m/s2

AccelerationYOriginal

Original value, m/s2

AccelerationZOriginal

Original value, m/s2

GyroscopeXOriginal

Original value

G - iOS; in m/s2 - Android

GyroscopeYOriginal

Original value

G - iOS; in m/s2 - Android

GyroscopeZOriginal

Original value

G - iOS; in m/s2 - Android

Accuracy

Accuracy of GPS data in meters

10 means the points mistake is in radius of 10 meters

Screenenabled

1-enabled
0-disabled

Last known points

:point-right: Description

Field

Short description

Additional information

Id

Unique point id

Accuracy

Accuracy of GPS data in meters

10 means the points mistake is in radius of 10 meters

Latitude

Latitude in degrees

Longitude

Longitude in degrees

PointOrigin

Source of the point:

  • Heartbeat
  • Track

Did this page help you?