What this BCFZIP auditor checks
The auditor validates bounded ZIP structure and CRCs, the root bcf.version file, topic-folder and Topic GUID agreement, readable markup, required topic fields, unique issue and comment identities, related-topic resolution, version-specific comment and viewpoint placement, viewpoint and snapshot paths, image signatures and dimensions, orphan assets, and internal header, document, and BIM snippet references.
Viewpoint and component diagnostics
Each readable .bcfv file is tied back to its markup GUID. Camera points and direction vectors must be finite, direction and up vectors must be nonzero and nonparallel, perspective field of view must fall between 0 and 180 degrees, and BCF 3.0 cameras need a positive aspect ratio. Selection, visibility exception, and coloring lists are summarized by unique 22-character IFC GUID; coloring, clipping planes, and bitmap geometry receive focused checks.
How to use the report
Start with errors, because they indicate missing package relationships, unreadable evidence, identity conflicts, or values outside the supported schema constraints. Warnings highlight case portability, orphan assets, or unfamiliar versions. The issue cards help coordinators see whether a problem is richly documented or missing its visual/component context; CSV and JSON preserve the same evidence for handoff or archival review.
Validation boundary
This is a focused structural auditor, not an official buildingSMART conformance validator or BIM viewer. It does not run the published XSDs, render model geometry, open IFC files, verify component existence, evaluate extensions, fetch external documents, validate every optional ordering/cardinality rule, assess issue correctness, repair packages, or guarantee import into a target application. Confirm critical deliveries with the current official schemas, buildingSMART test cases, and every receiving application.
Frequently asked questions
Does the tool display the 3D viewpoint?
No. It audits the XML camera and component evidence and the packaged snapshot without building a 3D renderer. That keeps the workflow fast and makes missing or contradictory package relationships easier to see.
Does a valid IFC GUID prove the component exists?
No. It proves only that the reference has the required 22-character lexical form. Existence requires the corresponding IFC model and model-aware validation.
Why can a package pass here but fail in another application?
This tool applies transparent high-value checks rather than complete XSD validation or vendor behavior. Element order, extension semantics, application profiles, and model-specific expectations may still affect import.
Primary references
The official buildingSMART standards server publishes BCF 2.1 and 3.0. The BCF-XML repository provides the current XML schemas, documentation, examples, and test cases; its BCF 3.0 markup and visualization schemas define the fields checked here.
Plan roof geometry · Audit a QGIS project · Browse BIM tools