Read glTF / GLB for XCAF output
Transfer glTF / GLB meshes into a XCAF workflow with the glTF / GLB reader and XCAF writer. This route carries polygonal geometry in the receiving document; it does not recreate the original CAD surfaces or feature history.
Read the glTF or GLB asset with the OCCT glTF interface. Resolve the geometry and companion resources used by the source scene, then inspect nodes, placements and the appearance information available through the reader.
Build and store an XCAF document
Transfer the scene meshes through the application document, preserving the selected placements. For a CAD container, write a supported mesh representation rather than claiming recovery of analytic surfaces. Treat unsupported scene properties as separate data to retain or author explicitly.
Place the imported geometry in an XCAF document and map the supported names, colors and structure to its labels. Use the native OCCT document storage appropriate to the selected XBF or XML delivery. Mesh data can remain mesh in the document; creating labels does not generate analytic CAD surfaces.
Check the XCAF result
Check scene scale, axis conventions and repeated objects. Materials, textures and scene behavior may not have an equivalent in the target; compare the required appearance and structure in the receiving application.
Reopen the document in the intended OCCT application and verify geometry, occurrence placements and mapped attributes. Keep application-specific additions distinct from source properties. XCAF storage is useful for continuing an OCCT workflow, but the recipient must support the chosen document format.
Discuss this conversion with the producing and receiving applications, representative files and required geometry and attributes. Compare the reader/writer catalog when a different representation is needed.