Read STL for XCAF output
Transfer STL meshes into a XCAF workflow with the STL 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 STL triangulation through the OCCT interface. Treat it as surface geometry: the source does not provide a full assembly tree, CAD names, materials or precise BRep surfaces.
Build and store an XCAF document
Transfer the existing triangles into the target mesh representation. If the destination needs names, colors or a scene hierarchy, author these in the application rather than claiming they were recovered from the STL.
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
Agree on unit scale and check bounds, face orientation and connected regions. Repackaging a coarse or incomplete STL does not improve its geometric accuracy or establish manufacturing suitability.
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.