Home > Supported File Formats > IFC to X3D

How to convert IFC (Industry Foundation Classes) to X3D (VRML2, VRML97)?

PolyTrans|CAD+DCC performs mathematically precise CAD, DCC/Animation, GIS and BIM 3D file conversions into all key downstream 3D packages and file formats. Okino software is used and trusted throughout the world by many tens of thousands of 3D professionals in mission & production critical environments, backed by respectable personal support directly from our core development team.

IFC

The Industry Foundation Classes (IFC) is a CAD data exchange object-based file format with a data model developed by buildingSMART to facilitate interoperability in the architecture, engineering and construction (AEC) industry, and is a commonly used collaboration format in Building information modeling (BIM) based projects.

IFC files can be written out by such industry standard programs as: ArchiCAD, Allplan, Autodesk's AutoCAD and Revit, Microstation, Tekla Structures, SmartPlant3D and Vectorworks.

Please note: you would always want to use the DWF-3D file format and the Okino DWF-3D file importer to import 3D model data from Autodesk's AutoCAD, Navisworks and Revit, as well as AVEVA's PDMS software.

It is may be safe to say that few 3D graphics users properly understand IFC or why/how it should be used, when it should be used or how it is to be used. In simplistic terms, IFC is NOT a universal data interchange file format like COLLADA, FBX, 3ds, OBJ, DXF, DWG, etc. Rather, IFC is more of an "abstraction" for an architectural model so that BIM companies can exchange IFC files for design iterations without any loss in overall geometric quality. Hence, the basis of IFC is to make an abstract building with stories, floors, doors, columns, windows, etc. From these hang "abstractions" such as 2D plan views and 3D renderable geometric data.

While IFC can be considered a standardized file format by BuildingSmart, not all 3D programs or 3D viewers will "interpret" an IFC file in the same manner due to the abstract nature of the file format and also by the generally loose manner in which a model can be defined and with different contexts and representations.

X3D

X3D is the XML-based replacement to the venerable VRML2/VRML97 (Virtual Reality Modeling Language) file format of the 1985-era. X3D extends VRML2 with support for CAD, geospatial, humanoid animation and NURBS. It also provides for multi-stage and multi-texture rendering. Each new iteration of the file format brings more modern functionality, headed up by the Web3D Consortium.

VRML2 (and its brotheren X3D) continue to be two of the very best of non-MCAD file formats. Many people (wrongly) believe that FBX is the primary "translation file format" but VRML2 pre-dated it by at least 10+ years and has equally good or better functionality (and in an open, non-proprietary specification).

VRML1 and VRML2 are 3D file formats with a long and complex history. They were originally developed in the mid 1990s to define 'interactive 3D worlds' on the then-new World Wide WEB. However, statistically speaking, VRML2 became more well known as a high quality "data translaton and storage" file format, partly due to Okino pushing it as such a standard in the industry. It was implemented by a good number of 3D software packages and hence became a "reliable back door" to convert 3D assets out of those packages before FBX, DWF, COLLADA, U3D and other similar file formats came along in the mid to late 2000s, or glTF in the late 2010's. So many new 3D file formats were introduced between 2005 and 2007 that many quickly died away or just became ghosts of the past.

Its brothern are also known as VRML2, Classic VRML, VRML97, VRML1 and Inventor2.

IFC import converter's overview

X3D export converter's overview