Shoulder Vertical Subbase

C3D ShoulderVerticalSubbase — 4 layers on a vertical outer edge + unpaved wing

At a glance


Kind	Subassembly (composed into an assembly)
Domain	Road
Civil 3D equivalent	`ShoulderVerticalSubbase`
Geometry	11 points, 14 links, 4 shapes
Targets	1 (surface / offset / elevation targets this subassembly can be linked to)

Parameters

Defaults are the metric values the palette inserts. Every parameter can be driven by an expression or a target.

Parameter	Type	Default	Meaning
`Side`	+1 right of the baseline, −1 left	Right (+1)	+1 Right / -1 Left
`PavedWidth`	number (metres unless the description says otherwise)	2.4	Paved shoulder width (m)
`DefaultPavedSlope`	cross slope as a ratio (−0.02 = 2 % fall)	-0.06	Paved cross slope (SE fallback)
`UnpavedLinkTreatment`	number (metres unless the description says otherwise)	1	1 always / 2 cut only / 3 when paved slope > 0
`UnpavedWidth`	number (metres unless the description says otherwise)	1.8	Unpaved wing width (m)
`UnpavedSlope`	cross slope as a ratio (−0.02 = 2 % fall)	-0.06	Unpaved wing slope
`UnpavedMaxBreakover`	cross slope as a ratio (−0.02 = 2 % fall)	0.08	Max grade break paved->unpaved
`Pave1Depth`	number (metres unless the description says otherwise)	0.025	Pave1 depth (m)
`Pave2Depth`	number (metres unless the description says otherwise)	0.025	Pave2 depth (m)
`BaseDepth`	number (metres unless the description says otherwise)	0.15	Base depth (m)
`SubbaseDepth`	number (metres unless the description says otherwise)	0.3	Subbase depth (m)

Points

Point codes are what feature lines, styles and quantity take-off match on — they are the contract this subassembly publishes.

Point	Code	Placed	From	Expression
`P1`	—	placed at the attachment point (an absolute offset/elevation)	—	`0 / 0`
`P2`	EPS	offset + elevation delta from the reference point	P1	`SidePavedWidth / PavedWidthDefaultPavedSlope`
`P3`	ES_Unpaved	offset + elevation delta from the reference point	P2	`SideUnpavedWidthG / UnpavedWidthUSG`
`P4`	—	offset + elevation delta from the reference point	P1	`0 / -Pave1Depth`
`P5`	EPS_Pave1	offset + elevation delta from the reference point	P2	`0 / -Pave1Depth`
`P6`	—	offset + elevation delta from the reference point	P4	`0 / -Pave2Depth`
`P7`	EPS_Pave2	offset + elevation delta from the reference point	P5	`0 / -Pave2Depth`
`P8`	—	offset + elevation delta from the reference point	P6	`0 / -BaseDepth`
`P9`	EPS_Base	offset + elevation delta from the reference point	P7	`0 / -BaseDepth`
`P10`	—	offset + elevation delta from the reference point	P8	`0 / -SubbaseDepth`
`P11`	EPS_Sub	offset + elevation delta from the reference point	P9	`0 / -SubbaseDepth`

Links

Link	Code	Between	Role
`L1`	Top,Pave	P1 → P2	drawn
`LU`	Top,Datum,Slope_Link	P2 → P3	drawn
`L3`	Pave1	P4 → P5	drawn
`L4`	Pave2	P6 → P7	drawn
`L5`	Base	P8 → P9	drawn
`L6`	SubBase,Datum	P10 → P11	drawn
`V1`	—	P1 → P4	drawn
`V2`	—	P4 → P6	drawn
`V3`	—	P6 → P8	drawn
`V4`	—	P8 → P10	drawn
`W1`	Datum	P2 → P5	drawn
`W2`	Datum	P5 → P7	drawn
`W3`	Datum	P7 → P9	drawn
`W4`	Datum	P9 → P11	drawn

Shapes (materials)

Shape	Material code	Boundary points
`S1`	Pave1	P1, P2, P5, P4
`S2`	Pave2	P4, P5, P7, P6
`S3`	Base	P6, P7, P9, P8
`S4`	SubBase	P8, P9, P11, P10

Generated page. The tables above are read from the built-in catalogue itself (yu3d_stock_dump), so they always match the version of yucad3d you are running.