thatopen-syntax-ifc-loading

Configure IfcLoader or IfcImporter to load IFC files into a ThatOpen viewer.

17|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/ThatOpen-Claude-Skill-Package --skill thatopen-syntax-ifc-loading
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thatopen-syntax-ifc-loading
Source: https://github.com/OpenAEC-Foundation/ThatOpen-Claude-Skill-Package/tree/main/skills/source/thatopen-syntax/thatopen-syntax-ifc-loading
Command: npx skills add https://github.com/OpenAEC-Foundation/ThatOpen-Claude-Skill-Package --skill thatopen-syntax-ifc-loading

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loading IFC files into a ThatOpen viewer can be error-prone without proper WASM configuration or matching compiler/runtime versions. This skill clarifies the two main approaches (IfcLoader and IfcImporter) and how to configure them to prevent common failures.

Core Features & Use Cases

  • Two integration approaches: a high-level IfcLoader and a low-level IfcImporter for server-side processing or workers.
  • WASM path configuration options: automatic resolution or manual path setup, and checks to avoid version mismatches.
  • Events and customization: hooks like onIfcImporterInitialized to tailor imported classes, and fragmentation workflow to convert IFC to Fragments for fast reload.
  • Use cases include loading models in the viewer, reading raw IFC data for debugging, and producing fragments for caching.

Quick Start

Load an IFC file by initializing FragmentsManager, setting up IfcLoader, and calling load with a Uint8Array of the IFC bytes.

Frequently Asked Questions about thatopen-syntax-ifc-loading

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load IFC files into a ThatOpen viewer using WASM?

To load IFC files, initialize the FragmentsManager, configure the IfcLoader with correct WASM paths, and pass a Uint8Array of the IFC bytes to the load function. This ensures safe WASM setup and converts the model into fragments for viewer display.

What is the difference between IfcLoader and IfcImporter in ThatOpen?

IfcLoader is a high-level approach for loading models directly into the viewer, while IfcImporter is a low-level tool for server-side processing or web workers. IfcImporter also provides hooks like onIfcImporterInitialized to tailor imported classes.

How do I fix WASM path configuration errors when loading IFC models?

WASM path configuration errors are fixed by setting manual path setup or using automatic resolution to prevent version mismatches between compiler and runtime. Proper WASM configuration ensures safe imports and reproducible fragment workflows.

Can I read raw IFC data for debugging without converting to fragments?

Yes, you can read raw IFC data for debugging by using the low-level IfcImporter. This provides optional raw web-ifc access, allowing you to inspect imported classes directly before or without executing the fragmentation workflow.

How do I convert IFC to fragments for fast reloading in web applications?

You convert IFC to fragments by configuring the IfcLoader or IfcImporter and executing the fragmentation workflow. This process transforms IFC data into fragments, producing a cached format that enables fast model reloading in ThatOpen viewers.

When should I use the IfcImporter instead of the IfcLoader?

Use the IfcImporter for server-side processing, web worker integration, or when you need raw web-ifc access for advanced debugging. Use the high-level IfcLoader for standard component-based workflows to display models directly in the viewer.