This tutorial explores how you can translate geometry from Rhino to Revit via Excel using an adaptive component family. The first stage is to generate some geometry within Rhino/Grasshopper. Below is a simple panelisation script that can be exported to Excel. Note the use of the path mapper component to group all of Pt1 together, and all of Pt2 together, etc. as we want the data to be structured in rows, not columns. Also, the replace component is used to delete the curly brackets. The Lunchbox ‘ExcelWrite’ component is used to export to Excel. Note that Excel needs to be open first before it will export.
Your Excel file should look something like this with 4 columns and each cell containing an XYZ coordinate.
Ensure that your 4-point adaptive component family (or however many points was exported) is pre-loaded into your Revit project. We can then use the ‘AdaptiveComponent.FromExcel’ node to populate our Revit model with the desired adaptive component.
If you receive an error, which usually takes the form of adaptive components not being placed or collapsed to the ground plane, check these common issues:
- Ensure that the normal to your surface is correct. Depending on the complexity of your Revit family, if the order of placement points is reversed, the adaptive component can fail. The best way to check that your normals are correct is to go into Rhino’s display options and set the backface settings to be a single colour. This will give you a visual reference of the surface’s direction.
- Ensure that the tolerance of your Grasshopper script is correct. If the tolerance is set too high, Grasshopper will return the XYZ coordinates of a point using scientific notation. This means that you will have an ‘e’ in the value. Since we are converting this value into text, Dynamo will be unable to generate a coordinate from it and hence, unable to place the adaptive component. To solve this issue, you will need to format the values to reduce the number of decimal places. More info on this topic can be found here.