Parasolid Import Component

On this page

Parasolid import for Open CASCADE applications

The Parasolid Import SDK reads text (.x_t) and binary (.x_b) Parasolid files into Open CASCADE Technology (OCCT) geometry and topology. The XDE layer provides access to imported names and colors alongside the shapes.

Use it when your application needs to work with a Parasolid export from another CAD system. Reading a Parasolid export from SOLIDWORKS, NX or Solid Edge is different from reading those systems’ native part and assembly files.

BRep conversion, XDE attributes and configurable healing

The module has two complementary layers. The BRep conversion component translates geometrical and topological entities into OCCT shapes and can be used independently. The XDE component builds on that conversion to transfer names and colors and expose them through the XDE API.

Shape Healing is part of the import workflow. Resource files let an application configure the healing operations; default healing is applied when no resource file is provided. This gives a conversion pipeline a repeatable repair configuration instead of requiring manual correction after every import.

Keeping geometry conversion and attribute handling separate is useful for different clients: a geometric calculation may need only shapes, while a viewer or conversion service also needs the names, colors and their relationships to imported entities.

Convert Parasolid, X_T or X_B to STEP

A Parasolid-to-STEP workflow combines this commercial reader with OCCT’s STEP writer:

1. Read the X_T or X_B file into OCCT shapes, or an XDE document when attributes matter.
2. Check the imported geometry, model units and required attributes. Configure shape healing for the source data and the application’s tolerance requirements.
3. Write the result with the OCCT STEP interface.
4. Reopen the STEP output and check the geometry and attributes required by the receiving application.

The same integration can start from either text or binary Parasolid input. Agree on the source schema and the required STEP output before evaluating a production conversion workflow.

Other conversion workflows

Target	Processing after Parasolid import	What to check
OCCT BREP	Store the imported shapes	Native geometry and topology; use a document format when additional attributes are needed
STEP	Use the OCCT STEP writer	Units, geometry, names and colors required by the receiving system
STL	Tessellate the shapes and write a mesh	Surface deviation and triangle count; STL does not retain the CAD assembly document
glTF / GLB	Prepare tessellation and use the OCCT glTF writer	Scene structure, appearance and tessellation quality
JT	Add the JT exchange SDK	Assembly and mesh requirements, output version and component licensing

See the CAD format matrix for open-source writers and commercial components. For surface mesh preparation, explore Express Mesh.

Import direction and data limits

This component imports Parasolid. It does not provide STEP-to-Parasolid or X_T/X_B export. Imported data is translated into OCCT structures; this does not recover the source application’s feature history or guarantee preservation of every source attribute.

The integration supports shape healing and separate geometry/attribute handling. Validate source schema coverage and required entities against the component delivery selected for your OCCT version.

Evaluate your Parasolid conversion

Include the source format and version, target format, OCCT version, platform, and required names/colors in your enquiry. Describe typical file size, batch throughput and tolerance requirements. A representative model and agreed output checks make it possible to assess the complete conversion path.

Discuss SDK evaluation and licensing, or request CAD conversion integration services.