Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

geometry_msgs/Vector2 ?

asked 2016-11-21 12:00:48 -0600

antonio
93 ●5 ●7 ●12

Is there an extension of geometry_msgs including 2D types, such as geometry_msgs/Vector2? I don't seem to find such a package on Github, for example.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2016-11-21 13:04:39 -0600

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

If you're looking to store 2D positions or poses, perhaps the Point or Pose2D types in geometry_msgs could work?

For Point, just ignore the z member. If you don't care about orientation, ignore theta in Pose2D.

edit flag offensive delete link

Comments

Right; my concern was mostly about keeping the message type semantically consistent with the content; but of course we can reuse Point for 2D.

antonio ( 2016-11-23 06:28:12 -0600 )edit

Well, I guess it's a bit of a point for discussion, but using Pose2D for this seems like a good fit: it encodes a position in a 2D space, with an associated orientation.

You could consider submitting a PR that adds a Vector2 (or maybe Point2D) to geometry_msgs though.

gvdhoorn ( 2016-11-24 00:56:28 -0600 )edit

add a comment

Question Tools

1 follower

Stats

Asked: 2016-11-21 12:00:48 -0600

Seen: 3,506 times

Last updated: Nov 21 '16

geometry_msgs/Vector2 ? edit

1 Answer

Comments

Question Tools

Stats

Related questions

geometry_msgs/Vector2 ?