Support loading DAE files using data uri

Description

I tried publishing the meshes of a robot as visualization markers (visualization_msgs/Marker) to a topic, which works for STL files but not DAE files. My robot model is the UR3e, directly off of the official ROS repos. The STL files are collision geometry, and the DAE files are visual geometry.

• Version: https://studio.foxglove.dev/
• OS: Windows 10, Chrome latest

Steps To Reproduce

The visual meshes are published to a topic using data URIs of the following format: data:model/vnd.collada+xml;base64,.... For STL meshes (which work), the data URI is data:application/sla;base64,..., so it seems there’s a problem with data type identification.

To reproduce:

• Launch ROS+MoveIt+UR3e using this docker compose file
• Using compas_fab in a Python environment, run this script

Expected Behavior

Loaded meshes.

Actual Behavior

[jhurliman]

@gonzalocasas I converted your question to a discussion at https://github.com/foxglove/studio/discussions/3139

[jtbandes]

Thank you for the report! I’m going to convert this to a feature request since it’s more of a missing feature within the app. We currently have a MIME type check for STL files but not DAE:

https://github.com/foxglove/studio/blob/34f8298432af3268eb671f96768b9914b41686b4/packages/studio-base/src/panels/ThreeDimensionalViz/commands/MeshMarkers.tsx#L65-L73