Basic shoulder computing as pave1

[WIZNICKARTS]

Okay here's the deal. I'm running civil 2010 and I defined an assembly using laneoutsidesuper a curb and gutter and a basic shoulder follwowed by some daylight links........simple right? I defined a materials list and added materials for pave1, pave2, base, sub-base, curb and gutter. The problem is the basic shoulder does not appear as a corridor shape in the quanitity takeoff in order to assign it as a seperate material...........furthermore, it's computing all of the basic shoulder material as pave1 when I generate the volume report. Anyone got any ideas?

[Anonymous]

From the help for Basic Shoulder:

This subassembly creates a simple paved shoulder with finish grade and
subbase.

Note the paved part......further down in the help the Codes are described,
with the Shape code being Pave1.

If you need something else, use one of the more complex shoulder
subassemblies. Or you could edit the program code and recompile the dll to
your liking.

"wiznickarts" wrote in message news:6398611@discussion.autodesk.com...
> Okay here's the deal. I'm running civil 2010 and I defined an assembly
> using laneoutsidesuper a curb and gutter and a basic shoulder follwowed by
> some daylight links........simple right? I defined a materials list and
> added materials for pave1, pave2, base, sub-base, curb and gutter. The
> problem is the basic shoulder does not appear as a corridor shape in the
> quanitity takeoff in order to assign it as a seperate
> material...........furthermore, it's computing all of the basic shoulder
> material as pave1 when I generate the volume report. Anyone got any ideas?

[WIZNICKARTS]

Thats good information but it still doesn't explain why it cannot be computed as a seperate quantity as in why is it not showing up as a corridor shape to be able to compute it as a seperate material. I never had this problem in 2008. However I will try one of the more complex shoulders as you suggested and see what it comes up with. I'll keep you posted.

[Anonymous]

On 5/27/2010 10:57 AM, wiznickarts wrote:
> Thats good information but it still doesn't explain why it cannot be
> computed as a seperate quantity as in why is it not showing up as a
> corridor shape to be able to compute it as a seperate material. I
> never had this problem in 2008. However I will try one of the more
> complex shoulders as you suggested and see what it comes up with.
> I'll keep you posted.

As Jeff said, if you look further down in the help file, it explains
that the codes are described, along with the shape of Pave1. The
subassembly is a paved shoulder, so the materials calculate it as Pave1
along with any other subassembly that might have that shape code assigned.

--

Regards,

Jason Hickey
Autodesk Product Support
http://beingcivil.typepad.com

[WIZNICKARTS]

Thanks for the information guys. I was able to get the quantity I needed using a more complex shoulder assembly. Autodesk should really think this one through on the next release. There should never and I repeat "NEVER"! be an instance where something can be called a shoulder assembly and not be computed as a seperate quantity. Even in instances of paved shoulder, none of the 26 different departments of transportation that I have ever worked for would ever allow the same quality of pavement used on the road to be used on the shoulder. Unless your project just has a lot of extra money in it and you can afford that type of shoulder treatment, but even then, they would demand that the shoulder quantity be kept seperate for cutting should the budget run low. I guess we just have to learn some things the hard way as I am now about to go and replace 27 different basic shoulder sub-assemblies with more complex ones............sheesh.

[Anonymous]

Sorry, but the Basic Subassemblies were not meant for the purpose you were
trying to use them. Again from the Help for the Sub:

This subassembly is one of a group of Getting Started subassemblies used for
simple roadway modeling, and for tutorial and training purposes.

This one sentence told me that after I was done with the tutorials I'd never
look at them again. And now you know, too. 🙂

Jeff

"wiznickarts" wrote in message news:6398864@discussion.autodesk.com...
> Thanks for the information guys. I was able to get the quantity I needed
> using a more complex shoulder assembly. Autodesk should really think this
> one through on the next release. There should never and I repeat "NEVER"!
> be an instance where something can be called a shoulder assembly and not
> be computed as a seperate quantity. Even in instances of paved shoulder,
> none of the 26 different departments of transportation that I have ever
> worked for would ever allow the same quality of pavement used on the road
> to be used on the shoulder. Unless your project just has a lot of extra
> money in it and you can afford that type of shoulder treatment, but even
> then, they would demand that the shoulder quantity be kept seperate for
> cutting should the budget run low. I guess we just have to learn some
> things the hard way as I am now about to go and replace 27 different basic
> shoulder sub-assemblies with more complex ones............sheesh.