![revit view range revit view range](https://www.revit.news/wp-content/uploads/2017/07/1498881074_maxresdefault.jpg)
Each sublist holds as many items as there are total parameters (columns). that’s the first data point in all of my sublists. Each key schedule comes standard with a Key Name parameter already loaded and added to every new row. Each element then has as many parameters assigned to it as there is parameters (columns) in the schedule. If you know how KeySchedules operate under the hood in Revit then you know that each row of in a key schedule is an element in Revit DB (like a family). It will then take the data supplied and fill in the parameters for each row. This node will take a key schedule created in Revit and add rows based on number of data points in the Data input. Now this node WILL NOT CREATE a Key Schedule. It also outputs them pre-sorted for the current view. This node will get you all of the Filled Regions in the model. This node will retrieve an area of a filled region. This makes it easy then to join all of the curves into polycurves while maintaining the association with the original source. Each loop of curves then will be outputted as a sub-list for that filled region. This node will query all of the boundary curves from a give filled region. Instance? – This is a True/False setting that will either make this an instance or type parameter.Parameter Group – Use Parameter Group node to get a value for this input.In the example below its a Generic Model but could be Furniture, Casework etc. Element Category – This is a category that the parameter will be added to.Visible? – This is a True/False setting that will either make this parameter visible to the user or make it only accessible via API.Parameter Type – Use the Parameter Types node to get a value for this input.
![revit view range revit view range](https://i.ytimg.com/vi/oPeAmuPjJcM/maxresdefault.jpg)
Keep in mind that this is not the same as Parameter Group. Shared Parameter Group Name – This is a name of the group that the parameter will be stored in the shared parameter file.If this parameter is a list then Visible and Instance have to be lists of the exact same length. Parameter Name – This can either be a list or a single string.Here’s what the inputs are supposed to be: As you can see in the image below it can create either a single parameter or a number of parameters. First it creates a parameter in the Shared Parameters file and then adds it to the project. A Parameter Group is where visible parameters are displayed in the Properties box when element is selected. This node will get you all of the Parameter Groups available in the project. Most well known Parameter Types are Yes/No, Text, Integer etc, but bear in mind that this is a list of all available types from Revit API so it will also contain some types like HVACCoolingLoad or BarDiameter which clearly are meant to be used with MEP and Structural models. This node comes helpful when creating a new parameter in the project. This node will query up all available Parameter Types. Link Document input can be obtained from another archi-lab package node called Get Documents. It will retrieve all elements of a given Category from a given linked model.
![revit view range revit view range](https://vnk.edu.vn/wp-content/uploads/view-2d-trong-revit-mep.png)
This node is a slight modification to Julien Benoit’s node published in his Steam Nodes package. Those two custom nodes can be found inside of archi-lab package. Use Get Rooms by Level to get a list of rooms by level that excludes unplaced rooms.
![revit view range revit view range](https://images.squarespace-cdn.com/content/v1/57c87c34e58c6258d91567bd/1482420071259-99XN80I99DGOZHDPYD3R/image-asset.jpeg)
Use Get All Elements From Linked Model to get family instances from linked model. The output will be a list of families grouped into sublists that match the order of supplied rooms which makes for easy grouping of all families within a room. This node will check all of the supplied elements if they are located in any of the supplied rooms. Use Get Rooms by Level to get all rooms per level that are placed. Use multiple All Elements of Category nodes to combine specified category types of elements. The output will be a list of families grouped into sublists that match the order of supplied rooms, which makes for easy grouping of all families within a room. If you want to tag all elements in a single view, you don’t have to duplicate it – just plug in that single view. Make sure that the list of Points, Views and Elements to be tagged are matching in length. This node will create an annotation tag in a specified place (points, views).