Revision history [back]

https://discourse.ros.org/t/rosbag-sharing-place/1956 mentions https://marvhub.com and https://botbags.com/bags - it looks like marvhub has the better searching facility (multiple filters applied in a boolean fashion would be nice to have, currently only one message type filter can be applied).

This is one search result that has a LaserScan and a /tf, I found it with this search: https://marvhub.com/aew7osa/?filter=ewogIm1zZ190eXBlcyI6IHsKICAib3AiOiAiYW55IiwKICAidmFsIjogWwogICAic2Vuc29yX21zZ3MvTGFzZXJTY2FuIgogIF0KIH0KfQ==#/collection/bags (not sure why the urls are so long, they don't inspire confidence they'll work for anyone else or will continue to work in the future...).

If you want to republish an odom as a tf look at the message definitions:

$ rosmsg show Odometry
[nav_msgs/Odometry]:
std_msgs/Header header
  uint32 seq
  time stamp
  string frame_id
string child_frame_id
geometry_msgs/PoseWithCovariance pose
  geometry_msgs/Pose pose
    geometry_msgs/Point position
      float64 x
      float64 y
      float64 z
    geometry_msgs/Quaternion orientation
      float64 x
      float64 y
      float64 z
      float64 w
  float64[36] covariance
geometry_msgs/TwistWithCovariance twist
  geometry_msgs/Twist twist
    geometry_msgs/Vector3 linear
      float64 x
      float64 y
      float64 z
    geometry_msgs/Vector3 angular
      float64 x
      float64 y
      float64 z
  float64[36] covariance

$ rosmsg show tf2_msgs/TFMessage 
geometry_msgs/TransformStamped[] transforms
  std_msgs/Header header
    uint32 seq
    time stamp
    string frame_id
  string child_frame_id
  geometry_msgs/Transform transform
    geometry_msgs/Vector3 translation
      float64 x
      float64 y
      float64 z
    geometry_msgs/Quaternion rotation
      float64 x
      float64 y
      float64 z
      float64 w

You could copy odometry pose.pose.position into tf transform.translation, copy each x y and z, luckily rotation can be copied straight across since they are the same type, and copy the header and child_frame_id also. (Is there an existing node available that does this?)

https://discourse.ros.org/t/rosbag-sharing-place/1956 mentions https://marvhub.com and https://botbags.com/bags - it looks like marvhub has the better searching facility (multiple filters applied in a boolean fashion would be nice to have, currently only one message type filter can be applied).

This is one search result that has a LaserScan and a /tf, I found it with this search: https://marvhub.com/aew7osa/?filter=ewogIm1zZ190eXBlcyI6IHsKICAib3AiOiAiYW55IiwKICAidmFsIjogWwogICAic2Vuc29yX21zZ3MvTGFzZXJTY2FuIgogIF0KIH0KfQ==#/collection/bags (not sure why the urls are so long, long and cryptic, they don't inspire confidence they'll work for anyone else or will continue to work in the future...).

If you want to republish an odom as a tf look at the message definitions:

$ rosmsg show Odometry
[nav_msgs/Odometry]:
std_msgs/Header header
  uint32 seq
  time stamp
  string frame_id
string child_frame_id
geometry_msgs/PoseWithCovariance pose
  geometry_msgs/Pose pose
    geometry_msgs/Point position
      float64 x
      float64 y
      float64 z
    geometry_msgs/Quaternion orientation
      float64 x
      float64 y
      float64 z
      float64 w
  float64[36] covariance
geometry_msgs/TwistWithCovariance twist
  geometry_msgs/Twist twist
    geometry_msgs/Vector3 linear
      float64 x
      float64 y
      float64 z
    geometry_msgs/Vector3 angular
      float64 x
      float64 y
      float64 z
  float64[36] covariance

$ rosmsg show tf2_msgs/TFMessage 
geometry_msgs/TransformStamped[] transforms
  std_msgs/Header header
    uint32 seq
    time stamp
    string frame_id
  string child_frame_id
  geometry_msgs/Transform transform
    geometry_msgs/Vector3 translation
      float64 x
      float64 y
      float64 z
    geometry_msgs/Quaternion rotation
      float64 x
      float64 y
      float64 z
      float64 w

You could copy odometry pose.pose.position into tf transform.translation, copy each x y and z, luckily rotation can be copied straight across since they are the same type, and copy the header and child_frame_id also. (Is there an existing node available that does this?)