Civil 3D 2019 corridor data references have crossing feature lines

[mgonzalez_symetri]

I've noticed that when you data reference a corridor in C3D 2019, wherever there is a region with a different assembly (even when all the codes are the same), the feature lines cross from one side to the other. It's perfectly fine in the source drawing, having checked it in model view, and using the same template and styles as the source drawing. I've even tested it with an intersection created with the intersection wizard, and it does the same thing.

have already installed the latest updates as of 11/1/2018

The pictures below show the corridor, first in the source drawing, the second in the data reference. This is the case whether the corridor is targeted or not. The subassembly used all have the same codes, so it should connect just fine. This is very confusing.

source drawingdata reference

[erdemcelenk]

Hi,

Have you tried  to space ( like 0.01m ) between each region through Corridor Properties? 

Regards,

[Anonymous]

Wanted to bump this up as it is still happening in 2020.. Has anyone figured this issue out??

[Anonymous]

Someone explain to me for what reason would you ever need to data ref a corridor?

keep the corridor in one drawing and data ref the resulting surface.

[dgladfelter]

Cross sections are a key use case to DREFing Corridors. Having the Corridor, Corridor Surface, and Cross Sections (especially if it's a long road) in a single DWG can result in a very heavy (aka alow drawing).

DREFs (theoretically) allow you to break that down into more manageable pieces; perhaps one Corridor DWG with several Cross Section drawings.

[Anonymous]

D'ref corridors are super beneficial to use in a grading file. D'ref the corridor, extract the outer feature lines and use those for grading the lots. 

[Anonymous]

Why not just extract the featurelines from the original corridor n the original file and either use those in a surface in the same drawing file, or cut paste them or write block them to another file?

[Anonymous]

feature lines are only dynamic if the are extracted in the same file as the corridor or its dref. files grow to big to manage if grading is also done in the same file as a corridor. Especially if you have multiple intersections, drainage ponds, etc.

[Anonymous]

I must be missing something. I've never considered a corridor as a memory hog in a drawing. Are many of you really experiencing crippling drawings because your corridor is in the same drawing as your surface?
I've never experienced this, and I've created some massive site plans with multiple intersections with ease.

[clayton_lewis]

Did you resolve this issue? Our group is running into the same problem.

See the attached images.

[Anonymous]

I have not resolved this issue happens often with corridor data shortcuts.

[Wojtek_Garczewski · Accepted solution]

Hi all,

Please see the below thread for a solution for the corridor data shortcuts issue:
Solved: Data Referenced Corridor Code Set Style not working properly

Thanks,
Wojtek