lattice-vw-itwin

Mapping IFC elements to iTwin BIS classes from Vectorworks requires enriching ingested IFC data with authoritative BIS class and subclass assignments. This process uses a C++ plugin and Python bridge to drive IPC flows and write mappings back into a Pixeltable update workflow.

Vectorworks IFC exports show missing BIS classification data when elements lack assigned bis_class or bis_subclass values. You can detect these null entries by auditing ingested ifc_elements and running an enrichment pipeline to apply authoritative BIS mappings.

The best way to audit null BIS class coverage is to detect elements with null bis_class or bis_subclass fields within your ingested ifc_elements dataset. This focuses enrichment efforts strictly on elements requiring authoritative BIS schema mappings.

You cannot use Revit, MicroStation, DGN, or Bentley-cloud workflows to author IFC data for this BIS ingestion process. The pipeline enforces safety guardrails that forbid these backend packages to keep ingestion and symbol naming consistent.

You need to validate plant symbol naming before enriching IFC data to ensure ingestion consistency. The pipeline enforces required Genus_species_cultivar naming rules and forbidden-string constraints during the VW-to-BIS enrichment workflow.

To start a Vectorworks to iTwin BIS enrichment cycle safely, begin with vw.ping health checks. Then map data via BisCore.ecschema.xml with a safe fallback, validate naming rules, and update Pixeltable using EPSG-normalized placement data.