lukesjohnson

CustomNode.Info

This will take the File  Path to a dyf file as input, and return many properties of that node. In the example below, List.Map is used to iterate through and return only the Node name.

Custom Node Info

msalvadoraltava

Element.FilterByParameterValue

This node gets a list of elements [list], a parameter name[string] and a parameter value [].

Checks if the elements parameter is equal to the given value, and splits the elements list in two: the first been “true” and the second been “false”Element.FilterByParameterValue

This node is built using OOTB nodes with nothing special in it.  But sumarizes a task we do in almost every definition.

Element.FilterByParameterValue_inside

Here follows a little example of this node in action:

We input all the rooms in the project, then get only those having “Comments” parameter equal to “revestir”Element.FilterByParameterValue_inAction

dimven

FamilyInstance.ByGeometry

This node converts a Dynamo surface, poly-surface or solid into a Revit family. It then places an instance of that family inside your project, reflecting the geometry position from inside Dynamo. It currently supports Revit 2014 to 2016.

Revit_2016-01-12_21-53-47.png

The most important inputs are:

  • The geometry objects
  • A file path to a family template (It is crucial that the family template version matches your Revit version)
  • A unique family name for each geometry object

The optional inputs are:

  • Category. The default value is Generic Model. Some templates, like the conceptual mass, do not allow changes to the family category. In those cases the built-in category will remain in force.
  • Material of the family, provided as a string. The material must be pre-loaded into the template for this option  to take effect. If a material with such a name does not exist in the template, the default “By Category” material will be used.
  • Void switch provided as a Boolean ( true / false). The default value is set to false. If you provide a true value, the newly created family will act a void cut element and will be able to perform cuts on  structural elements, generic model elements and host elements.
  • Subcategory provided as a string. The default value is null – meaning that this option is ignored. If you provide a subcategory name, it will be generated inside the family document, applied to the family and added to the project together with it.

 

Revit_2016-01-12_22-21-28.png

Do note that by default, the node works in “longest” lacing. That means that if any of the optional inputs are less than the geometry objects and the family names, the last input will be used for all remaining families. In the above image, the families at [6] and [7] will belong to the “Generic Model” category and will act as void cuts.

You can download this sample and others from the Spring Nodes repository:

https://github.com/dimven/SpringNodes/tree/master/Samples

Currently the node does not place multiple geometries into a single family. There is a partial workaround described in the following discussion:

https://github.com/dimven/SpringNodes/issues/10

A node for such cases might be developed in the future.

lukesjohnson

All Elements of Category

This is one of the simplest ways to select Revit objects in Dynamo. Simply feed a Categories selection into this All Elements of Category node, and after the script is Run, those objects will be selected in the Dynamo session.

revit-categories