I'm looking for insights as to the factors that determine whether ReCap recognizes a target. If this minimum of three is never reached, ReCap does not take into account any target data when it performs a registration. This prevents me from getting the necessary minimum of three targets to match across any two scans that I'm trying to align.

It DOES recognize SOME of them, but refuses to recognize others.

The problem I've encountered with this seemingly reasonable strategy is that I can't get ReCap to recognize most of my targets. I think this is essentially the same idea as Admad1st alludes to in his earlier post on this topic.īy trial and error, I discovered that ReCap only allows me to enter the measured coordinates of a given target if it has first detected that a target is present in the region where I've said there is one (i.e., ReCap requires one to supply a 'hint' as to where it will find a target, by clicking close to the target in a RealView of the scan). This caused me to investigate whether I could use targets (for which I provide separately-measured coordinates that I trust) to force ReCap to orient the Z-axis correctly - thereby making the X-Y plane perfectly horizontal.

In my experiments, this rendered my project useless, since I wanted to use my registered, unified point cloud to measure elevations at various points on sloped outdoor concrete surfaces. I've had the same problem with out-of-level results - sometimes grossly out of level) after bringing my BLK360 scans into ReCap Pro.

Recap pro blk360