Trimble Quadri Help
TrimBIM is a format for visualizing other formats. It is therefore a format with many dialects - all depending on which origin file format that is used when creating the TrimBIM. For example a TrimBIM created from a dwg-file will differ from one created from an IFC-file.
When importing files into Quadri, one should always use the origin source file behind the TrimBIM if possible. Importing DWG, DGN, IFC, LandXML etc instead of TRBs based on these formats, will give a better input result of the desired data.
Follow the general steps in Import Files.
Specify options in the TrimBIM Reader Settings Editor’s Import Settings.
Click OK.
Complete additional steps in Import Files.
Click Finish.
Although importing TrimBIM can be used as a backup for importing other supported formats - a special area of use would be to allow importing data from formats/softwares that is not otherwise supported. TrimBIM will for example allow data from Revit (.rvt) to flow into Quadri.
A Revit user may upload data from Revit using Trimble Connect for Revit. This will render a TrimBIM file in the Trimble Connect project. Import this file into Quadri by selecting the files from Projects:
To streamline the integration between several softwares and Quadri, we are providing TRB Import Conversion Rules for versions 1.x, 2.x, and 4.x. These rules are designed to automate data classification and ensure that complex civil BIM data is preserved during the import process.
For standard Quadri and legacy catalogs, the conversion rules utilize Proxy Object Mapping.
For IFC type catalog, the conversion rules utilize IFC Entity Types for mapping
1. Smart Entity Classification
The importer now prioritizes IFC Entity Types for mapping. This fits importing data from Revit especially well, since the Revit TRB export utilizes IFC-based logic. This alignment ensures that your elements (e.g., walls, slabs, or custom civil components) are categorized correctly within Quadri.
Safety Net: A "Catch-All" rule is included at the end of the logic chain to ensure that even elements without a defined IFC type are successfully imported rather than being dropped.
2. Automated Attribute Population
We have implemented Structure Mapping (S) to handle metadata.
Generic Property List: All source attributes from your TRB file are automatically mapped and populated into the GenericPropertyList. This ensures that custom data fields from Revit remain accessible and searchable within the Quadri environment without requiring manual configuration.
3. Intelligent Layer Management
For users managing multi-layered models, we have introduced Dynamic Layer Concatenation.
Using automated expressions, the importer identifies and maps numbered layers (e.g., "Layer 1", "Layer 2") to their corresponding counterparts in Quadri, maintaining the organizational structure of your original design file.
4. Optimized Legacy Support (1.x & 2.x)
For standard Quadri and legacy catalogs, the conversion rules utilize Proxy Feature Mapping. This approach optimizes performance by simplifying data filtering, allowing Revit-based IFC data to be parsed quickly while maintaining the integrity of the geometry.
Zero Data Loss: All Revit attributes are captured via the GenericPropertyList.
Predictable Imports: Elements are categorized based on industry-standard IFC types.
Cleaner Models: Automated layer naming keeps your Quadri model workspace organized.
When importing aTrimBIM that contains alignments - please be aware of that it is only the Design Curve geometry of the alignment that is imported. If the imported geometries are to be used as alignments in the project - use the Alignment tool and select the imported design curve data as input. This will create the Alignment design task required to support further design work involving alignments.
Currently there are som known issues when importing TrimBIM into Quadri:
Billboards are not supported: if importing billboards, only the insertion point will be displayed as default.
Textures are not supported: colours from geometry can be viewed but not textures.