Is my IFC file uploaded anywhere?

No. Files are parsed entirely in your browser via web-ifc, a WebAssembly build of the open-source IFC parser. Nothing leaves your machine. The app works completely offline once loaded.

Can I use it with confidential models under NDA?

Yes. Because all processing happens in your browser and no data is ever transmitted to any server, you can safely use it with confidential project models under NDA. There is no service agreement to review with your client — no data changes hands.

Can I share the validation results with my team or client?

Yes. After running validation, click Share Report to copy a link that encodes the full Health Score and issue list directly in the URL — no file upload, no server, no account required. You can also export results as JSON, CSV, or a Validation Certificate. The IFC file itself never leaves your browser.

Yes, fully. IFC Viewer Online works on any modern browser — Chrome, Edge, Firefox, and Safari on both Mac and Windows. No plugin, no installation, no operating system restriction.

What happens if my IFC file is very large?

The app handles files up to 2 GB. Performance depends on your device — files under 200 MB load well on most modern hardware. Once parsed, geometry is cached in OPFS so every subsequent load of the same file is instant, even offline.

How does the validation work?

The validator runs 44 built-in rules in a background Web Worker so the UI stays responsive. Rules cover GUID duplicates, spatial hierarchy, orphan elements, naming conventions, missing type assignments, ISO 19650 property sets, LOD completeness, clash detection, proxy overuse, coordinate offset, storey-elevation integrity, unit consistency, and more. You can also run a buildingSMART IDS specification against the model. Every model receives a Health Score from 0 to 100. Results stream in as each rule completes.

Can I fix errors and re-export a corrected IFC?

Yes. All edits (GUID fixes, renames, property value changes) are held as non-destructive diffs with full undo/redo. Clicking Export IFC applies all diffs to the original binary in a Web Worker and downloads the corrected file — no server involved.

What IFC versions are supported?

IFC2x3, IFC4, IFC4x1, and IFC4x3. The viewer uses the open-source web-ifc parser — the same engine used by most modern BIM tools and @thatopen/components. Outdated schemas are automatically flagged by the validator.

What measurement tools are available?

You can measure lengths between any two points, areas of surfaces, volumes of enclosed elements, and individual edge lengths — all directly in the 3D viewport. Measurements persist as labelled annotations and can be exported alongside your model.

Can I load multiple IFC files at once?

Yes. Load as many IFC files as your device memory allows. Each model has independent visibility, transforms, validation, quantity takeoff, and export. Use the Scene panel to manage, reorder, or remove models at any time.

Does it work offline?

Yes, once the page is loaded. The WebAssembly parser and WebGL renderer run entirely in the browser. Parsed geometry is cached in OPFS so repeat loads are instant even without a network connection.

What are the file size limits?

There is no enforced limit — performance depends on your device. Files up to ~200 MB typically load well on modern hardware. The OPFS geometry cache means you only pay the parse cost once per file.

Is it free? Can I use it for commercial projects?

Yes, completely free. The source code is MIT-licensed. You can use the live app or fork the repository for your own projects, including commercial ones.

¿La demo está conectada a un sensor físico?

No. Es una fuente determinista y claramente etiquetada como simulada. Valida reproducción, parser binario, actualización GPU y fallos sin afirmar una conexión real.

¿Por qué se conservan solo dos o tres frames?

En una vista viva un frame reciente vale más que uno antiguo. Un buffer acotado evita que una cola transforme la latencia de red en un retraso creciente.

¿El MCAP de la demo es ROS PointCloud2?

No. MCAP admite serializaciones arbitrarias. La demo usa un contrato binario propio; ROS PointCloud2 y Foxglove PointCloud necesitan adaptadores explícitos.

Volver al blog BIM e IFC

Gemelos digitales · 2026-08-21 · 12 min

LiDAR en tiempo real + IFC: demo web con replay MCAP

Abre la interfaz real de replay y entiende los frames binarios, buffers acotados y telemetría de un flujo IFC + LiDAR claramente marcado como simulado.

LiDAR en tiempo real + IFC: demo web con replay MCAP — IFC Viewer Online

Un vídeo de una nube y un stream de puntos no son equivalentes. El stream conserva XYZ, atributos, pose y tiempo para inspección y comparación con IFC, pero exige controlar memoria, retraso, corrupción y reordenamiento.

Pipeline LiDAR web en cinco etapas desde el sensor y filtrado edge hasta transporte binario, buffer de dos o tres frames y superposición con IFC — El edge normaliza y filtra; el navegador valida y conserva únicamente frames acotados.

Prueba el replay temporal IFC + LiDAR

Pabellón de operaciones — LiDAR temporal simulado

Escaneo simulado de 16 segundos a 12 FPS alineado con un IFC4. Demuestra el pipeline; no representa un sensor físico.

Interfaz real de IFC Viewer Online mostrando el replay LiDAR temporal simulado y alineado con el IFC del pabellón — LiDAR simulado en reproducción — arrastra para orbitar

IFC Viewer Online mostrando un escaneo LiDAR temporal simulado sobre el IFC del pabellón con telemetría de replay y alineación — Captura real del producto: la fuente temporal es simulada y determinista; parser, buffer, actualización GPU y alineación IFC funcionan en el visor real.

Contrato mínimo del frame

Campo	Función	Problema detectado
sequence	Identidad monotónica	Pérdida, duplicado o reorder
timestampNs	Referencia temporal común	Desfase con vídeo o pose
origin + bounds	Precisión local y culling	Jitter o reserva absurda
pointCount + stride	Presupuesto del payload	Paquete truncado o malicioso
flags	Semántica explícita	RGB, intensidad o clase inventados
CRC32	Integridad	Corrupción

Backpressure: gana el frame válido más nuevo

Si llegan frames cada 80 ms y decodificar tarda 120 ms, una cola normal crece indefinidamente. El visor termina mostrando el pasado aunque la conexión siga activa. El enfoque vivo conserva dos o tres slots reutilizables, descarta trabajo obsoleto y muestra edad, pérdidas, inválidos y reconexiones.

MCAP para grabar antes de conectar hardware

MCAP es un contenedor modular para mensajes pub/sub con timestamp y serialización arbitraria. Sus chunks e índices permiten buscar por tiempo y topic; consulta la especificación oficial de MCAP.

Compatibilidad de contenedor no significa compatibilidad de mensaje. ROS sensor_msgs/PointCloud2 y Foxglove PointCloud requieren adaptadores definidos.

Para contexto estático vuelve al flujo Scan-to-BIM con IFC y nube. Para recursos comprimidos en píxeles, consulta IFC + vídeo sobre terreno 3D.

LiDAR en tiempo real + IFC: demo web con replay MCAP