A wide array of design applications are supported in synchronization workflows, ensuring all your engineering data can be aggregated into a single digital twin environment.
You can find the latest list of supported iTwin Connectors here: https://developer.bentley.com/apis/synchronization/supported-formats/
If you are interested in iTwin Synchronizer Client supported connectors, here are the differences from the main list:
If you do not see required connector, you can fill out the idea in your main design review portal ideas page.
MicroStation (via dgn)
Up to and
IFC2x3, IFC4, IFC4.3
2.0, 3.0, 4.0, or 5.0
MIF / MID
Some file types are listed as being supported by "MicroStation" under the connector type and these can be synchronized directly with the MicroStation Connector. Examples of this are FBX, OBJ and SKP. Other file types that are listed as "MicroStation (via dgn)" must first be imported into MicroStation and saved as a dgn, then the MicroStation Connector can be used to synchronize the dgn into an iModel.
Note for .imodel files, they must be referenced into a DGN file and then an i.dgn must be produced in order for the model to be imported with the MicroStation Connector. Support for .imodel 1.5 and 1.6 versions will be dropped with MicroStation CONNECT Edition Update 17.
Reality Data Support
Reality data, like point clouds and reality meshes, can be viewed along with your engineering data. There are no iModel Connectors to sync reality data, instead use Bentley ContextCapture to add real-world digital context to your iTwins.
For more information on how to associate your reality data to an iTwin go to the Reality Data page.
The GeoConnector is being developed to support geospatial data coming from multiple sources.
Presently, Shapefile, PostGIS database, ESRI File Geodatabase, ArcGIS Feature Service, and WFS(Web Feature Service), KML/KMZ, GeoJSON and Oracle Spatial and SQL Spatial database formats are supported.
For more information on how to use the GeoConnector, visit the GeoConnector page.
The Autodesk Material Library consists of several sub-libraries and installers (MSI files) can be taken from installers for Revit, 3dMax or AutoCAD.
Or they can be downloaded separately from the Autodesk site: https://knowledge.autodesk.com/support/infraworks/learn-explore/caas/CloudHelp/cloudhelp/ENU/IWGettingStarted/files/Install/IWGettingStarted-Install-ToInstallAutodeskMaterialLibraries-html-html.html (all resolutions packages are necessary but first Common package isn’t).
It is better to install all Base, Low, Middle, and Advanced Image libraries. At least Base, Middle, and Advanced has unique files.
Materials should be exported to i-model automatically if Autodesk Materials are installed on the machine where the iModel Connector job is executing from.
Navisworks can be used to import the additional formats listed below. This of course requires that the source file is first loaded into Navisworks and then saved as a nwd file. Some formats are not listed in this table such as dgn, dwg, or ifc as examples. When a connector exists for a specific format, the best option is to use the native connector for that file format. However, for instances where a native connector does not exist for that format, using Navisworks for one of the formats listed below can be an option. The listed formats below have been tested and successfully imported into an iTwin from Navisworks.