topic Re: Section/Clipped View Geometry List in Navisworks API Forum

Section/Clipped View Geometry List

nasip13904 — Mon, 30 Jan 2023 14:17:31 GMT

Is there a way to get the model list which is present in section/Clipped box not whole model list which we got through oDoc.Models?

Re: Section/Clipped View Geometry List

timw3333 — Tue, 31 Jan 2023 08:11:31 GMT

Get JSon text of current clipping box using GetClippingPlanes API. Then define new BoundingBox (oBox).
LINQ search will be something like this (though it's very slow)

items = From item In Search.FindAll(oDoc, False) Where item.BoundingBox.Intersects(oBox)

Re: Section/Clipped View Geometry List

nasip13904 — Thu, 02 Feb 2023 11:34:51 GMT

Box Section provides the oriented box value, I understand that but how do I do with just the planes section, as those do not provide any bounding box?

Re: Section/Clipped View Geometry List

timw3333 — Fri, 03 Feb 2023 01:09:28 GMT

Define section plane as LcLPlane3f (oPlane)
LINQ search must be something like this;

items = From item In Search.FindAll(oDoc, False) Where (item.BoundingBox.Contains(oPlane.ClosestPoint(item.BoundingBox.Center)) OrElse oPlane.GetNormal.Dot(item.BoundingBox.Center - oPlane.ClosestPoint(item.BoundingBox.Center)) > 0)

Re: Section/Clipped View Geometry List

alexisDVJML — Sat, 18 Feb 2023 11:03:21 GMT

Since I think this will first build a list of ALL items in the model before applying the LINQ filter, I wonder how long such search would take on even a reasonably sized model?
Interested since this is kind of useful feature

Re: Section/Clipped View Geometry List

timw3333 — Sat, 18 Feb 2023 12:03:01 GMT

I'm working plant engineering/construction. Model data file size is several GB.
So LINQ filter to whole model data is not practical at all.
I always use Property filter first to limit the number of target elements before applying LINQ filter.