Add Boundary to TIN Surface

[BlackBox]

Likewise!

I'm (slowly?) building the routine, piece by piece, right now.

I tested the elapsed time from building a single floodplain (flat) surface manually, and compared that against my *current* piece-meal automation, and the routine was +/-1 minute to +/-6.4 seconds, respectively. (approx 10 times faster!)

The performance gains (so far) were even better when stepping through a selection set (thank you vla-zoom*!) of the 16 individual basins (each at a different elevation) for my current sub-phase of work (of 3 phases). Whew! lol

Again, many thanks!

[BlackBox]

Actually, this will keep you from having to append the point lists.

(defun AT:VertexPointsForArray (e / p l)
  ;; Return point at each vertex of LWPolyline or Polyline (in single list)
  ;; e - LWPolyline, 2DPolyline, 3DPolyline
  ;; Alan J. Thompson, 09.24.10
  (if e
    (repeat (setq p (1+ (fix (vlax-curve-getEndParam e))))
      (setq l (append l (vlax-curve-getPointAtParam e (setq p (1- p)))))
    )
  )
)

This too is very helpful.

Note - I just need to precede this function with (vla-put-elevation lineObj basnElev), otherwise the resulting point list includes 0.0 as the elevation.

[alanjt]

This too is very helpful.

Note - I just need to precede this function with (vla-put-elevation lineObj basnElev), otherwise the resulting point list includes 0.0 as the elevation.

That's odd, it shouldn't. It will report the correct Z for each vertex on my end.

[BlackBox]

That's odd, it shouldn't. It will report the correct Z for each vertex on my end.

Exactly. The polyline I am selecting has a 0.0 elevation, hence the need to use (vla-put-elevation lineObj basnElev) prior to (AT:PointList->Array (AT:VertexPointsForArray eName)).

No biggie.. it's just a 'lil error checking, or an additional mapcar on my end. I mean, I *could* just leave the basins at their Z-values...?

Curious. It's Friday, and I am leaning toward the path of least resistance. Shocking. lol

[alanjt]

Exactly. The polyline I am selecting has a 0.0 elevation, hence the need to use (vla-put-elevation lineObj basnElev) prior to (AT:PointList->Array (AT:VertexPointsForArray eName)).

Oh OK. I didn't realize your curve was at a zero elevation, to begin with.

[BlackBox]

Oh OK. I didn't realize your curve was at a zero elevation, to begin with.

You'd laugh....

My drainage Engineers use GIS & ACAD to produce shapefiles for me to import for drainage basins, etc..

I use ._mapimport to bring in the line work with Object Data (OD), and I have some schnazzy routines to check for discrepancies between the OD area value vs. the calculated areas of the closed polylines imported, extract and label the catchment names, etc. (Hooray, ade_od* functions!) .

My drainage engineers don't even have MAP... They're relegated to using vanilla ACAD, so they cannot even see the OD (once I've saved the shapefile import to .dwg) in the drawings I create to verify, etc.

Edit: The polylines are at 0.0 because they came from my drainage engineer.

Oh, well... at least there's job security. lol

[BlackBox]

Good deal. Can't wait to see the finished product.

Unless I can find a programmatic means of closing a surface once it has been opened, there will not be any finished product to speak of.

Each time a surface is built, the surface is opened. This also applies to the resulting volume surfaces (DifferenceGrid in this case).

Without being able to close the surface once the required tasks are complete, the Page File usage continues to grow, until AutoCAD's memory is used up, resulting in a terminal failure (crash).

[89139290787693941]

Hi!
Tell me please, how to get the coordinates of the boundaries?

Found how to extract the border, in principle it is possible, then from the resulting 3D polylines get the coordinates, but why the extra traffic?

(vlax-invoke-method surf_object 'ExtractBorder 1)