Community
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Incorrect QTO data in AutoCAD Civil 3D with custom curb subassemblies

Incorrect QTO data in AutoCAD Civil 3D with custom curb subassemblies

Dear colleagues!

A couple of days ago i encountered a problem with a computations of curb length over all corridors in a DWG file. For the curb i used my custom curb. Fortunately, i have found out why. In fact, for this we need to assign a pay item for any point code in the curb subassembly. I did everything correctly, but the report turned with wrong sums.

What seems to you as the cause?

In fact, points in my curb were coded with spaces, for instance, "Insertion Point", "Curb Top Inside", "Curb Top Outside", and so on. My curb worked correctly like the similar predefined subassembly, left except the trouble with using its codes for quantity take offs.

I found this out when comparing my manner of coding with codes in predefined Civil subassemblies coded with no such spaces. I felt that this was the matter and change my curb point codes to "InsertionPoint", "CurbTopInside", "CurbTopOutside", and so on.

And now my curb lengths is perfectly calculated and updated with the Takeoff tool!!

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea  

Answer Day

Rail Community


Autodesk Design & Make Report