-
Notifications
You must be signed in to change notification settings - Fork 100
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
SDF-specific documentation on how to interpret model:// URIs #1234
Comments
There is some documentation in http://sdformat.org/tutorials?tut=composition&cat=specification&#including-a-model. Is that helpful? |
Sorry, I missed your reply. Yes, this is indeed what I was looking for, I was confused as I was mostly investigating the use of
We can just use |
I look a bit more into this, and apparently the use of
This sentence was added in gazebosim/gz-sim#172 with the rest of the tutorial, but I am not really sure why it is not recommended to use it. |
Anyhow, this is definitely a bit OT here, so let's close this issue. |
Desired behavior
As a mantainer that writes software that loads SDF files, and as a mantainer that distributes SDF models, I would like to understand how URI in the form
model://
should be interpreted according to the SDF standard.It would be great if this information could be documented.
It would be great if this would be documented.
Alternatives considered
Each program could implement its own way to interpret
model://
URIs, but in that case as a mantainer that distributes SDF models, it would not be clear to me how to make sure that all programs that interpret SDF are able to load my files.Implementation suggestion
At least for Gazebo-related software, from what I understand the URI is expanded w.r.t. to the following env variables:
GAZEBO_MODEL_PATH
for Gazebo ClassicIGN_GAZEBO_RESOURCE_PATH
for Ignition Gazebo <= 7GZ_SIM_RESOURCE_PATH
for Gazebo Sim >= 7It would be great if there would be a clear way endorsed at the SDF level tha explains how to load
model://
URIs.Additional context
I opened this after reading ami-iit/rod#20 .
The text was updated successfully, but these errors were encountered: