Skip to main content
A road vehicle is kind: "vehicle". This example follows a nuScenes-style rig: surround cameras, a roof LiDAR, bumper radars, CAN-bus signals and GPS, with the vehicle kinematics under the nomadic.driving.v1 profile.

Channels

Overlay

overlay.json

Sanity-checking the geometry

Each sensor’s height in the vehicle frame is the z of its FrameTransform.translation. For this rig:
Every z is positive because the origin is on the ground, not at a sensor. Cameras sit near 1.5 m, the roof LiDAR at 1.84 m, the bumper radar near 0.5 m. If your equivalent table shows the roof LiDAR at −1.84, your z axis is inverted; at 0.0, your origin is at the sensor rather than on the ground.

Notes

  • Kinematics. Under nomadic.driving.v1, speed and gyroz are required, with exactly the units shown. Convert km/h and deg/s in your converter.
  • Two steering angles. A rig often logs a steering-wheel angle and a road-wheel angle, in different units. Publish both, each with its own name and unit.
  • Rates differ. Signals in one recording commonly range from 1 Hz to 1 kHz. Publish each at its native rate; nothing needs resampling.
  • Route. recording.task holds the route for the whole recording; the navigation_instruction signal holds the instruction active at each moment.