Skip to content

Fixing remaps and namespaces - #390

Open
Mat198 wants to merge 1 commit into
ros-perception:rollingfrom
Mat198:fix_remap&namespace
Open

Fixing remaps and namespaces#390
Mat198 wants to merge 1 commit into
ros-perception:rollingfrom
Mat198:fix_remap&namespace

Conversation

@Mat198

@Mat198 Mat198 commented Feb 5, 2026

Copy link
Copy Markdown

This PR adresses issue #357 and also applies a correction for topic remap.

I was in need for this correction on my work so I made this PR without much discussion. I consider this solution as non ideal because it will break everyting using the image_transport_py right now. Anyway, the api is kinda broken as there is not a proper way to remap topics and add namespaces.

Any suggestions are welcome and I hope this PR helps someone :)

Uses the main python node and parse the data for the internal image_transport node.
@peci1

peci1 commented May 15, 2026

Copy link
Copy Markdown
Contributor

I have already learned to manually resolve the base topic before giving it to image_transport. What you propose seems to be more intuitive (and ROS1-like). I could live with both variants - if the intentional behavior is well documented.

Do the maintainers have a stance at which way is the preferred?

a) do not remap base topic
b) automatically rename base topic

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

Successfully merging this pull request may close these issues.

2 participants