I have just added two nodes to the Data-Shapes package:
The names of the nodes are pretty explicit: they gather elements in linked documents visible in a host view.
GetLinkedElements.ByHostView uses the visibility settings of the host view when collecting the linked elements, whereas GetLinkedElements.ByHostViewAndCategory allows you to set the categories you’re interested in collecting.
Both nodes can be found in Data-Shapes Package (version 2017.02.20).
I recently sliced off a few nodes focused on package management and have placed them in a new package called RollingPin.
Current Node List:
Check DYF folder for Dependencies in Package Folders
Get DYF Dependencies for One DYF File
Get DYF Dependencies through Recursion v1
List Nested Node Nicknames for Folder
List Nodes in DYFs for an Entire Folder
Node Names From Directory String
Package Folder Details
Report Dynamo Package Details by Folder
Show Dependency Ids for one DYF
Show Dependency Nodes for one DYF
Summary and Node Search for a Folder of DYFs
The workflow assumed that the model contains all trades in one file. But most of cases each trade exists in its own file and based on the linking technique used in your firm the relation between the trades projects defers.
In this example I assumed that the architecture linked the piping file to the base model project, because most of cases the architect will be the responsible for making the opening in the walls of his model.
This node will take a series of close model lines and output a points list based on a chosen resolution (Default resolution is 20). It will output the information in both a Single Point list and a Grouped Point list based on the X-Coordinates of each point.
This node will take an input of model curves (Model Lines / Detail Lines) and output a series of extent information: The centre points and corner points of the extent frame, the centroid and the external rectangular extent frame.