Author Topic: Create Surface - Filter levels  (Read 43326 times)

EvylRat

  • Newbie
  • *
  • Posts: 16
Create Surface - Filter levels
« on: October 25, 2013, 05:06:06 PM »
Version 688.

I have a 3d survey, with some annotations and construction lines drawn with a Z of 0. When I triangulate them, even specifying a filter greater than 0 for the minimum Z, it still uses Z of 0 somewhere, giving me a spike in the my contours. I will have to hide the layers.
I think (once this works) that the default could be 0.001, to stop these FLAT parts of the drawing for ruining a triangulation.

When looking at the statistics for the triangle data, there IS a reduction in the number of triangles, but the Min and Max elevations do not match what I set the Filter option.

UPDATE: The point that it is snapping to is on a polyline, is closed. However, when I open the polyline, it still appears to be closed. Could the polyline be confusing the filter?
« Last Edit: October 25, 2013, 05:22:35 PM by EvylRat »

Lars

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
Re: Create Surface - Filter levels
« Reply #1 on: October 25, 2013, 10:56:24 PM »
Hi!

The filtering process is used on every point that will be included in the triangulation. You must set min and max values before selecting objects in the DWG. To get rid of polylines with elevation of zero you should set minimum Z to 0,001. However there is a bug in the filtering, the first point in the selection set passes without any control of elevation. Therefore you will in some cases (when you have selected a object with zero elevation first, by crossing or whatever) end up with one point with elevation of zero which ruins the triangulation. This bug will be fixed in next update, meanwhile you could hide or unselect object with elevation of zero.

Thanks' for making me aware of this!

/Lars

Lars

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
Re: Create Surface - Filter levels
« Reply #2 on: October 25, 2013, 11:26:35 PM »
The update that fixes this issue is now available for download (Build 689)

EvylRat

  • Newbie
  • *
  • Posts: 16
Re: Create Surface - Filter levels
« Reply #3 on: October 28, 2013, 01:35:40 PM »
Resolved! Your latest update (build 689) has fixed the issue of a point skipping the filter check. Tested and working on the dwg I supplied above.

EvylRat

  • Newbie
  • *
  • Posts: 16
Re: Create Surface - Filter levels
« Reply #4 on: June 18, 2014, 05:37:54 PM »
Sorry to resurrect an old post. In version 698 the filter is broken. If you ask it the surface creation to use BREAKLINES, the filter is ignored.

Lars

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
Re: Create Surface - Filter levels
« Reply #5 on: June 18, 2014, 10:07:47 PM »
Hmmm… I’ve missed that combination, thank’s for making me aware of this.

If you are using breaklines you should not use the filtering option. CadTools stores all selected objects vertices and insertion points in a array. Finally all points are filtered for min and max values, those inside the filtering span are excluded from the array. This works well because we are dealing with points.

Breaklines must be excluded from filtering otherwise the triangulation will be a mess. If you have a breakline with two points, one inside the filtering span and the other outside it. Excluding one of the points will turn the line to a point and that won’t work as a breakline. Probably that’s what you have noticed.

The best solution would be to make CadTools leave all breakline points unchanged while filtering. This will need a major redesign of the pretriangulation process, it will take a couple of days to fix.

/Lars
« Last Edit: June 18, 2014, 11:12:08 PM by Lars »

EvylRat

  • Newbie
  • *
  • Posts: 16
Re: Create Surface - Filter levels
« Reply #6 on: June 18, 2014, 11:24:41 PM »
Not a problem! I should probably just hide all entities that should not be included in the surface creation.  I love this program!!!

Lars

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
Re: Create Surface - Filter levels
« Reply #7 on: June 20, 2014, 11:50:24 AM »
This is fixed in Build 699