Update README.md

[topguns837]

🦟 Bug fix

Summary

Bug : The ROS topic for GPS sensor is not visible in ros2 topic list even though ros-ign bridge has been created for it according to the provided documentation

Fix :

• The ROS type given for gz.msgs.NavSat is wrong.
• It should be sensor_msgs/msg/NavSatFix instead of sensor_msgs/msg/NavSatFixed

Checklist

• Signed all commits for DCO
• Added tests
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

[ahcorde]

Thank you for the contribution @topguns837 , we need to backport this to iron and humble. Do you have time to do it ? or should I create the PRs ?

[topguns837]

sure @ahcorde !
Just to be sure, backport means I have to make the same changes in the humble and iron branch, right ?

[ahcorde]

you should use cherry-pick, here the cmds that you should use:

cd ros_gz
git checkout humble
git checkout -b topguns837/humble/backport_411
git cherry-pick c279a53
git push origin topguns837/humble/backport_411

[topguns837]

Would love to contribute, can you assign me this issue ?

[ahcorde]

@topguns837 no need to assign the issue, you can just open the PRs

[topguns837]

Hey @ahcorde ,
I have created PR #415 and PR #416 regarding this

[ahcorde]

The backports were not created properly. Can you try again ?

[topguns837]

@ahcorde can you check now ?