this is file from the picture and there is alot of these polylines whitch are so close next to each other but i need it deleted or just 1 line just to get good total lenght and its only if there is only 1 line and no overlapping lines.
Check your settings in the OVERKILL dialog box. Maybe you have too tight a tolerance, or need to have it ignore more properties. I used it to eliminate over 1700 objects/segments from your drawing with a tolerance value of 0.1.
yes i know i this so many times overkill, explode, join, again overkill etc and lost like almost all overlaping but problem is with this like 3 polylines next to each other whitch are not overlapping, I want them do join and make just one, like to pick one of those 3 polylines and melt into it. so i can get real lenght not like 3x... maybe there is something for this i ll try to find out, thank you so much anyway ❤️
@Fleww wrote:
.... problem is with this like 3 polylines next to each other whitch are not overlapping, I want them do join and make just one....
Can you set a large-enough tolerance value in OVERKILL that it eliminates 2 of them? [If you can, I assume you would have no control over which of them it keeps.]
@Fleww wrote:
Tryed but not enough. 😕
I think something's wrong about the description or implementation in OVERKILL regarding the Tolerance setting in the dialog box.
These 3 Line objects all meet at their other end, and are about 200 drawing units long, and the difference in X value at this end is only 0.01 unit. I tried OVERKILL with a Tolerance value of 0.5, which is hugely more than the difference in these endpoints' positions, but it didn't consider them "duplicate."
Help for -OVERKILL describes the Tolerance setting, which sounds like it ought to consider these overlapping:
Tolerance
Defines the value within which OVERKILL makes numeric comparisons for determining object duplication.
I wonder if my old DUPDEL.lsp would work.
It was created long before OVERKILL and even LWPolylines were born (c. 6-21-97)
I'll have to redact it and remove the security and test it out.
I know that it compares two lines both as-is and reversed with user input for the "fuzz" tolerance.
It does not treat collinear lines of different lengths as duplicates; it compares the ends.
I doubt if you care, but it also compares Xdata if you so choose.
John F. Uhden
It appears to still work, at least for lines anyway.
I tested with 3 lines on the same layer, each about 0.5 units from each other at one end.
I used a fuzz of 1 and bada-bing, the later 2 were deleted.
Bear in mind I removed locked layer checking 'cause the code was in another file.
There's a revision note in the file that says it handles LWpolys, but I don't remember how.
John F. Uhden
That vacuums.
Please post a sample dwg.
John F. Uhden