This node will get elements from a Link Instance given the instance object and a Category. It also reports a ‘coordinate transform’ for the Link Instance itself.
You also have the option to simply pick the linked instance with the “Select Model Element” node:
This node will collect objects by doing a wildcard ‘contains’ search on part of the Link Filename, and then using the Built-in Category Name to collect the desired objects. It can be used with the ‘convert…’ node below to allow human readable category name input as string.
This node takes an integer as input.
Returns the “alphabetical equivalent character”, and a list from A to the alphabetical equivalent character.
It only works from 1 to 26 (A to Z). [See NumberToCharacter AAZZ for higher inputs]
After this, returns a “Out of range” message.
The node uses DesignScript to work:
There is a local variable, “a”, which is an alphabetical list.
The input, named index in the code block, is evaluated to see if it’s less or equal than “a” count:
index<=List.Count(a). This is passed into a formula node as the “Test input”.
If it’s true, then, it retrieves the index, less one, in the alphabet’s list. We subtract one unit because we want to make our input “one based”, instead of “zero based”. 1 will equal to A.
If it’s false, the string “Out of range” is passed to the output node.
For the second output, a new list called “b” is defined. Starting with “a” list, it is “choped” in two lists, been the input the chopping point.
The last step is getting the first list, so a” b[0]” is used and passed to the second output. This second output is also connected to te “Out of Range” string if the condition is not true.
ImportFile takes the name of a file as input, and outputs a Mesh object. The file can be of the following types:
.obj – Wavefront OBJ file
.mix – Meshmixer file
Source: https://github.com/DynamoDS/Dynamo/wiki/Dynamo-Mesh-Toolkit
This node reports the Level an Element is associated with:
This node allows you to select objects by simply specifying a Level as input using the Levels node:
This node requires Floor objects that have been populated with a Comments parameter as an identifier. In the workflow example below, a linked model contains the Floors. These are selected and filtered to the specific Level and identifier, and with that one Floor object in hand, the Dynamo script goes on to make a Section Boxed 3D View around that Floor, Set its Name, and Set a View Template to the newly created view.
This node generates a string for input to the ECCLevel input of QRCode node. When run first time it opens a drop down window where one can select between the 4 levels of error correction level on QR codes. L, M, Q or H for 7%, 15%, 25% or 30% respectively.
Inputs:
Credits: The Ironpython script used in this node is largely based on Dimitar Venkovs selection nodes from the sping nodes package. It is licenced under the MIT licence.
Form a Point given 3 Cartesian coordinates.
This was developed as part of the workflow to convert Rooms to Floors. Revit needs ModelCurves, but to get there Dynamo needs to make Polycurves from the Room boundary. Simply send a list of Rooms as input:
Dynamo Nodes 