So I've had this problem where on my report it'll show Zero on my cut and fill and it is usually because the line crosses itself, usually happens when im joining up linework. TBC will usually show me where that error is with a blue flag, very helpfull, but on other occasions my Report will spit out a quantity in certain areas within my closed polyline (See image below) When I run a Report with several boundaries it can be easy to miss the fact that one of the boundaries did not calculate correctly. Im just not sure what it could be and why it would only calculate, from what I can tell, a random area.
Both my intial and final surfaces cover the entire boundry area so i should have and isopach for the entire thing. Has anyone had the same issue?
Eric
The Cut Fill Map references two surfaces as shown below here
The Cut Fill Map will create the Isopach Surface only where the two surfaces overlap - when I look at these two surfaces in the plan view I get the following
This is surface YCS_053019(DTM SUB ALL) in grey color - the red triangles are surface YCTopo_190923
The Red Surface does cover the whole of the Grey Surface Area so you should get a CF Map that is where the overlaps are if you run without any boundary lines
So now I ran a CF Map using the two surfaces and no boundary line and I get this
and this is what I get
When I apply your boundary AOI to the CF Map I get the same result as you did, however I made a copy of your AOI Boundary and changed it to look as below here
Now I applied these two boundaries as Surface Boundaries because based on what I could see from your AOI Boundary it is these two areas that you want to report (and an AOI can have two areas in one AOI as shown below)
And the CF Map now looks as I think you wanted it to look.
I attach the modified project here as a reference
What you did on paper looks OK and I will send it in to QA to take a look at what happened in your AOI case - While this was the way that Paydirt AOIs worked, TBC has the ability to do separate islands in the model and holes etc in models which Paydirt did not, and I guess the two areas separated by the narrow gap with this specific set of data and the underlying surface models and the way that the Triangle Faces and Boundary Lines do / do not line up is some data glitch - because I also did an offset line 0.05' inside your AOI line and I get the result you wanted
So I guess it is a "zero check error" of some kind here where the boundary line is slightly off the triangle sides of the surfaces but so close that it throws some kind of error in the calculation - if you see this type of thing happening, often a very small offset to your boundary line will make all the difference - our internal "point tolerance" is 0.1mm which is 0.00032' (very small), but sometimes these small defects cause this type of issue - so I would sometimes offset my boundary line by anything from e.g. 0.001' or 0.005' or 0.01' just to see if that makes a difference.
Hope this helps
Alan