Hi Jakub, i am also a user of the eagle scanner (max version). I just found this exciting post: Did you already have the opportunity to work with the eagle sacanner files? I am highly interested in that workflow! Like Swescan, i also would be happy to share any files and give feedback.
Cheers,
Jan
Hi @OndrejTrhan and @JakubVanko ,
The COLMAP workflow is working well with my L2 Pro data, and I’ve successfully meshed several projects in RealityScan. However, I’ve noticed that the LSP files generated when importing LAS files into RealityScan are very low resolution.
Because of this, I struggle to automatically align photos taken with other cameras (e.g., Canon R5) to the L2 Pro data. Is there a way to improve the resolution or alignment process?
Ideally, I’d like to avoid using control points to manually align L2 Pro data with images from other cameras.
Please let me know your thoughts on this. Thank you.
Hi @brucehimself , you are correct about the lower resolution of the LSPs in RealityScan. Those are just previews and indeed are not the best for manually adding control points.
For automatic alignment, feature detection occurs on full-resolution LSPs generated during LiDAR import. Those detected features are then matched to features detected in images from other cameras.
The best advice I can give you right now is to take photos from the other cameras at roughly the same positions as the SLAM scanner path to help with automatic alignment. In this scenario, it is easier to place the CPs in this scenario as well.
Hello @Swescan_AB and @Polyvista , we have been able to fix the issue with importing COLMAP from the Eagle scanner, but the COLMAP we had was in a local coordinate system and the point cloud was georeferenced. XGRIDS provided a map_config.json and in it a offset_xyz which we can use during the COLMAP import so it matches the point cloud.
Does the Eagle scanner also output such information? From the tutorial:
Anyone tried SHARE S20 SLAM? Does Relity Scan support this SLAM?
Hi @JakubVanko, thanks for this tutorial. The tutorial got me 90% of the way with my 3DMakerPro Raven Max Lidar scan, I was able to import the camera poses with the COLMAP by clearing out the points3d.txt file. I also applied a 90 degree x-rotation on import to correct the orientation.
When I import the LIDAR data, the orientation is completely wrong.
If I then try to align with these two components, they are unable to align. I have tried rotating the .las point cloud itself by 90 degrees in the x direction before importing. This is the result (also will not align):
As of mid June 2026, it seems that XGrids encrypts the Colmap output (images and csv). Can anyone confirm? File in my hands look like this (image.jpg.enx, points3D.csv.enx, cameras.csv.enx,…).
