Choose mesh or BRep exchange from JT
JT-to-STEP conversion can start from mesh data, precise geometry or a model containing both. STEP supports mesh import and export, so a JT visualization mesh can be transferred into a mesh-capable STEP workflow without pretending to recover analytic surfaces.
For precise geometry, the JT component imports embedded Parasolid BRep through the Parasolid interface. The source JT must contain Parasolid BRep data; the imported OCCT shapes can then be written to STEP. A mesh-only JT file has no embedded BRep to read. Mesh transfer and precise-geometry transfer should have separate acceptance criteria.
Read the required JT representation
Use the JT-to-OCAF converter for supported hierarchy, visual attributes and geometry. Select the mesh level of detail when the conversion depends on tessellation. For a BRep route, inspect the precise imported shapes before configuring STEP output.
The published reader description lists JT 8.1, 9.5, 10.0 and 10.5. Confirm the selected delivery, representation and optional components for the actual files being processed.
Validate the STEP consumer
Configure a STEP representation the receiving application accepts. Check geometry coverage, mesh detail or BRep quality, part placements, names and appearance required by the workflow. PMI handling needs its own reader-to-writer check.
A STEP file containing mesh data does not become a parametric solid simply because it has a CAD extension. Conversely, a BRep-capable conversion should not discard precise source geometry unnecessarily. For a triangle-only target, compare JT to STL; for the reverse visualization route, see STEP to JT.