topic Re: Point Check in Visual LISP, AutoLISP and General Customization Forum

Point Check

johnd — Mon, 14 Aug 2023 14:08:41 GMT

Looking for suggestions:

I have a routine that creates a points group from cogo points that are used to make up a 3Dpolyline. You select the 3D polyline and it ask for a group name then using the "f" selection made up from vertex list (PLIST) it creates a group with all the points that make up the line. Since the points are what make up the line they are being selected and put in the group.

Two lists are created during the routine: Plist (verticies on 3Dline) and Cogolist (points on 3Dline)

I have added a subroutine to check to make sure that each vertex has a point. It compares the two lists and draws a circle at the vertex that does not have a point attached to it. This works well.

I use a similar routine to check if a point is connected to the 3D line. It's supposed to draw a circle at the node of the point that does not have a connection to a vertex on the 3Dline.

This works, but only if the point is actually crossing the 3Dline. But, if it does not at least cross the 3D line the point is not selected and the comparison is ignored. So, if the point is below or above the line, no circle.

I'm looking for a way to put a circle on the point that does not reside in the Cogolist but is close to a vertex on the 3Dline.

Don't need code, just ideas.

Hope I explained that well enough.

Thanks

Re: Point Check

Kent1Cooper — Mon, 14 Aug 2023 14:33:43 GMT

Check whether the distance from the Point to the closest place to it on the Path is zero. Given the Point's coordinates list as location, and the Path object as either entity name or VLA object:
(if (not (equal (distance ThePoint (vlax-curve-getClosestPointTo ThePath ThePoint)) 0 1e-4))

then the Point is not on the Path. The 4 is arbitrary -- increase for greater exactly-on precision.

EDIT: Come to think of it, that would "pass" a Point that is actually on the Path but not at a vertex. If that should be flagged, use (vlax-curve-getParamAtPoint) to check whether the parameter value on the Path, where the Point is, is a whole number, which would mean it's at a vertex.

Re: Point Check

johnd — Mon, 14 Aug 2023 14:55:44 GMT

I think I follow your logic, but I'm missing something. If the point is not connected or the node (or label) does not cross the path it is not selected and placed in the list. If not in the list how is it identified to run your suggestion.

Re: Point Check

Kent1Cooper — Mon, 14 Aug 2023 15:18:55 GMT

I think I misunderstood part of the original. You presumably have the "points group" early in the description in Message 1, so go through those. Or, are there more than one set of Points / 3DPolyline in the drawing? If only one set, you should be able to grab all Points and run the check(s) on them.

Re: Point Check

johnd — Mon, 14 Aug 2023 15:19:37 GMT

There is only one 3D line and (at this time) only the points that make up the 3D line. the circled point being the problem

Re: Point Check

johnd — Mon, 14 Aug 2023 15:22:02 GMT

So you are suggesting I make another selection set

Re: Point Check

Kent1Cooper — Mon, 14 Aug 2023 15:36:47 GMT

@johnd wrote:

So you are suggesting I make another selection set

Don't you already have it? In what form do you have the "... cogo points that are used to make up a 3Dpolyline"? Whether it's a list or a selection set, you can remove everything in the set found by Fence selection from that, and see what's left. If it's something else, is it in a form that can be made into a list or a selection set?

Re: Point Check

johnd — Mon, 14 Aug 2023 15:44:21 GMT

this may be where I'm getting lost. the points that make up the list COGOLIST are selected by the fence made by the list of verticies (Plist) on the 3Dline. so if the fence does not cross the point it does not get put into the list. So how do I identify the point that is not in the COGOGLIST? Do I make another list of all the points then compare the two lists?

Re: Point Check

Kent1Cooper — Mon, 14 Aug 2023 15:52:37 GMT

You haven't answered my question: In what form do you have the "... cogo points that are used to make up a 3Dpolyline"?

If the 3DPolyline was made from them, you must already have them in some form or other.

Re: Point Check

johnd — Mon, 14 Aug 2023 15:56:07 GMT

I guess I'm not unerstanding what you mean by form. this is a snippet of the list

It is the coordinates of all the cogopoints selected.

Re: Point Check

Kent1Cooper — Mon, 14 Aug 2023 17:50:40 GMT

@johnd wrote:

I guess I'm not unerstanding what you mean by form. this is a snippet of the list

It is the coordinates of all the cogopoints selected.

I meant is it [in the form of] a list, or a selection set, or something else [maybe a spreadsheet file]? When you say "all the cogopoints selected," do you mean those selected afterwards by Fence from the 3DPolyline's vertices? Or do you mean the ones beforehand, from which the 3DPolyline was drawn?

Re: Point Check

Sea-Haven — Tue, 15 Aug 2023 03:33:13 GMT

In CIV3d you can have say 1000 COGO points, a point group can have from none or 1 to 1000 points in that group, so your saying you have a group say called Pline1 which matches the vertices of a 3dpline.

In your image post 5 you show a COGO point with a label which is not part of a 3dpline. So it will not be added to the PLINEX group.

Thats where I got to and are confused about what you want. Post a before and after dwg, but remember not every one has CIV3D.

Are you stringing points based on field codes and a point has been missed or something?

Re: Point Check

johnd — Tue, 15 Aug 2023 12:12:45 GMT

Ok, I'm going to try and describe my question again.
The 3Dpolyline is created using the Create line by point object. These point objects will eventually create a list (COGOLIST).
I select the 3Dpolyline and create a list (PLIST) of all the coordinates of the veriticies.
With this list I create a fence that selects all the cogopoints that make up this line and create a list (COGOLIST).
All the points in this list are put into a points group of a name selected by the user.
IF all the verticies have a cogopoint connected to it, all is fine.
But, in the creating the line, the designer may create a vertex where there is no point, or,
he may miss the point and move on to the next one.
If the vertex has no point attached that is easy to locate, If member of PLIST is not a member of COGOLIST, draw a circle at the vertex
If the point is not connected to a vertex, it locates the point, if member of COGOLIST is not a member of PLIST, draw a circle at the point
But, and here is the issue:
If the point node does not reside at the vertex the routine will pickit up, IF the point label crosses over the 3DPolyline.
If, as in the snippet posted above, none of the point or its label touches the 3DPolyline, it is not selected with the fence method and is not detected.
In that case, the COGOLIST to PLIST does not succeed.
I was considering creating another list, (COGOCHK), perhaps by crossing window to pickup all the points, then run a comparison between
it and COGOLIST, but I'm looking for other suggestions.

Re: Point Check

komondormrex — Wed, 16 Aug 2023 06:16:37 GMT

if cogolist is prime data and your objective is to find cogo points missed in building 3dpline you may try to check every cogo point to find closest point to it on 3dpline, then get the parameter of point found and if it is a 3dpline vertex its parameter will be floated integer like 1.0, 2.0 and so on, otherwise the cogo point was missed in building 3dpline or additional proximity checking of cogo point to a vertex on 3dpline should be accomplished. no comparison of lists. that is what i am thinking on this.

Re: Point Check

Sea-Haven — Thu, 17 Aug 2023 07:26:19 GMT

OK back to CIV3D why are you picking points and joining ? CIV3D has stringing but a point must have a code / Description key loading the points file will string all the correct coded points. We have done this since the 80's no CIV3D then it was other software.

Post a COGO point property listing. Ours would be like num,X,Y,Z,Code where code would be say 23EB meaning 23rd edge of bitumen string only 23EB's join together.