Read glTF / GLB for JT output
A glTF / GLB-to-JT workflow connects the glTF / GLB reader to the JT writer. Select the model items and output representation needed by the receiving application.
Read the glTF or GLB asset with the OCCT glTF interface. Resolve the geometry and companion resources used by the source scene, then inspect nodes, placements and the appearance information available through the reader.
Build a JT visualization model
Transfer the scene meshes through the application document, preserving the selected placements. For a CAD container, write a supported mesh representation rather than claiming recovery of analytic surfaces. Treat unsupported scene properties as separate data to retain or author explicitly.
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.
Check the JT result
Check scene scale, axis conventions and repeated objects. Materials, textures and scene behavior may not have an equivalent in the target; compare the required appearance and structure in the receiving application.
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.
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.