Zhi Yan, Li Sun, Tomas Krajnik, and Yassine Ruichek
https://epan-utbm.github.io/utbm_robocar_dataset/
We forked the implementation of the following state-of-the-art methods and experimented (with minor changes) with our dataset:
- Pose Estimation: https://github.com/tu-darmstadt-ros-pkg/hector_localization
- Lidar odometry: https://github.com/laboshinl/loam_velodyne
- Lidar odometry: https://github.com/RobustFieldAutonomyLab/LeGO-LOAM
- To be continued ...
All users are more than welcome to commit their results.
Ground-truth trajectories recorded by GPS/RTK
roslaunch utbm_pose_estimation.launch bag:=path_to_your_rosbag
utbm_pose_estimation.launch
is here.
First of all, you should have something like this:https://yzrobot.github.io/
Then, /fix/pose
(geometry_msgs/PoseStamped) ihttps://yzrobot.github.io/s the estimated robot pose (6DOF) based on the GPS data.
roslaunch loam_velodyne loam_velodyne_utbm.launch bag:=path_to_your_rosbag
loam_velodyne_utbm.launch
is here.
First of all, you should have something like this:
Then, /aft_mapped_to_init
(nav_msgs/Odometry) is the output lidar odometry that needs to be evaluated.
Single Velodyne HDL-32E (left)
- Minor changes w.r.t. LeGO-LOAM (Issue #9, thanks to robot54)
roslaunch lego_loam lego_loam_utbm.launch bag:=path_to_your_rosbag
lego_loam_utbm.launch
is here.
First of all, you should have something like this:
Then, /aft_mapped_to_init
(nav_msgs/Odometry) is the output lidar odometry that needs to be evaluated.
Single Velodyne HDL-32E (left)