Read OCCT BRep for glTF / GLB conversion
A OCCT BRep-to-glTF / GLB workflow combines the OCCT BRep reader with the glTF / GLB writer. Use it when the receiving application needs glTF / GLB data from an existing OCCT BRep model.
Read native OCCT BRep shapes from BREP or SHAPE files. This provides geometry and topology for modeling or tessellation. A standalone shape file is not an XDE document and should not be assumed to contain assembly names, colors or materials.
Prepare a scene for glTF or GLB delivery
Use the imported shapes directly for a precise CAD writer, or generate surface triangulation for a mesh writer. If the input contains open shells, faces or wires, select the geometry appropriate to the target instead of assuming every shape is a solid.
Map supported model items into glTF scene nodes and configure the mesh, placements and appearance for browser or application delivery. Decide whether the receiving workflow expects a GLB package or glTF with companion resources. Keep names useful for selection and inspection.
Validate the glTF / GLB result
If application-owned labels, placements or appearance must accompany the shape, supply them explicitly in the document passed to the writer. Keep this enrichment distinct from information read from the BRep file.
Reopen the asset in the target viewer and compare orientation, bounds, assembly placement and visible surface quality. Check material mapping and resource paths. Measure loading cost together with geometric detail so that reducing mesh size does not silently remove required features.
For a production pipeline, keep a representative source file and its expected geometry and attributes with the conversion settings. Discuss conversion integration with the source and destination applications, or compare the supported format interfaces.