This is not too well known, but there isn’t really anything in URDF which prevents you from using mesh formats other than
.stl,.daeand.mesh.
Yes structure of the format itself doesn’t prevent it – my tool here allows for overriding the the load mesh callback to enable loading any geometry format. It does look like RViz uses ASSIMP to load geometry so this may just be a matter of updating the docs. The URDF spec document makes the geometry format support sound very limited (STL and DAE only):
The recommended format for best texture and color support is Collada .dae files, though .stl files are also supported.
If there are no objections it would be great to update the docs to say that the mesh file extension is flexible but of course compatibility is dependent on the application – most or all reasonable file formats would be supported in ROS via ASSIMP, though. This would enable and encourage users to use more efficient and more generally compatible file formats for their models.
We’re using GLTF and GLB and in some cases PLY for our models for a variety of reasons and at least on the surface it looks like we’re creating out-of-spec and ros-incompatible models which seems to not be the case and something I want to avoid.
What would the right way to get the URDF wiki updated be?
We’ve been discussing this in various places, most recently over at https://github.com/ros/urdf/issues/34 . Feel free to join in the discussion there.
Great, thank you! I’ll write something later this week.