gps velocity
Description
Field | datatype | Description |
---|---|---|
utime | string | Best estimate of when this message is from, host clock in UTC |
utimeGlobal | utimeGlobal | Global time of navigation solution generation |
vNorth | double | NED north velocity m/s |
vEast | double | NED east velocity m/s |
vDown | double | NED down velocity m/s |
groundSpeed | double | ground speed (2-D) m/s |
heading | double | NED heading of motion (0.0 = North) (2-D) rad |
speedAccuracy | double | ublox model speed estimate accuracy m/s |
headingAccuracy | double | ublox model heading estimate accuracy rad |
validFix | bool | GNSS fix is within ublox configured DOP and accuracy masks |
vehicle | string | unique vehicle name the data is associated to. |
topic | string | type of telemetry data |
utimeGlobal
Field | datatype | Description |
---|---|---|
utime | string | Best estimate of when this message is from, host clock in UTC |
timeSys | TIME_SYS | Conveys the time system this global time message is in |
TIME_SYS
Value |
---|
INVALID |
LOCAL |
UTC |
TAI |
GPS |
LORANC |
Topic/channel string
For Realtime API
Pass the comma seperated topic name as a query param
/.vehicle.{vehiclename}.GPS_VELOCITY
For Batch API - TBD
To access the Batch API, you need to include the vehicle name and topic name as path parameters in the URL.
/vehicles/{vehiclename}/topics/GPS_VELOCITY
JSON Output
Order of fields might differ
{
"groundSpeed": 0.004000000189989805,
"heading": 5.671097755432129,
"headingAccuracy": 0.3244701325893402,
"speedAccuracy": 0.13500000536441803,
"topic": "GPS_VELOCITY",
"utime": "1683642288861757",
"utimeGlobal": {
"timeSys": "UTC",
"utime": "1683642289199983"
},
"vDown": -0.003000000026077032,
"vEast": 0.0010000000474974513,
"vNorth": -0.004000000189989805,
"validFix": true,
"vehicle": "vehiclename"
}