![\"Surfaces_Horizontal_\"](\"https:\/\/www.modelical.com\/wp-content\/uploads\/2015\/11\/Surfaces_Horizontal_.jpg\")
<\/p>\nRhinoceros and Revit are programs with different properties. While Rhinoceros is a good option for modelling complex surfaces and geometries with precision, Revit is a high quality program for modelling with information. So working with both programs in a properly way can easily implement and optimize our work. Most times\u00a0we will use Revit as the main platform of work and just will\u00a0need\u00a0Rhinoceros to model complex geometry (mostly surfaces) that would\u00a0be really hard to do in Revit.<\/p>\n
<\/p>\n
Thinking about the possible workflows between Rhinoceros and Revit, we point out these three options as the main ones:<\/p>\n
– Direct import of the Rhino geometry (sat or dwg formats) into Revit scenery. This option is a valid one for volume reference in Revit, using the imported geometry without material properties.<\/p>\n
– Import the Rhino geometry (sat\u00a0or dwg formats) into a Mass in Revit. This is the best\u00a0option to convert\u00a0the geometry imported into native elements in Revit (floors, walls, ceilings and curtain walls).<\/p>\n
– Import the Rhino geometry (sat or dwg formats) into a Family in Revit. This is an option to model complex geometry families in Revit.<\/p>\n
<\/p>\n
With the purpose to determine which is the best format to export surfaces from Rhino into Revit, we have\u00a0analysed the main types of surfaces in Rhinoceros.<\/p>\n
<\/p>\n
For each type of surface we have analysed how it works when we import them into Revit with different uses:<\/p>\n
– Geometry Reference\u00a0without\u00a0properties in Revit<\/p>\n
–\u00a0Geometry Reference\u00a0with material properties in Revit<\/p>\n
– Conversion to Native elements in Revit<\/p>\n
– Generate Families in Revit<\/p>\n
In order to have some useful data about the testings we have done, we have generated the following table with the conclusions of the studio:<\/p>\n
![\"\"](\"https:\/\/www.modelical.com\/wp-content\/uploads\/2015\/11\/Table_2.jpg\")
<\/p>\n
The importation\u00a0in Dwg format\u00a0shows problems both with very simple geometries (horizontal and vertical planes) and with too complex, especially open polisuperfices. Also, the imported geometry remains the source layers, which is important to manage the imported geometry.<\/p>\n
When importing in this format, certain issues may become problematic. Some are permanent, always happen, others only in certain cases.<\/p>\n
Permanent problems:<\/p>\n
– The following surfaces cannot be imported in Revit in Dwg format: planes (horizontal, inclined or vertical), open or closed polisurfaces, complex surfaces and collapsed ones.<\/p>\n
Occasional problems:<\/p>\n
– Heavy files. If the imported geometry is complex it will increase considerably the size of the Revit file, thus will slow the rhythm of work\u00a0and\u00a0the visualization.<\/p>\n
– Visualization: Tangent borders. Some geometries with curve surfaces may not be visualized correctly. Also in an elevation view it may occur to see\u00a0incorrect lines.<\/p>\n
<\/p>\n
The importation in Sat format is considerably good, mainly with simple surfaces, while with complex surfaces it may occur some problems.<\/p>\n
When importing in this format, certain issues may become problematic. Some are permanent, always happen, others only in certain cases.<\/p>\n
Permanent problems:<\/p>\n
–\u00a0Loss of information from layers. When you import in\u00a0Revit, layer information disappears, so\u00a0you might have into account it before exporting the geometry for Rhino. One solution is to export each layer in Rhinoceros in a different file, so that we can manage the different files in Revit and apply different materials to each file.<\/p>\n
Occasional problems:<\/p>\n
– Heavy files. If the imported geometry is complex it will increase considerably the size of the Revit file, thus will slow the rhythm of work\u00a0and\u00a0the visualization.<\/p>\n
– Visualization: Tangent borders. Some geometries with curve surfaces may not be visualized correctly. Also in an elevation view it may occur to see\u00a0incorrect lines.<\/p>\n
<\/p>\n
Some of the main conclusions that can be drawn from the analysis of imported surfaces in Revit are:<\/p>\n
– Generally Sat is a better exportation\u00a0format than Dwg.<\/p>\n
– Revit does not import planes.<\/p>\n
– Revit is not a good software when importing complex surfaces: open or closed polysurfaces.<\/p>\n
– When we import\u00a0a\u00a0surface to convert it into native elements in Revit, we have to be aware that some surfaces work for walls and some for ceilings, but rarely we will be able to convert a\u00a0surface\u00a0both into walls or ceilings.<\/p>\n","protected":false},"excerpt":{"rendered":"
The purpose of this post is to cover some of the different workflow options between Revit & Rhino and find out which is the best format to export the Rhino geometry depending on the use we will need in Revit.<\/p>\n","protected":false},"author":5,"featured_media":27098,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[4],"tags":[411,785,649],"class_list":["post-3251","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guidelines","tag-technology-revit","tag-technology-revit-workflows","tag-technology-rhino"],"acf":[],"yoast_head":"\n