Read AMF for XCAF output
Transfer AMF meshes into a XCAF workflow with the AMF 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 AMF geometry through the Assimp integration and inspect the mesh, object structure and appearance returned by the reader. Select the parts required downstream.
Build and store an XCAF document
The Assimp integration provides mesh geometry, colors, materials and scene structure for its supported inputs. Pass that data to a separate OCCT or commercial writer. For STEP, STEP XML or DXF output, use the mesh-capable representation; this does not reconstruct BRep surfaces from polygons.
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 each imported object and its placement. Manufacturing metadata and process settings are separate from the mesh and require explicit retention checks.
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.