Velodyne-only odometry type support #40
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…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'.
odom_velo
|
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.bagfor the selected sequence number XX.