2-3. Raw Telematics Data Format

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

Raw Telematics Data is a JSON object that contains 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 JSON 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.

Description of `Points`

📄 Parsed JSON Dataset

Field	Short description	Additional information
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	Calculated and filtered speed at this *timestamp (km/h)
midSpeed	Speed as it is from sensor
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
Deceleration	Deceleration in m/s2
EstablishedIndexA	Points indexing status field
EstablishedIndexB	Points indexing status field
TickTimestamp	Timestamp
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
BeaconId	Id of beacon if exists
Measured power	Power data from vehicle if beacon exists	V
RSSI	The strength of the beacon's signal
Ping	The ping of the beacon's signal	ms
Screenenabled	1-enabled 0-disabled
DeviceBlocked	1-enabled 0-disabled
VehicleIndicators	Id of user's vehicle if connected
Urban	Flag of point attributed to urban area
Quantile	For each second of acceleration and gyroscope data we rotate axis to align with direction of movement and aggregate values with frequency of 1HZ This field is JSON object that collects aggregated acceleration and horoscope data for each second. Turned off by default

Description of `Last known points`

📄 [Parsed JSON Dataset] (https://datamotion.docsend.com/view/bvit2t2nz89xcv3j)

Field	Short description	Additional information
PointDate	Unique point id
Latitude	Latitude in degrees
Longitude	Longitude in degrees
Accuracy	Accuracy of GPS data in meters	10 means the points mistake is in radius of 10 meters
PointOrigin	Source of the point: Heartbeat Track

Description of one event in `Events JSON`

Events is array of JSON objects, each object is event, event is threshold triggered window unity that collects sensor's data in the initiated event recording

Field	Short description	Additional information
Type	type of event	cornering/braking/acceleration/accident
PointStart	Coordinates at event start
PrevEventSpeed	Speed at which previous event occurred	m/s
SpeedStart	Speed at event start	m/s
PureDuration	Event duration in ms (excluding all gaps between acceleration points - time from start to end)	ms
SpeedStop	Speed at event start	m/s
AccelerationLateral (1)	Acceleration rate at the beginning of event that is aligned with perpendicular vector to direction of movement	m/s2
AccelerationDirect (2)	Acceleration rate at the beginning of event that is aligned with vector of movement	m/s2
PointEnd	Coordinates at event end
AccelerationLateralEnd	(1)* at the end of window	m/s2
AccelerationVerticalEnd	Vertical acceleration at the end of [window]	m/s2
AccelerationDirectEnd	(2)* at the end of window	m/s2
RangeDirect	Aggregated metics on (1) inside event window	m/s2
RangeLateral	Aggregated metics on (2) inside event window	m/s2
RangeVertical	Aggregated metics on Vertical acceleration inside event window
Accuracy	GPS accuracy at the beginning of event	m
Speed	GPS speed at the beginning of event	m/s
TimeStart	Time of event started recording
Duration	Event duration in ms (including all gaps between acceleration points - time from start to end)
SpeedMedian	Median speed during event window
AccelerationVertical	Vertical acceleration	ms

Updated 5 days ago