Since the Reality Scan 2.0 update, importing LiDAR Scan Data automatically creates a new Component. Is there a reason for this change in functionality? I’d prefer if importing LiDAR Scan Data didn’t create a new Component, similar to how it worked in Reality Capture 1.5.1. Could you please add an option to the import settings, allowing users to select “Yes/No” for creating a new Component? I would really appreciate it. This is a really important option for me.
1.5
2.0
Hello @Nuriarchive
You are right, this option was added in the newest release.
It was the response to the customers, as they were asking, where is my point cloud after import.
But this is only happening for the georeferenced point clouds.
May I ask, why this option doesn’t work for you? Basically, you need to align the data anyway.
Hello.
There was a reason for that.
Thank you for applying the request to the new version.
It’s a story based on my experience.
I don’t just use Laser Scan Data, but I also import and align the image.
In the absence of new components, it seems that aligning the image together has produced better results.
Yesterday, I found something strange in the project I was working on.
Laser Scan Data Import
Import Images and Align
I created a new project and imported previously generated .lsp data (only .lsp was added and no new components were created)
This should work also with the images and laser scans, it shouldn’t be related to the already aligned laser scan component.
What are your laser scan import settings and the alignment settings?
Are you able to reproduce that strange behaviour?
As you imported only LSPs, these are considered as images for RealityScan and therefore there is no automatic alignment.
The error could not be reproduced.
It was my first time experiencing this situation while using Reality Scan.
As it is not possible to reproduce I suppose we can consider it as “closed” for now.
But indeed, it was very strange behaviour…
Okat Thank you so much.
Have a nice day.
See you.
