Check for private robot_description #89
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I came across a use case where I want robot_state_publisher to use its own version of URDF (namely: without meshes as they are loaded with absolute pathes which can lead to unfound mesh files when using several robots).
A solution is to run robot_state_publisher in its own namespace, another is to allow a private robot_description parameter to be used.
If you find any interest in this PR then feel free to merge, otherwise I'll use my fork on our system.