So I had a project of a jobsite that I scanned and registered a couple months ago. I then added survey points to rotate and locate the scan where I wanted to bring it into other programs in the correct location. I went back to the site yesterday and did a couple more scans to document the work that had been done. I brought the three new scans into the old project, and manually registered them in. Bringing the revised cloud into my other program, it was not matching up with the other objects in the model, it was about an inch low. I then had my IT guy restore the old rcp, and brought this in, and in fact, adding the new scans moved the cloud.
I checked my survey points, the xyz on the top has slightly different values from project to project, but the coordinates I assigned remain the same.
also my rms has changed between the two projects. see attachment
Has anyone else had this happen?
Solved! Go to Solution.
Solved by ryan.frenz. Go to Solution.
Hi,
Are you saying that the new project has different coordinates than the first time when you assigned the points?
That shouldn't happen.
Try to remove them and add at least 3 points and that should update your model.
Mitko
I know it shouldn't happen.
as it turns out, my first project turned out to have an inclometer issue, and was off level.
adding the new scans seemed to level it out a bit, but I cant have there being a possibility of the project moving when new scans are added.
Hi Jason,
ReCap performs a nonlinear optimization of the whole scan network every time that network changes. So yes, technically adding a new scan can adjust the pose of any scan in the registered network. This should be because there is now a tighter solution - if not, that means the new scan had an adverse affect on the registration. Your survey alignment getting worse would again be a red flag for that.
We are evaluating a feature to allow locking of registration groups. This would give the behavior you expect (your old scans wouldn't move) - but you'd end up with a (possibly much) worse registration of the new scans. You could also achieve what you want by registering the sets separately and using common survey points to orient them together.
-Ryan
We are continuing to have issues with manually adding scans to established projects and moving them.
We have had two projects actually change the registration of scans already registered in the original project for the worse, so one pipe, now its 3 pipes.
I am looking forward to being able to lock registration groups.
This appears to be happening a lot lately, and we never had issues like this before.
could this be a bug in the latest version 3.0.2.12?
Was there ever a solution to this found? I am currently experiencing the same issue with Recap 2025...
Can't find what you're looking for? Ask the community or share your knowledge.
