I am experiencing an issue with the Autodesk Platform Services (APS) Model Derivative API where the bounding boxes of elements differ between SVF and STL formats when converting from a Parasolid file. However, if I first convert the Parasolid file to SAT and then use the APS Model Derivative API to convert it to SVF and STL, the bounding boxes match.

Problem Description: Original Conversion: Directly converting a Parasolid file to SVF and STL using the Model Derivative API results in different bounding boxes for the same elements.

Workaround: Converting the Parasolid file to SAT first and then to SVF and STL yields consistent bounding boxes.

Use Case: APS Viewer: Users select elements in the APS Viewer, which uses SVF. We need to map these selections to the corresponding elements in STL for further processing.

What could be causing this discrepancy in bounding boxes between direct Parasolid conversions and the SAT intermediate step? Are there any known issues or workarounds for ensuring consistent bounding boxes across both formats?

Desired Solution: A method to ensure consistent bounding boxes for elements across both SVF and STL formats.