Hi,
In RealityCapture it was possible to import Laser Scans from terrestrial laser scanners.
However in RealityScan 2.0 I can only find option to import LiDAR Scan, and trying to use that option to import Laser Scans does not work.
Does it mean that RealityScan will no longer support importing data from terrestrial laser scanners?
Mike
Hello Mike,
the functionality for the terrestrial laser scans weren’t change. It should work as before.
Do you have Z&F laser scanner? If so, there is a bug for the import such data.
Yes I have Z&F laser scanner. I just tried converting it to .E57 file format in Recap and RealityScan imported that without any problem.
Thanks for help and for great software 
Do Laser scans need to have color information in order for them to be processed during import?
@Dim-Geo
No, they don’t need that.
So, regarding profile selection when importing, we still do select “color” in the initial menu?
It depends on your data. When there is also intensity, you can choose that option.
Hello, still having problems aligning laser scans and photos. More specifically we’re importing RTK tagged photos, aligning and then importing the lidar data (exported e57 with scan stations from RECAP).
As for alignment settings, we’re using a 5,5,10cm for the prior pose accuracy and all photos have custom values for their independent accuracies.
Still no way to align the components, is there anything else to try out?
Hello @Dim-Geo
Are the laser scans also georeferenced?
Basically, when the overlap between the data is good, they should be aligned automatically. When it is lower, then you can use the option Merge georeferenced components in the Advanced Alignment settings or (maybe the best option) is usage of the control points or GCPs. But for this case you need to have enough LSPs for placing them (basically you need to consider this during the capturing the data).
Yes the laser scans are georeferenced. Tried with tie points and they indeed aligned, although views are limited for the laser scan tie point views. Merging the georeferenced components didn’t work (as it hasn’t worked in the past for photogrammetry datasets), as it produced shifted double point clouds.
It also depends in which coordinate systems are they georeferenced. It is better, when it is the same one. You also need check which height system is used. As RealityScan works only with ellipsoidal heights, when you for example use geoid heights and ellipsoidal heights then you can get shifted double point cloud.
Another detail; When lsp files are created in the first place, is there a specific setting that controls the frame that is created from panoramic images? A lot of times in the final cube image, there is not enough detail in the distance (it is blurred on purpose? ). Actually how exactly does the software decide what to blur or not in the final cube image?
In most cases it depends on the distance. Also, the sky is omitted.
But there is no a specific setting for that. The LSP creation is hard coded.