Jupiter Tesselation (JT)¶
JT is an Exchange Format managed by Siemens and standardised in ISO 14306:2017. JT is used for the exchange of 3D data between different CAD systems. It is a lightweight format that is used for visualization and collaboration. The application of JT is predominant in the automotive and aerospace industry.
Extensions¶
JT contains the following container suffix supported by instant3Dhub:
.jt
Structure¶
JT files support two primary structural formats:
Monolithic files: Single self-contained JT file
Linked Structure Files: Multiple interconnected JT files
These structures typically represent hierarchical assembly structures from the top-level assembly down to individual parts. instant3Dhub fully supports both structural formats.
Level of Detail (LOD):
JT format supports multiple LODs (Levels of Detail) describing varying geometric precision through tesselated representations.
instant3Dhub automatically loads the highest available LOD.
External File References:
JT specifications allow external file referencing providing a mechanism to link to other JT files or resources.
External file references are supported by instant3Dhub.
Geometry¶
JT supports facet information (triangles) as well as B-Rep information. Both are supported and loaded by instant3Dhub.
Tesselation¶
instant3Dhub trys to use tesselation out of the referenced files if available. If geometry is described only as B-Rep instant3Dhub creates a tesselation.
B-Rep¶
XT-BRep Elements (formerly JT BRep ELement - deprecated) are used as persistent identifiers for B-Rep elements in the JT-file to maintain an addressability of faces and edges over different versions of a file.
These elements are supported by instant3Dhub and can be accessed e.g. via the TopologyAPI.
PMI & Model Views¶
JT supports Product Manufacturing Information (PMI) typically in form of tolerances. Two types of PMI are differentiated: Graphic and Semantic.
Graphic PMI are intended for human consumption only. PMI created in the source CAD system are transformed to tesselated lines, arcs, and faces, making it machine-unreadable.
Semantic PMI convey the data in a machine-readable way. It follows a pre-defined structure, consisting of a set of parameters (key-value pairs) and links to the underlying model elements.
In addition, a varying extent of styling information is given, including fonts, line styles, colors, widths.
PMIs and the relation to strcutural nodes as well as topological elements is maintained and can be used e.g. via QueryAPI.
Metadata¶
Metadata contained in JT is extracted per node as well as per resource.