Trimble Business Center

Erik Petersen posted 01-19-2024 12:17

You probably have a overlapping line somewhere on your boundary line. Try off setting it 5 feet and you will probably have a huge long line. that can usually help help you find out where its at.

Line offset 5' does this 

Victor O'brien posted 01-21-2024 09:24

Erik,

I had no overlapping line loops. I drew a new boundary, nothing changed. I was thinking I have a setting messed up.

Ronny Schneider posted 01-21-2024 10:05

Which TBC version are you using?

How quick does the report appear? Does it look as if it's doing any calculations at all?

Did you create the outline by hand or programmatically by using an isopach or surface edge breakline? I had an issue with too small/short elements within the boundary before.

See here bug earthworks report V5.30 | Trimble Business Center

Victor O'brien posted 01-23-2024 07:24

Hi Ronny,

Version 5.90

It does appear to be calculating before report is generated.

I drew the boundary by hand. I did not add the hand drawn boundary to the isopach surface.

Ronny Schneider posted 01-23-2024 08:34

How big are your surfaces? Would it be possible to upload them as TTMs and the boundary as DXF?

I haven't got a valid licence at hand right now, I'd have to try to get another demo licence. But I'd have a look in the viewer if anything stands out. And can try it in the old HCE version, which allows to run earthworks reports without licence. If it doesn't work there either it would point to something in your data.

Victor O'brien posted 01-24-2024 12:30

Small Surfaces. 69,000 square feet.

I think one of my issues is the surfaces don't extend all the way to the surface boundary. I use the same boundary for all the surfaces, but they are all have a different square footage.

There is not enough data extending out to the boundary. I typically use the property line as the boundary. I used Paydirt for about a billion years and it would interpolate to the AOI.

 

Ronny Schneider posted 01-24-2024 15:46

That the boundary is larger than the surface shouldn't be any issue. It would just crop/retriangulate the surface before computing the Isopach. In your case it only would have to crop it marginally.

Does it create the "Isopach" under Cut/Fill Maps in the project explorer? If yes, and if you show the properties of it, what does that one say about the volumes? If those are correct it points to an issue with the report template that came with 5.90.

There had been issues with stockpile/depression computations and if the report language was anything but English. But that was fixed in 5.80.

The just released 2023.11 notes include "The Earthworks Summary report included incorrect total volume calculations". Not sure which constellation that is referring to and to which version the fixed bug dates back.