Take octomap file as target cloud.

[lorenwel]

Decides based on file extension which load function to use.

[rdube]

@lorenwel nice that will be handy! :) I am not sure although if we want to have the base segmatch repo to depend on octomap. Are there other situations where dependency on octomap is needed (for segmatch, not for the higher level mapper)? This could also be converted in a separate tool to load an octomap and save it as .ply. Maybe less convenient but would reduce dependencies. @HannesSommer do you have an opinion on this?

[lorenwel]

Sure I can make it a separate tool. I don't think a dependency on octomap is required anywhere else in segmatch. Do you want to create a separate laser_mapper_tools repo? I could also put the laser_track to octomap conversion in there. That will obviously depend on octomap as well.

[rdube]

Sounds good! Lets make it a laser_slam_tools package in the laser_slam repo. We can latter see how these tools evolve and if we want to group some of them in a specific package.

[rdube]

@lorenwel can we close this and delete the branch?

[lorenwel]

Yup