How to transfer attributes from 3D Deswik polygons to a Block Model in Leapfrog Edge

ValterOliveira
ValterOliveira Posts: 16 Diamond Rank Badge
in Leapfrog

Hello everyone,

I'm currently working on a workflow between Deswik and Leapfrog Edge, and I’d really appreciate some guidance or shared experience from anyone who has already integrated polygon attributes into a Leapfrog block model.

Context

I’m dealing with about 5,000 3D solids (polygons) exported from Deswik, each representing a blasting or release polygon.

My first test was done using the .OBJ format, which correctly exports the 3D geometry, but unfortunately does not preserve any polygon attributes (such as IDs, names, or grades).
When imported into Leapfrog under the Meshes folder, the solids appear as valid 3D volumes — but with no associated data.

Objective

I’m trying to achieve two specific steps in this workflow:

  1. Export from Deswik
    Find a file format (and export configuration) that preserves both the 3D geometry and the polygon attributes (for example, Poly_ID, Grade_real, or Mass_real) when exporting blasting or release polygons from Deswik.
    Formats like DXF or other solid-based formats may support embedded attributes — I’d like to confirm the most reliable approach.
  2. Import into Leapfrog and transfer attributes
    Once the exported solids contain attributes, I need to import them into Leapfrog Geo/Edge and then transfer those attributes to the block model, so that each block inherits the corresponding categorical or numeric values from the polygon that contains it.

Questions

  • Which export format from Deswik best preserves both geometry and attributes when transferring solids into Leapfrog?
  • How can I import those solids with attributes and use them to populate or evaluate attributes in a block model?

Any suggestions or experiences from other users who have done similar integrations (Deswik → Leapfrog → Block Model) would be very welcome!

Thanks in advance,
Valter Oliveira
Vale Base Metals – Brazil

Tagged:

Comments

  • KathrynGall
    KathrynGall Posts: 42 mod

    Seequent was excited earlier this month to announce our new technology partnership with Deswik. The aim of the partnership is to build smoother transfer of data between our products. TO demonstrate the partnership we made a video to showcase integration via Evo using our open python data converter for Deswik .duf. However, while it uses Python, the video aims to show the potential of the partnership and build more seamless integration in the future. You can watch the video here:

    https://www.seequent.com/introducing-the-new-integration-between-seequent-evo-and-deswik/

    The workflow you have described above would be enabled via Evo. I would recommended speaking to the local sales team in Brazil to learn more about Evo. Evo will be the data platform that is used to power cloud compute capabilities and integration across a number of different workflows and products (both Seequent and non Seequent).

    For the moment, in recent versions of Leapfrog, we have been adding better to support for attribution of data in Leapfrog. This was first added for polylines and then meshes in 2025.1. However, there are some limitations. The For polylines, you can convert the polyline to a mesh, using the extruded mesh functionality. This will retain the attribution within leapfrog from the polyline. This is a great workflow for blast domains. https://help.seequent.com/Geo/2025.2/en-GB/Content/meshes/extruded-mesh.htm?Highlight=extruded%20mesh

    For meshes, you need to assign the attributes after input, using the attribution table - https://help.seequent.com/Geo/2025.2/en-GB/Content/meshes/meshes.htm?Highlight=attributed%20mesh#mesh-attributes

    The best way to evaluate meshes onto a block model is via the Grouped Mesh. Fro non attributed meshes, you can add each mesh into a Grouped Mesh, and then assign the attribute manually to each mesh. When this mesh is evaluated onto the block model, it will apply the attribute. See more details here: https://help.seequent.com/Geo/2025.2/en-GB/Content/combined-models/grouped-mesh.htm?Highlight=group%20mesh

  • ValterOliveira
    ValterOliveira Posts: 16 Diamond Rank Badge

    Hi Kathryn,

    Thank you for your detailed and insightful reply — it’s great to see how Seequent and Deswik are strengthening integration through Evo.

    It’s very encouraging to know that Evo will enable this type of workflow natively in the near future. We’ve already started exploring the new mesh attribution features in Leapfrog 2025.1, especially for extruded and grouped meshes, and they’ve helped a lot in maintaining consistent attributes across different domains.

    We’ll be glad to get in touch with the Seequent team in Brazil to learn more about Evo and upcoming integration capabilities with Deswik.

    Thank you again for your feedback and for sharing the resources!

    Best regards,
    Valter Oliveira
    Geologist — Vale Base Metals, Brazil

Categories