assembly superelevation and shoulder elevations error

[granite07]

There are three issues with this section that I cannot resolve and need help with: 1) the median does not have superelevation, 2) the southbound (left) lane outer shoulder elevation is incorrectly at the roadway datum (L10), and 3) the northbound (right) lane elevation is incorrectly at the roadway datum (L10)

This subassembly document for the shoulder provides that "Link L10 is determined by the Subbase 3 Inner Depth and Super Elevation/Grade on Link L1, if a User...

 

And, this subassembly document for the median provides that "Indicates whether the subassembly supports the axis of rotation calculation. To view a description ... The text dialog hover states that axis of rotation is supported only if superelevation parameter (Potential Pivot Parameter?) for both lanes is set to NO; this is the setting.

[CyberAngel]

Welcome to the forum!

 

Is this an isolated section or one of a group of sections? That is, does the problem occur in one place or along the whole superelevated section?

 

Is it possible that the lanes are not showing properly while the shoulders are? That is, are the shoulders at the right elevations? Or are the lanes at the right elevations while the shoulders are wrong? Or are they both wrong?

 

I'm somewhat confused by the statement about "axis of rotation." Wouldn't you want to enable superelevation for the lanes?

[granite07]

Thank you for the welcome.

 

Answer:

From the cross-sections that I have parsed through it looks inconsistent.

 

• It is not clear what it depends on, the sections that target for width a retainingWall are better but not OK
  
• The sections that target for width a polyLine or roadway alignment are not close
  

The roadway is at the correct elevation.

 

I was confused by the axis of rotation too; by 'lanes' I think they mean either the median subassemblies superelevation is turned off or that the roadway subassemblies are not designated as potential pivot. I tried several permutations of configurations looking for one that worked.

 

Intuition for real issue:

Also, this model is in inch model space unit. Possibly the intera-assembly attachment elevation between subassemblies is calculated in feet so the elevation is correct but instead of 3' is 3". Someone with knowledge of c3d inner workings should be able to validate this.

[CyberAngel]

I don't work with corridors much. The fact that you're using the superelevation axis of rotation means you're already way ahead of me. As a complete shot in the dark, I'll suggest checking the link codes on the assembly template, because each subassembly should have links that match at least one link on an adjacent subassembly.

[granite07]

can't be that far ahead - this IS c3d we are talking about

 

A friend made a custom subassembly for me in both feet and inch model space unit; I compared the text of the subassembly file and see where the difference is; mostly just adding *12 here and there.

 

I am parsing through the 'Imperial - Lanes.atc' file with an xml viewer looking for where I can change the elevation to inch. Give it a few tests and see if it works!

 

Appreciate your help - now that this is more focused on the subassembly code I will repost to a forum with a dedicated .NET forum - and place a link to that thread here.

[CyberAngel]

can't be that far ahead - this IS c3d we are talking about

 

Let's see--you're dealing with superelevation, an output parameter for a custom subassembly, the code for the subassembly itself, an XML viewer, and .NET programming. Nothing like a power user to make you feel old.

[granite07]

I would not use the word 'use' more like 'trying' so nothing like being young ambitious, over your head, and maybe just not smart enough to know when to say when.