-
Notifications
You must be signed in to change notification settings - Fork 14
Explicit mapping Revit families to BHoM types on Pull
In some cases, on Pull, the elements of one Revit API type and belonging to one Revit category are meant to be converted into a few different BHoM types. An example of this may be FamilyInstance
belonging to Mechanical Equipment category - this potentially could be converted to multiple BHoM types, such as Exhaust
, Fan
etc. This would not be possible out of the box, but can be achieved using family maps in MappingSettings
.
The picture below shows an example of MappingSettings
structured in a way that will map elements from families BHE_GenericModels_OpeningRectangular_Wall and BHE_GenericModels_OpeningRectangular_Floor to BH.oM.Architecture.BuildersWork.Opening
, plus it will map the BHE_Height parameter to Height
property of the output BHoM object as well as BHE_Width to Width
.
Mapping has been also covered in the Pull examples.
-
Overview:
What is Revit_Toolkit for?
Code structure
Building from source and debugging
License
Sample scripts -
Adapter:
Basics
Revit <-> BHoM conversion
BHoM vs Revit identity
Handling of Parameters
Conventions
Setup in Revit
Setup in Grasshopper
Setup in Dynamo
Setup in Excel
Details -
Pull:
Basics
Requests and filtering
Pull of Geometry and Representation
Pull from Links
Pull in Grasshopper
Pull in Dynamo
Pull in Excel
Examples
Explicit family vs type mapping
Details -
Push:
Basics
Push modes
Updating Revit types
FamilyLibrary
Push in Grasshopper
Push in Dynamo
Push in Excel
Examples
Details -
Remove:
Basics
Remove in Grasshopper
Remove in Dynamo
Remove in Excel
Examples
Details -
References:
BHoM Wiki
BHoM Adapter