UPDATE: All things considered, it's not too horrible simply looping through every position from the Geometry.Points.PositionArray, and comparing the distance in order to find the closest point in the cloud. So far, that technique is faster than anything else I've attempted to cook up.
-Bradley On Tue, May 1, 2012 at 3:01 PM, Bradley Gabe <[email protected]> wrote: > Nah, it was raising errors when I tried it before starting this thread, > and it still is now [?]: > > # ERROR : 2028 - Traceback (most recent call last): > # File "<Script Block >", line 2, in <module> > # obj.ActivePrimitive.Geometry.GetClosestLocations([0, 0, 0]) > # File "<COMObject <unknown>>", line 2, in GetClosestLocations > # COM Error: Invalid argument specified. - [line 2] > > > On Tue, May 1, 2012 at 2:58 PM, Bradley Gabe <[email protected]> wrote: > >> I was going by the following quote from the docs: >> >> Note: Point locators are currently only supported by NurbsSurfaceMeshand >>> PolygonMesh objects. >> >> >> But I'll still give it a shot... >> >> >> On Tue, May 1, 2012 at 2:54 PM, Stephen Blair <[email protected] >> > wrote: >> >>> But doesn't a PointCloudGeometry support GetClosestLocations? Can you >>> use that (I didn't try it yet) ? >>> >>> >
<<347.gif>>
