Baseline not showing in section of data shortcut corridor

[Anonymous]

I have a corridor built from two baselines data shortcut into a drawing to produce cross-sections. One of my baselines is not showing in the data shortcut. I can see cross-sections of the other baseline along the alignment but for one specific baseline it is not showing, so it's not a case of not sampling that feature.

I've attached a couple photos showing that the corridor is visible in the original modeling file but not in the data shortcut file.

[Civil3DReminders_com]

Is the sample line not skewed relative to the corridor? Is the sample line at the exact station of the corridor? 

If not then the corridor data shortcut probably won't show the data correctly, as you are experiencing. 

I'd suggest using the XREF the corridor drawing method instead. 

Autodesk didn't bother to create a useful data shortcut object for the corridor and leaves all of the functionality out of the product when it comes to cross sections from corridor data shortcuts.   

[Anonymous]

I think you may be right, because I'm using offset subassemblies the subassembly likely perpendicular to the offset alignment but slightly skewed to the baseline alignment and therefore skewed to the sample line. I tried to use the same intervals for the assembly drops as the sample lines but apparently it's skewed.

I find it very odd that C3D doesn't allow interpolation of the data shortcut corridor between points of the assembly. It seems like the most logical work flow is to have the model in one drawing and data shortcut into another to produce cross sections.

I'm unsure of the xref method. Are you saying xref the model into my x-section drawing and produce sections from it. How could the sample lines pick up the corridor through the x-ref?

Thanks

[Civil3DReminders_com · Accepted solution]

Autodesk didn't foresee you using the product as you are. 

The xref method copies the dwg file locally and then accesses the database to create sections at the skewed location. 

The data shortcut method opens the source dwg and only gets a dumbed down version of the corridor with no link to the assembly data. Without the data it can't create an accurate section. So instead of creating an accurate section it skips it. 

I doubt this gets fixed in 2020 or 2021.

[Anonymous]

It seems quite useless to shortcut a corridor and not be able to have the full function of it minus the editing aspect. It renders the ability to data shortcut a corridor useless and unnecessary in a typical workflow.

Thanks for your help.