Vincent,
Any help on how to locate this option ("rigidly move all mission data to control in a registration and after a LiDAR QC adjustment session") would be helpful. I am using v2025.10. Tried the "global" registration but the cloud still gets either lifted above or place below the GCP. I've tried locking only x&y on the areas that the vertical is bad but got the same result.
Can you point me to a workflow that would be helpful to use this feature to it's full potential.
Thank You
------------------------------
Kyle Braga
Kyle
------------------------------
Original Message:
Sent: 07-04-2025 13:43
From: Vincent Fortier-Richer
Subject: TBC mobile mapping workflow
Hi Mark, this is a known issue. As mentioned in this power hour, the next TBC release (2025.01) will include the possibility to "rigidly move all mission data to control in a registration and after a LiDAR QC adjustment session". Meanwhile, have you tried selecting the "global" registration type (rather than "local" or "global than local")?
------------------------------
Vincent Fortier-Richer
Original Message:
Sent: 06-18-2025 04:13
From: Mark Brooker
Subject: TBC mobile mapping workflow
I've recently been using a new Trimble MX60 for our mobile mapping projects.
Does anyone here have experience in the processing side of this data? Specifically in regards to processing to ground control points. I've been utilising the Lidar QC tool which is great at cleaning the multiple runs and putting them all together. However, when it then comes to registering these scans to control it just seems to pull the scans apart for this to happen (this seems to undo all the work Lidar QC has automatically adjusted). Is there any way of having multiple runs/scans locked as one cloud after the Lidar QC tool has successfully been used? This way when adjusting to control it all moves as one and on grid so to speak.
The issue may be down to user error on my part and not fully understanding how TBC processes the mobile mapping data.
Our current process is to drive the jobs capturing the runs as we go. Being careful when scanning on tight turns and then splitting these runs later on to remove redundant captured detail.
We then need to get a final pointcloud on grid before exporting. We use ground control points captured by total station on site and processed to the chosen grid and pick these from the scan data to adjust.
any advice is appreciated.
------------------------------
Mark Brooker
------------------------------