distilledObsData Webhook

Print Friendly and PDF

The Driver•i device collects information related to geolocation, accelerometer and gyrometer readings, vehicle speed, etc., and uploads it to Netradyne Cloud for every 10 minutes of drive timeThe distilledObsData webhook pushes a subset of this observation data to users who have subscribed to receive data through webhooks 


However, users do not receive this data in real time. If the LTE connectivity is poor, there can be delay in uploading the data-heavy observation data file. In some cases, it might take around 20 minutes or more to push the data to the users. 

 

The following table describes the parameters for the distilledObsData event.  

Parameter 

Description 

deviceModes 

Captures the following states of the device: 

State 

Description 

Possible Values 

Privacy Mode 

Indicates whether privacy was enabled or not during the session in which this file was recorded 

0: Privacy was not enabled 

1: Privacy was enabled (inward camera video is not captured) 

idle 

Indicates engine idle status during the session in which this file was recorded 

0: Vehicle was not idle (vehicle was not at zero speed for a specified time (300 seconds)) 

1: Vehicle was idle (video files are not stored in internal storage.) 

ignition_status 

Indicates the status of ignition line during the session in which this file was recorded 

0: Ignition was OFF during the entire session 

1: Ignition was ON at some point during the session 

 

tenantName 

Unique name of the Fleet. 

geoLocation 

Geographic location of the device. Includes the following: 

  • altitude: Altitude of the device in meters, relative to sea level 
  • bearing: Direction in degrees 
  • accuracy: Accuracy, with a 95% confidence level, of the latitude and longitude properties expressed in meters 
  • long: Longitude of the position in decimal degrees. A value of 181 indicates that the value is invalid. 
  • latLatitude of the position in decimal degreesA value of 91 indicates that the value is invalid. 
  • speed: Speed of the device in miles per hour 
  • timestampTime when the event was captured 

accelerometer 

Accelerometer in X, Y and Z directions  

  • accZIndicates driving/longitudinal direction and forward is positive 
  • accY: Indicates lateral direction and right is positive 
  • accXIndicates gravity direction and is positive downwards 
  • timestampTime when the event was captured 

gpsStartTime 

Start time of the current minute captured from GPS sensor 

gyrometer 

  • gyroX: Rotational force around yaw 
  • gyroY: Rotational force around pitch 
  • gyroZ: Rotational force around roll 
  • timestamp: Time when the event was captured (Epoch time) 

gpsEndTime 

End time of the current minute captured from GPS sensor 

vehicle 

Vehicle information. Includes the following: 

  • vehicleNumber: Unique vehicle number within the fleet 
  • vinVehicle Identification Number 

camera

Includes the following:

id: Unique camera identifier

webhookType 

The event corresponding to the Webhook, in this case “distilledObsData”. 

This is a Webhook sample payload to share observation data, such as GPS, accelerometer, gyrometer, etc., reported by the Driver•i device. 

{
"tenantName": "XXXXXXXX",
"deviceModes": {
"idle": 0,
"ignition_status": 1,
"privacymode": 1
},
"geoLocation": [
{
"altitude": 706.1,
"bearing": 150,
"accuracy": 3.54,
"long": -114.9109421,
"lat": 35.9719658,
"speed": 0,
"timestamp": 1573791742000
}
],
"accelerometer": [
{
"accZ": -0.629675,
"accY": -0.687136,
"accX": 9.87848,
"timestamp": 1573791740126
}
],
"gpsStartTime": 1573791742000,
"gyrometer": [
{
"gyroX": 0.824427,
"gyroY": -1.03817,
"gyroZ": -4.85496,
"timestamp": 1573791740126
}
],
"gpsEndTime": 1573791801000,
"vehicle": {
"vehicleNumber": "XXXXXX",
"vin": "XXXXXXXX"
},
"camera":
{
"id": "string"
},
"webhookType": "distilledObsData"
}
Was this article helpful?

We're sorry to hear that!

Please tell us why.
0 out of 0 found this helpful