Best Of
Re: 🚀Leapfrog 2025.1 is finally here!
Hi @WandaCarter @HectorMendivil1, the login workflow for Leapfrog has been adjusted in the new version to direct users towards signing in with a Bentley account rather than a Seequent ID when certain conditions are met. All of your product entitlements will still be available when signing in with a Bentley account. More information on the new login workflow can be found in our Knowledge Base here. If you do still have any issues or questions after going through the article, feel free to email us at support@seequent.com, and we can assist further.
New MX Deposit Fundamentals Courses Are Live!
We’ve just launched two new self-paced courses to help you hit the ground running with MX Deposit:
1️⃣ Getting Started in MX Deposit
2️⃣ Project Configuration and Setup
These have already been shared with our product, technical, and global support teams - and now they’re available for you too!
Whether you're just getting started or need a quick refresher, these bite-sized lessons are a great way to build confidence and get hands-on with MX Deposit.
💬 Tried a course?
Share your key takeaways, ask questions, or troubleshoot any issues right here in the community! We're here to learn together.
Dive into the courses:
🔗 Course 1
🔗 Course 2
Let us know how you're finding it - we’d love your feedback!
Re: What is the fastest way to import topography?
I have found that points is the best way, but don't add them directly to topography.
Topography is a bit different compared to other data sets, triangulation tends to be more spatially accurate than interpolation in most cases, and RBFs do not deal with high-density, regularly spaced data well.
I nearly always triangulate from points and then provide an error margin (depending on useful project resolution). That way I can merge multiple datasets together into the best topography surface, for instance, DGPS drillhole collars, a local Lidar survey, surrounded by 30m SRTM data, often a final 'boundary' polyline. (I use QGIS to convert grids to points)
I add the mesh to the topography object last. the only time I use interpolation in topography is if there are only sparse hole collars for topography, and even then I'm more likely to build that in the mesh area first.
🚀Leapfrog 2025.1 is finally here!
The latest versions of Leapfrog Geo, Leapfrog Works, and Leapfrog Energy are now officially available to download from MySeequent.
This release is packed with updates to help you work faster, communicate more clearly, and get more from your models!
📢 Highlights include:
- Refreshed structural trends: Improved usability, visualisation, and data handling make interpreting structural data more intuitive.
- Standardised category colouring: Easily import and share colours across projects to streamline workflows.
- Improved cross sections: Enhance your communication of ground conditions.
- Smarter 3D filtering: Use correlation filter sets and hex colours to spot key geological changes faster.
- Copy Domained Estimation (Leapfrog Edge): Quickly build multi-domain, multi-variable estimates with new flexibility.
- Seequent Evo connection (Leapfrog Geo only): Leapfrog 2025.1 introduces cloud integration for collaborative workflows and cloud processing.
👉 Try it out and let us know what you think!
Re: How to call extension from GS script with relative paths?
@SerbanMarin1 My 'distribution process' is giving a zip a file containing a omn file and some py files and telling people to unzip it in the equivalent of C:\Users\v.savenije\Documents\Geosoft\Desktop Applications
So this one varies per user, and is problematic with absolute paths only GS scripts, because the username is inside the path. I think I landed at this location, because the error message that Oasis gives when it can't find the the python extension file points to this location ( C:\Users\v.savenije\Documents\Geosoft\Desktop Applications\python )
Re: Postgresql ODBC connection
If I understand well your message you figure it out how to connect to the PostgreSQL server (creating an ODBC connecton on your local machine and using that to connect Leapfrog to Postgres).
For me, the message you obtain is a proof that the connection is working. It's just that, probably, the database on Postgres it's not exactly structured or organised like the Leaqpfrog needs.
Sorry, I cannot help you more than that.
In my case, it was just that I did'nt figure out how to configure the ODBC connection.
Re: I want Advice on Managing Complex Geological Models in Leapfrog
Hello,
Yes, an easy way to divide and organize your 3D models is through the use of Central.
https://www.seequent.com/products-solutions/seequent-central/
Central allows you to centralize your datasets and your model revisions in one location which is good for team collaboration and peer review. For dividing the datasets and project volumes, you can create branches within your model to manage larger more complex geological models. This will help with processing times as well with general model management. There are many approaches to branching, either through physical zones that could follow natural breaks such as faults, or dividing by project scope such as by geochemical data versus geophysics data.
You can also pull data from Central directly into Leapfrog and if there are new updates to the file that you upload in the Central Files room, you will be prompted to refresh your datasets in Leapfrog when you next open up that Leapfrog project. The files in the Central Files room also has version control so you can download any previous versions as well.
Please feel free to reach out to support@seequent.com if you would like to learn more about using Central for your project or if you would like to hear about any training opportunities!
JennyNi1
I want Advice on Managing Complex Geological Models in Leapfrog
Hi everyone,
I have been working on a fairly complex geological model in Leapfrog & while I love the flexibility the software provides. I am starting to feel a bit overwhelmed with managing multiple data sets surfaces and volumes efficiently. Things are getting a little cluttered when trying to track changes or update certain layers based on new drillhole data.
I want to know if any of you have tips or workflows that help keep things organized & manageable. Do you use naming conventions or folder structures within Leapfrog that help keep the workspace clean Also how do you usually handle updates when the data changes frequently.
I am if there are any built-in tools or plugins you find useful for reviewing or validating complex models before sharing them with others.
Also i have check this https://community.seequent.com/group/discussions-mongoDB-course/1-data-management stil need advice . Also if any advice or shared experience would be appreciated.
Thank you…:)