Rerun URDF ingestion

A URDF gives you a robot's geometry and its kinematic tree. Ingesting it means two API calls on one rerun.urdf.UrdfTree: stream the static model, then drive it with forward kinematics from joint states. The transforms it produces are derived, so they are a layer, never base (the URDF + joints (computed) row of the rerun-data-model table).

This skill is the UrdfTree API and the two judgment calls it cannot make for you: how your joint values map to URDF joints, and how the disconnected frames in the scene connect to one root. The stream/lens plumbing (LazyChunkStream, DeriveLens, Selector, writing and optimizing RRDs) is in rerun-chunk-processing; reach for it, do not re-derive it. Nothing below is tied to a data format: where your joint names, joint values, and calibration come from is yours to wire in.

Getting the URDF

Datasets rarely ship one, and the robot's own repo is not always the fastest route. In order: