Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Velodyne-only odometry type support #40

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

alexandrx
Copy link
Collaborator

Added support for velodyne-only odometry type. It will generate a rosbag file with pointcloud-only topic with timestamp, and the bag filename will be kitti_data_odometry_velo_sequence_XX.bag for the selected sequence number XX.

alexandrx and others added 2 commits December 4, 2018 18:08
…bag file with pointcloud topic only with timestamp, and the bag filename will be 'kitti_data_odometry_velo_sequence_XX.bag' for the selected sequence number XX. For better results use pykitti from 'utiasSTARS/pykitti#39'.
@tomas789 tomas789 requested a review from valgur May 14, 2019 07:31
@valgur
Copy link
Collaborator

valgur commented May 14, 2019

Including Velodyne data in the odom bag output is definitely a good idea. I think a common logic between raw and odom datasetes to select the types of data (velodyne, mono/rgb images, imu+gps) to include or exclude might be a better idea than creating a separate 'odom_velo' type, though?

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