Month: June 2016

lukesjohnson

Resource: Dynamo for Grasshopper Users

Paul Wintour has created a 15 page document that outlines the differences and similarities between some Grasshopper and Dynamo Nodes. If you know one of the programs but not the other, this may be a good place to start…

Download at: Dynamo For Grasshopper users pdf

 

Dynamo For Grasshopper users_1600x2100From Parametric Monkey:

To assist Rhino users in becoming acquainted with Dynamo, I have produced a ‘Dynamo for Grasshopper Users‘ primer. Since everything is a little different in Dynamo, the primer provides a list of ‘translations’ in order to find a comparable node/component.

GrasshopperToDynamo_1600x800

lukesjohnson

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.

lukesjohnson

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.

davittlamonarch

Workflow: SRTM Data to Topography in Revit

Overview: This workflow allows the user to source SRTM Data in GeoTIFF format from http://earthexplorer.usgs.gov/, and use it to create topography in Revit. Shuttle Radar Topography Mission (SRTM), was carried out by Nasa in 2000 and recorded elevation data. This data has been made available globally at 1 Arc Second, and in more detail at 1/3 Arc Second for some parts of the US.

Packages: ‘Elk’.

Download Script: Dropbox link

header

Continue reading

lukesjohnson

Family Instance By Point in Transaction

Some family placement nodes consume previously placed families if run with List.Map. This node was adapted from Clockwork, and it just wraps a ‘Family by Point’ command to ensure that each list of points is processed in a separate placement transaction in Revit.

Credit to Dimitar Venkov for the assist.