Trimble Business Center

 View Only
Expand all | Collapse all

Why are my Earthwork Reports showing "0" volumes?

  • 1.  Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 07:58
      |   view attached

    I'm trying to run an earthwork report between two surfaces using a boundary. It takes about 15 minutes to compute, then when the report is done generating it shows Cut=0.0, Fill=0.5 Yds. The closed boundary covers 39 acres, all of which encompasses the two surfaces with fills up to 33'.  

     

    Attachment(s)

    zip
    0 Volume.html.zip   1 KB 1 version


  • 2.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 09:45

    Please upload your .vce file so we can take a look.



  • 3.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 10:43


  • 4.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 10:33

    I have this happen commonly when my surface boundaries have edges that cross ("bowties"), or if they boundary has a segment "on top" of another segment.  Sometimes it's hard to track these down, so I'll just redraw my boundary over the existing boundary, then delete the old boundary line.  

     

    It could be something else however.  



  • 5.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 11:11

    I do this too. I also usually offset my line .01 to .1 then re run the report due to above. Also are you using a drone surface I'm assuming? Do make calculations faster go in to Project Settings>Computations>Surface and then turn Volume Computation: to Do Not Track Breakelines.



  • 6.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 11:26

    I've gone through the line and there's no overlapping, or crisscrossing segments. I have had that happen before though, not sure what's going on this time around, I've tried just about everything. Also, no it's not any drone data, just a really big site with multiple surface levels. The file does seem to be uncharacteristically large though, I've worked with drone data that covers the same area before and still kept the VCE files under 150MB. 



  • 7.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 11:38

    I'm assuming you're using the 0 Levee BNDY for your volumes and these two surfaces because they're the same color as your x-section?

    I ended up running project clean up with the following and turning off do not track breaklines

    and it shrunk it down to 77 megs. 

     

    Here is the link to the project

    Rackstation - Synology RackStation 



  • 8.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 12:24

    Thanks, The VCE file that I sent was actually one that I just made quick because the same issue was happening in the main file that I'm using which is actually a little smaller. I exported the surfaces out of the main file, and imported my boundaries just to see if the same issue occurred. It did, so then I imported the design linework and made some new quick and dirty surfaces (hence the multiple same surfaces with different names) to try that, and had the same problem. These files have been somewhat of a pain to work with, every cad arc, and several lines were set to a different UCS, so I've had to do a lot of manual cleanup that the project cleanup wouldn't fix on it's own. 

          I did just run the project cleanup on my main file, and re ran the EW report with success, thank you for the help. I wonder what it is in the imported files that causes this? Must be those UCS arcs that come in way off in elevation but tie into the surface fine. 



  • 9.  Re: Why are my Earthwork Reports showing "0" volumes?

    Posted 08-15-2019 12:39

    I redrew a new polyline over your existing levee boundary line and ran the surface volume report with success.  Actually, that's not true.  It didn't work until I changed the "closed" property of the polyline.  It should have been closed but for some reason it wasn't being reported as such.  Then I ran the report successfully.