Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse meshes specified via package:// URIs #27

Open
traversaro opened this issue Dec 16, 2024 · 1 comment
Open

Parse meshes specified via package:// URIs #27

traversaro opened this issue Dec 16, 2024 · 1 comment

Comments

@traversaro
Copy link
Collaborator

traversaro commented Dec 16, 2024

URDF models used in the ROS world typically contains meshes that are specified via package:// URIs, also as that is the only way to specify meshes without absolute filenames, at least according to the URDF specification.

While many libraries (including urchin) also support an undocumented URDF extensions in which meshes location specified by filename="this/is/a/path/to/a/mesh.stl" are interpreted as relative paths, "official" URDF files must use meshes specified via package.xml.

To support meshes specified via package:// URI in urchin without the need of depending on ROS libraries not available in pypi, I think we could add support for resolving package:// URIs via the https://github.com/ami-iit/resolve-robotics-uri-py, that is a no-dependency pure python library that can resolve package:// URIs, just using environment variables (like ROS_PACKAGE_PATH or AMENT_PREFIX_PATH) that ROS or most other URDF-capable libraries already define and support, see for example:

@traversaro
Copy link
Collaborator Author

fyi @LudovicaDanovaro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant