Tool

3D web viewer specialised for BIM models

A 3D WebGL viewer for navigating 3D data (Collada and BIM models). The viewer has been developed as a WASM (Web Assembly) solution, which makes it easy to embed

Main features and benefits

Among the web applications powered by the ICE (Inception Core Engine) technologies, there is a 3D WebGL viewer for navigating 3D data processed by other ICE technologies, that makes it possible to visualise 3D data aggregated with heterogeneous sources.

In this way semantic data can be visually accessed and retrieved by queries allowing to use the information contained at different scales for a more aware understanding of how an asset is connected. In fact, in the viewer you can navigate the model in three dimensions and view it in three modes: IFC, texture and hybrid.


Figure: Texture, Hybrid and IFC mode views.

The IFC mode allows you to select geometric elements, filter them by levels or classifications and query their metadata, while the texture mode (that exploit COLLADA textured models of the same asset) does not present selectable elements but offers a visualisation capable of offering an intuitive material understanding.

The hybrid mode superimposes the previous ones by means of an editable transparency layer and allows you to select IFC geometric elements enriched this time by their real appearance. It is also possible, for each element, to access its metadata: it is possible to read the unique Global-ID, the name, the IFCType, notes and comments. Through a graphical schema it is also possible to navigate between categories, parameters and values (which may contain links to internal references on the same platform or external on the web) attributed during the modelling phase as well as attachments in the form of various file types (e.g., documents, images, videos, 3D models of details).

Figure: Layer and IFC classes filtering mode.

This viewer is developed as a WASM (Web Assembly) solution, propaedeutic for embedding. Furthermore, the viewer doesn’t need that the 3D content is collocated in the same place as the viewer (except for the CORS policies) allowing it to possibly run directly on a web server.