The Verifi3D Viewer makes use of Three.js as its backbone engine on which we make use of the IFC-Engine to parse IFC models through Verifi3D and then have them visualized within the viewer. To read Revit files we make use of the Autodesk Forge Design Automation API connection where all Revit models are pushed through the API Connection to then have them viewable within the Verifi3D Viewer.
If a model is not uploaded but is instead being grabbed from one of the A360 / BIM360 hubs we make use of the Autodesk BIM360 Document Management API to retrieve the file and then based upon the file format we either push it through the IFC-Engine (if it’s an IFC File) or via the Autodesk Forge Design Automation API (if it’s a Revit file). Hence data that is sent to the viewer is only converted once during the process such that it can be loaded within the Viewer and such that it can be visualized through the web browser via Three.js throughput.
Comments
0 comments
Article is closed for comments.