Using Spring Nodes, we next use to separate out each dimension individually. Once we have the filtered list of families, we need to take the bounding box of each element, we do this with an Element.BoundingBox node. This is because every family in the view will be prefixed with Family Type: whereas non-family objects will not. Just in case there is anything in the view that isn’t a family I’m getting the element type of each element, convert that value to a string and then filter the list based on the string “family”. The way that I approach the majority of my COBie work is through a 3D view and a schedule with a set of very hand filters, so I’ve continued down this route for my Dynamo graph and I start it off by getting all the elements in the active view – my 3D COBie view. If you save your old 1.3 graphs in 2.x, it’s now a 2.x graph forever. I put this one together in Dynamo v1.3, but I have tested it in v2.x as well and it still works just fine, just a note though. Well there is no need to stress, as always there is potential for Dynamo to come to the rescue.
So you’re new to COBie and a deadline is approaching, your favourite project BIM manager comes up to you a few hours before the deadline and tells you “We have to do dimensions.
0 kommentar(er)
