How does the 'Compute Materials' QTO function differ from the 'Corridor Properties/Code/Code Set Style/Link|Point/PayItem' QTO function - I understand that the measurement is obtained using a different approach - I'd like to know why one method is used over another method? They both appear to provide the quantity for the same ACAD model object?
Also, same question for the 'Volumes' QTO function - I understand this function is only for volume difference between two surfaces but the Corridor Code payItem and Compute Materials documentation appears to say they also compute difference of surface volumes, but I do not see where you define the comparison surface so doubt this is correct and I must misunderstand the authors.
I think the corridor quantities are for linear feet (Points) and area calcualtions (Links). The Compute Materials QTO function is for volumes of materials (shapes) from the corridor. If you create a material criteria for surfaces you can use them in the Comput Materials. http://screencast.com/t/pqk9s8dnqz
I don't think the QTO functions are user friendly. I despise having to run it more then once for each material group. It really needs a dialog box interface to let the user run multiple reports from one place.
That sounds like the actual truth of C3D but was it intended the QTO would report volumes too?
In the corridor properties code tab, payItems can be assigned to the link and point code set style codes. The links are 2D and the Points are lines, but the links can also be 3D if a volume unit of measure is designated in the payItem file. For the subassembly.MedianFlushWithBarrier with a specified Pave1 depth .951' the QTO report found the correct CY volume of 156.96CY; there is more to this specific test documented here http://cife.stanford.edu/wiki/doku.php?id=granite:
The question: While Autodesk intended the QTO function to report volumes, in reality it has unresolved issues so the Compute Material should actually be used for volumes and QTO only used only for 2D and lines?
I was going to report volumes using QTO but I'd rather avoid any issues with this if Compute Material is a cleaner approach.
I have absolutly no idea what it is you are trying to say or do, but I noticed on your link you set up your "model space units to inch"
Civil3d does not work in inch units - it works in decimal feet of meter.
Thank you for pointing out the issue with inch msu - I am well aware of this.
Also, good adice about earthwork. I was an earthwork engineer with the Granite Construction Heavy Construction Division on a large design-build project. The equipment manager retired unexpectedly so I was also the equipment manager for a regional comapny sized fleet. I can appreciate what you are saying and it is under control.
Civil 3D has three quantity takeoff functions, "volumes", "compute materials", and "takeoff" by payItem
As I understand it:
When is "takeoff" by payItem used for volume in place of "compute materials"?
Also, a note on earthwork shrink and swell - haul truck factors for computing bank and embank volumes - this is vastly more significant than the compaction shrink. Unless you complete a laser scan or can survey a square earthwork object with clean edges, you have no clue what your actual volumes are in bank, loose, or embank units. And, scales were made to be tampered with and teamsters were made to eat lunch and add an extra tick mark to their time cards. Last, this is assuming you can even track what type of haul trucks you are running and the actual fill factor for the trailers by material type. The fill is done when it is filled and the excavation is done when the hole is there - how much was it? It was that much, who cares we are working on something else today, I also understand the field mentaility out where it counts.