-
Notifications
You must be signed in to change notification settings - Fork 0
Update README with information on how it works #7
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
Conversation
Yes! I suggest something more but more and less it is what I needed. |
|
I have some ideas cooking along the lines of formal definition of an interface (I saw your fingerprints on the same over in ros/urdfdom#200 and related issues), but I'm trying to clean up the upstream schema before making one that derives from it. (ros/urdfdom#227, ros/urdfdom#228, ros/urdfdom#229) |
|
Yes, I think what would also useful at fyi @saikishor |
traversaro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently I added a suggestion but it remained in pending mode (that it was the "more" I was suggesting in my comment, sorry for the confusion. @EzraBrooks
|
|
||
| ## How does it work? | ||
|
|
||
| URDFZ treats your URDF as an archive manifest for your URDFZ archive. It looks up all the URIs listed in the URDF, resolves them to absolute paths, and copies them into the archive. It then creates a copy of your URDF that has its URIs rewritten to a `urdfz://` scheme that points to the asset's path within the archive, and places that modified URDF at the root of the archive. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| URDFZ treats your URDF as an archive manifest for your URDFZ archive. It looks up all the URIs listed in the URDF, resolves them to absolute paths, and copies them into the archive. It then creates a copy of your URDF that has its URIs rewritten to a `urdfz://` scheme that points to the asset's path within the archive, and places that modified URDF at the root of the archive. | |
| URDFZ treats your URDF as an archive manifest for your URDFZ archive. It looks up all the URIs listed in the URDF, resolves them to absolute paths, and copies them into the archive. It then creates a copy of your URDF that has its URIs rewritten to a `urdfz://` scheme that points to the asset's path within the archive, and places that modified URDF at the root of the archive. | |
| Once the URDFZ is extracted, the `urdfz://` URIs are replaced with a `file://` containing the absolute path to the extracted resource file. |
I am not sure if what I added is correct, but it would be great to describe what happens at extraction phase.
Good to know. We should definitely tackle this ;) |
Closes #5.
@traversaro is this the sort of information you were looking for?