A Revit vector property is different to a Dynamo vector ‘object’. Dynamo can work with Vector objects to determine angles and so on. This node takes a Revit vector property and tries to make a Dynamo vector from it.
Bakery
Get Transform Properties from Revit Transform Object
Transform objects (such as coordinate systems) in the Revit API have many ‘members’ or properties. This node takes a Transform object and unpacks most of the useful properties for downstream use.
Get Connector.CoordinateSystem
Connector objects in Revit typically have a ‘coordinate system’. When we extract this coordinate system from the connector, we get a Transform object as shown below.
Get Connectors from ConnectorManager
ConnectorManager objects in Revit typically have various ‘connector’ subobjects. This node reveals the connectors from each connector manager.
Get ConnectorManager
MEP elements in Revit have connections. These connections are typically managed by a special API object called a “Connector Manager”. This node takes a Revit element and returns the connectorManager.
Revit Element Clash Detection v1
We can easily use builtin nodes like Element.Geometry, Geometry.DoesIntersect and Geometry.Intersect to put together a simple clash detection process in Dynamo. However, these geometry nodes bring some processing overhead.
To speed things up, I packaged it all into a Python Script in this node. Basically, it doesn’t have to unpack or ‘draw’ the actual element geometries, so the performance should be better than the standard nodes.
Inputs:
· RevitElementSetA – the first set of elements
· RevitElementSetB – the elements to clash against set A
The node does a full cross-product check to find the clashes.
Outputs:
· clashSetA – elements that clash with same index in set B
· clashSetB – elements that clash with same index in set A
· SetA_GeometryFailures – instances where Element.Geometry (pythonic / api) failed to make a geometry
· SetB_GeometryFailures – as above
· IntersectingSolid – the full geometry intersection between the two clashing elements
· clashPoint – the centroid of the intersectingSolid
This will be made available in Bakery package.
Future versions will likely be ‘chasing more speed’.
Filter Element List by Revit Z Value
This node takes a list of Revit points (feet, XYZ format), unpacks the Z values, converts to mm, and then filters an input list by a given benchmark value.
So, if you know that 90% of your Grids are set correctly with a -300mm lower Grid Z extent, place -300 in the input benchmark value, and you will get a list of ‘not matching’ elements. This allows quick checking of Grid extents that may be inconsistent.
Comma Separated Point Value to Point Object
This node takes a point list from the Revit API (feet, XYZ), and creates actual Dynamo point objects. It allows you to input a scale. To convert to mm, put in 304.8 for the scale.
Comma Separated Revit Data to XYZ Values
This node unpacks point information obtained via the Revit API, which is usually delivered in feet units, XYZ format.
You may need to set Lacing to Longest.
Get Grid Extents
This node uses Python and the Revit API to extract the outline object from each Grid element, and then get the minimum and maximum points from those outline objects. These points are delivered in Revit API format: units are feet, comma separated XYZ.
Dynamo Nodes 