CATIA File Import Limitations

The following page lists the limitations related to the import of CATIA files into Speos.

CATIA Object Names Conservation

After importing a CATIA file into Speos, the object names (default or custom) from CATIA are kept. However, the geometrical set names from CATIA are lost, which means geometries are renamed.

Non-Supported CATIA Disjoint bodies

SpaceClaim does not support disjoint bodies.

If you switch from Lightweight to Heavyweight a geometry imported from CATIA and originally created in CATIA with disjoint bodies, SpaceClaim creates as many geometries as existing CATIA disjoint bodies. As a consequence, Speos links are only kept on one geometry, and other created geometries from each disjoint body do not have Speos links.

Tip: Instead of importing a CATIA geometry made of disjoint bodies, split the disjoint bodies in different geometries in CATIA, and import each geometry individually.

Non-Supported CATIA non-manifold geometries

Non-manifold geometries created in CATIA are not compatible in Speos after importing the CATIA Project.

Import of Hidden Geometries from CATIA

Importing a *.CATPart file containing hidden geometries in Speos does not have any impact on the import time.

Publication Names VS Geometric Sets in *.CATPart

Known Issue: Speos does not support *.CATpart file import containing "Publication names".

Workaround: Make sure to use "Geometric sets" instead of "Publication names" in your *.CATpart file for the import to interpret it as "Named selections".

Workaround in script: To avoid importing "Publication names", you to explicitely write it in the script. Example:

importOptions = ImportOptions.Create()
importOptions.Catia.MapGeometricSetsToGroups = True
importOptions.Catia.PublicationsOnlyToGroups = False
DocumentOpen.Execute("C:\\Users\\username\\CATIA_Project\\filename.CATPart", importOptions, None)