Bug? Incomplete "Estimate Structural Data" (from points).

JosephMillard
JosephMillard Posts: 4
in Leapfrog

Hi all,

I am trying to model stratigraphy from structural disks because disks are editable and not tied to (or affected by) ODBC refreshes. I create points by Points → New Points → New Contact Points. Then I create structural disks from those contact points by Contact Points → Estimate Structural Data. During the step of creating those disks, LF fails to create disks for all the points. Sometimes, it will only create one or two disks, or maybe the southern half of the disks, or the northern 1/5th of the disks. I seem to get different results depending on which units i "ignore" or utilize during the point creation process. In my photos, you can see that utilizing the Tv unit creates a different result from ignoring the Tv unit. There is come consistency - if I repeat the point generation procedure and structural estimate disk creation exactly the same each time, I get identical disk (abet incomplete) generation.

I've tried doing this same process on different sets of points, on different projects, and I've even sent it to a coworker who gets the exact same disk generation (abet incomplete).

If someone has a solution to this problem, please reach out.

Thanks

image.png image.png

Answers

  • JosephMillard
    JosephMillard Posts: 4

    Oh. I am using Version 2025.2. I think that's the latest as of 11/8/2025.

  • NiklasSääv
    NiklasSääv Posts: 19 mod

    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.

    The only way is forward!

Categories