Best Of

Hello Leapfrog Community 🎉🐸

I’m excited to share with you today the link to the latest version of Leapfrog Geo, Leapfrog Works, and Leapfrog Energy. The latest release improves efficiency and gives you greater control across data analysis and modelling workflows.

In this version, you’ll find:

🔹Refined geostatistical analysis: Save graphs and tables, and filter swath plots by domain or set coordinate limits

🔹Contextual core imagery: Stream Imago core photos directly in the drillhole correlation tab, with automatic unit conversion

🔹Revamped structural toolkit: Fine-tune clustering settings in downstream models, and enjoy a new interface layout and display filtering in stereonets

🔹Better site presentation with strip view: Add strip views to long sections with enhanced section line controls and chainage alignment

🔹 Enhanced borehole planning experience: Plan, visualize, and communicate more easily using end-of-hole labels and depth markers, as well as faster model evaluations and export filters

I’ll be keen to hear what you think of the new version! Click here to check it out.

I believe that Stephanie has reached out on this over at the support section.

Long story short, this is the currently designed behaviour for Estimating Structures from Points, I don't have the details, but this method will only select a subset of the data.

There are on the other hand different ways of dealing with a connected database. Such as adding in Query Filters to handle new data being added. How you set that up depends on your project.

But if you don't want new data to automatically get added with any new reloads you can use a Query Filter as soft blocker, possibly set on selected and validated holes using a Categorical Selection.

Thanks a lot for the detailed workaround — it’s a smart approach and definitely helps in many situations.

However, there are a few caveats I’ve noticed when applying this method in projects that already have an existing topography:

• It’s not possible to create a new topography directly from a mesh when one is already defined in the project.
• In such cases, the alternative is to use the “Set Elevation” option to project the points onto the surface of the generated mesh.

The problem, however, is that when the points are moved only in the Z direction, a distortion in real spacing occurs — since the XY distances remain fixed while elevation changes.

For planar surfaces, this can be corrected using a trigonometric adjustment based on the dip of the plane:
by slightly modifying the XY spacing when creating the grid, you can ensure that, after projection, the final spacing along the inclined surface matches the desired regular mesh.

But for irregular meshes, where dip and azimuth vary continuously, this correction is not feasible — there’s no single trigonometric relationship that can preserve regular spacing everywhere.

That’s why I believe the most practical solution would be to have an option to generate a regularly spaced point grid directly on an irregular surface, preserving the true spacing along the mesh itself.

Since Leapfrog geo 2024 (definitely in LF Geo 2025) you can import and convert lineations recorded in alpha-beta-gamma format. Right-click on a Drillholes set name, then Import from file or Import from ODBC and there is an option for 'lineations'. This takes you to the usual import dialog where you select holeid, depth, alpha, beta and gamma columns from your data table.

Hello @NatsagdorjBatbayar. Yes, you can probably convert your gamma to trend and plunge by using a calculation. It cannot be done automatically.

If you know the orientation of the bottom-of-core-line (probably the trend of the drillhole), and you know beta, then you should be able to calculate gamma. You could do this in Leapfrog or in Microsoft Excel. The calculation would look something like: [bocl trend + beta + gamma]. If the result is greater than 360, subtract 360.

See part 1 of the online Leapfrog Structural Modelling Tools course in Seequent Learning, for more information.