ros-planning/navigation_msgs

Message packages required by the navigation stack

navigation_msgs's Issues

Release in Eloquent?

Consider merging these messages with nav_msgs

This is a follow up to the Aggregate Foxy Message API Review

It was suggested that these messages could be homogenized with nav_msgs potentially extending them.

https://github.com/ros2/common_interfaces/pull/86/files#r393332939

Clarify project license

Currently, the only indication regarding the license is given by the two package.xml files simply mentioning BSD. This creates an uncertain licensing situation as it is unclear which BSD version is being referenced.

A LICENSE file should be added to the repository or package.xmls should precisely state which BSD license applies.

Release navigation_msgs to Noetic?

Would you mind releasing navigation_msgs to ROS Noetic? It looks like all of its dependencies have been released, and recursively 109 repos need it.

I'm not sure how much work it will need. At a minimum it needs #13.

SaveMap.srv API review recommended updates

This is a follow up to the Aggregate Foxy Message API Review

The message should use string not std_msgs/String and it would be valuable to provide a return value to indicate success or potential failure.

Lunar release

Hi @mikeferguson and @DLu,
As you may know the next ROS release Lunar Loggerhead is around the corner 🎉

Is it possible to release 1.13.0 into Lunar to allow downstream packages to be released?

Thanks!

move_base_msgs not included in melodic desktop_full

Sorry to throw this here, I am not sure if it is the right place, but I'm hoping.

When I run rosinstall_generator desktop_full --rosdistro melodic --deps --tar > melodic-desktop-full.rosinstall the resulting .rosinstall file includes navigation_msgs/map_msgs, but NOT navigation_msgs/move_base_msgs

This seems like an oversight, but I do not understand the system well enough to know were to report this or who to ask.

ROS 2 build fails with (old) ament_tools

The package.xml of map_msgs and move_base_msgs is lacking a build tool export

This means that ament_tools cannot build the package due to missing build type.
Colcon seems to handle this correctly, so maybe this is not a problem moving forward.

SetMapProjections and get MapProjectionInfo have odd semantics

In the pre Foxy API review it was flagged that these services appear to be named the opposite of what would be semantically expected.

ros2/common_interfaces#86

https://github.com/ros2/common_interfaces/pull/86/files#diff-4fa5d39b533930879a61949f36d238cbR574

https://github.com/ros2/common_interfaces/pull/86/files#diff-4fa5d39b533930879a61949f36d238cbR590

New custom message Feedback

Hi,

I add new message Feedback.msg to navigation_msgs.
float32 dist# Path distance left to goal(m)
float32 time# Time left to goal(s)
Feedback.h was created in my workspace folder.

But move_base.cpp can not find <move_base_msgs/Feedback.h>
It looks like move_base.cpp prefer move_base_msgs from Debian repo to my local.

What do I miss?

Thanks in advance,

MIchael

Kinetic Release

Needs a kinetic release. Currently on the blocking-other-packages list. Is there anything we want to change before we do so?

Rolling release?

We're preparing to fork rolling into galactic and we noticed there are changes on the default branch that have not been released yet: 2.0.2...ros2

@mikeferguson @DLu do either of you have time to evaluate whether or not a released needs to happen and make it? If you find it does need a release but do not have time to do it, let me know and we'll try to do a release for you.

Releasing into ROS Crystal

I just wanted to let the followers of this repository know I was pushing a release of this into Crystal: ros2/rosdistro#368

No action needed just FYI.