Read JT for XCAF output
A JT-to-XCAF workflow connects the JT reader to the XCAF writer. Select the model items and output representation needed by the receiving application.
JT can contain stored visualization meshes, embedded Parasolid BRep, or both. Select the representation needed for the destination before reading the assembly. The Parasolid interface imports precise geometry only when the JT file contains Parasolid BRep data.
Build and store an XCAF document
For a mesh route, select a suitable stored level of detail or tessellate the imported Parasolid BRep with the required deflection. For a precise-geometry route, use the embedded BRep; a mesh-only JT file cannot supply the original CAD surfaces.
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 part placements and repeated instances as well as names, colors and transparency. A stored coarse level of detail cannot regain surface detail merely by changing file format.
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.