← CAD and mesh conversion guides

OCCT conversion workflows

OCCT BRep to XCAF

Convert OCCT BRep to XCAF for OCCT applications. Store imported geometry with supported names, colors and document structure.

Build this conversion into your application with OCCT readers, writers and the commercial components identified below.

Ask about this workflow
Input interface
OCCT BRep reader
Processing route
CAD and mesh exchange
Output interface
OCCT XCAF document writer

Read OCCT BRep for XCAF output

A OCCT BRep-to-XCAF workflow connects the OCCT BRep reader to the XCAF writer. Select the model items and output representation needed by the receiving application.

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.

Build and store an XCAF document

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.

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

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 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.

Conversion integration

Build a OCCT BRep to XCAF workflow

Share the source and receiving applications, representative files, required attributes and throughput. We can scope SDK evaluation or an integrated conversion service.