Read IGES for JT conversion
A IGES-to-JT workflow combines the IGES reader with the JT writer. Use it when the receiving application needs JT data from an existing IGES model.
Read IGS or IGES geometry with the OCCT IGES interface. Inspect the transferred curves, surfaces and topology before conversion: an IGES model may contain disconnected surfaces or wire geometry rather than a closed solid.
Build a JT visualization model
For mesh output, tessellate the imported faces and inspect boundaries between adjacent surfaces. Curves alone do not define a surface mesh. For BRep output, determine whether sewing or shape healing is needed before writing the translated geometry.
Use the OCAF-to-JT converter for supported hierarchy, names, colors and mesh representations. Configure tessellation and any required levels of detail around the viewing task. This output route creates a visualization representation; it does not promise Parasolid BRep export inside JT.
Validate the JT result
Check units, surface coverage, open boundaries and tolerances. A successful translation does not establish watertightness or restore product structure that the source IGES file did not contain.
Select a JT version accepted by the recipient and check part positions, geometry coverage and appearance there. Compare both the full assembly and selected parts. If later processing requires precise CAD surfaces, retain the source BRep alongside the visualization derivative.
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.