Feature request: expose plate stress/strain field (result mesh) via the API for 3D visualization

[linkwisesrl-coder]

Summary

Would it be possible to expose the per-node (or per-element) stress and plastic
strain field of plates through the API, i.e. the result mesh that IDEA StatiCa
already uses internally to draw the stress contour plots in the UI and in the report?

Context / what is already available

Using the Connection REST API (Python client ideastatica_connection_api), I can
already retrieve:

• Per-component check results via get_raw_json_results (equivalent to
  GetCheckResultsJSON): plates[id].maxStress, plates[id].maxStrain,
  boltsAnchor[...] forces, welds, etc. — see discussion Expansion of result access through IDEA Statica API #243.
• The 3D geometry via presentation.get_data_scene3_d → DrawData { vertices, normals, groups }, where each group is a set of triangles colored by part
  (steel / concrete / bolts), not by result.

What is missing

There is no way to obtain the stress/strain field mapped to the mesh:

• plates[id].form and plates[id].items are empty / null.
• platesDeformation exposes only maxDeformation (+ node ids), no stress array.
• get_data_scene3_d only carries geometry + part colors, no nodal result values.

So only the single maximum value per plate is available, not the field needed to
render a stress contour.

Proposed solution (any of these would help)

1. A result-colored scene, e.g. an option/parameter on get_data_scene3_d to
   return the mesh colored by equivalent stress σ_Ed / plastic strain ε_Pl
   (the same data the report renders).
2. Or a nodal/element results array per plate in the results JSON, aligned with a
   mesh (node coordinates + connectivity + value per node), so it can be rendered
   externally (e.g. pyvista).

Use case

Programmatic / automated stress visualization and custom 3D rendering (parametric
studies, batch reporting, integration into our own tools) without opening the IDEA
StatiCa UI.

Environment

• IDEA StatiCa 25.1, Connection REST API, Python client ideastatica_connection_api 25.1.x.
• Related: discussion Expansion of result access through IDEA Statica API #243 (detailed bolt/anchor forces).

Thanks!

[TomKohoutek]

Hello @linkwisesrl-coder and thank you for your request.

I am looking into it and we have this functionality only not exposed to the API.

And for such connection:

I am able to return the data to visualize it with python to this:

I would like to verify with you if this is the desired functionality. I tried to attach here also the .ideaCon + the meshResponse.json file but it is not supported. How can I reach you out so we can finalize this ?

The expected version where we could deliver this could be patch 26.0.3 if everything goes well.

Thanks for an answer
Regards
Tomas

[linkwisesrl-coder]

Hello Tomas,

Thank you very much for your feedback and for looking into this.

Yes, this is exactly the functionality I am looking for. Being able to access the internal result mesh used by IDEA StatiCa to generate the stress/plastic strain contour plots would be very useful.

For my use case, either of the following would work well:

a result-colored 3D scene, similar to what IDEA StatiCa already renders internally;
or, even better, a mesh response containing node coordinates, element/connectivity data, and the associated values per node or per element, for example equivalent stress σ_Ed and plastic strain ε_Pl.

The Python visualization you showed seems to match the expected direction. That would allow external rendering, automated reporting, and batch post-processing without needing to open the UI.

I also think this would be a great feature not only for my workflow, but for many users who want to integrate IDEA StatiCa results into custom tools or parametric studies.

Thanks again for your help.
Best regards,

[TomKohoutek]

Hello @linkwisesrl-coder

for estimated time of this being delivered will probably be a little later than just next patch.
There are some further discussions how to handle it properly. I will keep you updated in this discussion.

Sorry for the misleading information about sooner release. The work on this feature is still in active development, not declined.

Regards
Tom