humanoidsdata.com

Search

Search companies, datasets, articles, and glossary terms for humanoids and embodied AI.

← All glossary terms

Simulation & transfer

URDF

Unified Robot Description Format

URDF, the Unified Robot Description Format, is an XML format used in ROS to describe a robot as links connected by joints, together with properties such as geometry, collision shapes, inertial parameters, limits, and visual materials. A URDF describes a robot model; it is not by itself a controller, simulator, CAD assembly, or complete record of the physical machine.

Also known as: URDF model, URDF file

Updated

ROS describes URDF as a format for specifying robot geometry and organisation. Links represent rigid bodies. Joints connect a parent link to a child link and specify the transform, axis, type and limits that define permitted relative motion.

A link can reference separate visual and collision geometry. It can also contain mass, centre of mass and inertia for dynamics. These roles should not be conflated: a detailed visual mesh may be unsuitable for collision detection, while a coarse collision shape may not match appearance closely enough for rendering or synthetic perception data.

A valid file can still be an incomplete robot description

The urdfdom schema defines elements such as links, joints, inertial properties, geometry and materials. It does not make those values correct. Missing inertia, unrealistic collision shapes, incorrect joint axes or stale limits can produce a model that loads successfully but behaves unlike the hardware.

URDF models also form a tree, so closed kinematic loops and simulator-specific behaviour often require extensions or another format. Transmissions, sensors, actuators, contact parameters and plugins may live in additional ROS or simulator configuration. The robot's firmware, controller gains, delays and safety logic are not recovered from link and joint geometry.

Version the model with the data

For a robot dataset, a URDF can make joint names, frames, kinematic structure and geometry interpretable. It is especially useful when poses, torques, camera calibration or retargeted motion refer to named links. But a generic model downloaded later may not match the robot revision used for collection.

Publish the exact file or source commit, mesh assets, units, calibration changes and hardware modifications with the dataset. State which parameters were measured, identified or approximated. When simulation generated the data, retain any converted model and simulator-specific additions as well as the source URDF.

Sources