TBC Macros and Extensions

Hello,

@Gary Lantaff 

due to performance reasons I try to filter cloudpoints as much as possible with built in methods.

But there seems to be a bug in Trimble.Vce.Scanning.SDEIntegration.SdePointCloudDatabaseIntegration.FilterCloudByPolyline, including TBC 5.81.

If useonlyradius is set to False and the filtering is done via the leftvalue/rightvalue the points on the line, with offset 0.000, are ignored.

The vertical filtering via abovevalue/belowvalue works as expected, dh = 0.000 is included.

I suspect they forgot an equal sign when checking the computed offset against the horizontal thresholds.

Pure radius selection works correct as well.

Hey Ronnie, see attached video. I am not able to reproduce the issue. Point clouds appear to be visible under the line string. See video below showing my workflow. Is there anything missing in my workflow?


https://youtu.be/_VQds4-b8TI

Thank you for your comment, but the video has nothing to do with the problem I've described.

You posted in the macro language section of the forum. The problem I've posted refers to a specific method of the API. You'd need Visual Studio to confirm the problem.

I've just tested it, and the issue remains in version 5.90. The above mentioned method takes a selection of a point cloud and filters it by the entered thresholds.

The resulting "included" list doesn't include points with a horizontal distance of exactly zero.

Purple is the point cloud (1 by 1 by 1 mm grid), orange the selection that went into the macro, and white are the cad points that got created by the macro. As you can see it didn't create points exactly above/below the line since their horizontal distance is exactly zero and they are missing from the "included" result.