-
Notifications
You must be signed in to change notification settings - Fork 14
BHoM vs Revit identity
Exchange of information between Revit and BHoM often requires linking the objects from both sides with each other, e.g. when querying the model for changes or updating it. The mutual relationship is being created and maintained as follows:
- On Pull, the identifiers of pulled Revit element are stored in
RevitIdentifiers
fragment attached to the resultant BHoM object. - On Push, Revit element is being considered correspondent to a BHoM object when the latter contains a
RevitIdentifiers
fragment with value ofElementId
property equal to the ElementId of the former.
Additionally, tags can be assigned to Revit elements on Push and BHoM objects on Pull, which can mark them as related to a particular Adapter action.
-
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