Read JT for OCCT BRep conversion
A JT-to-OCCT BRep workflow combines the JT reader with the OCCT BRep writer. Use it when the receiving application needs OCCT BRep data from an existing JT model.
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.
Store imported geometry as native OCCT shapes
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.
Write the imported precise shapes using native OCCT BRep storage. This route is useful for retaining translated geometry for subsequent OCCT modeling and analysis. It requires BRep source geometry and does not recover analytic surfaces from a mesh-only representation.
Validate the OCCT BRep 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.
Read the BRep file back with the intended OCCT delivery and compare shape types, tolerances and geometry coverage. A standalone BRep file does not carry the complete XDE assembly and attribute document; choose XCAF storage when that document-level information must be preserved.
For a production pipeline, keep a representative source file and its expected geometry and attributes with the conversion settings. Discuss conversion integration with the source and destination applications, or compare the supported format interfaces.