Can't Create a Corridor Data Shortcut

[khaledCULN8]

Hi,

I've a file just for my Alingments and another one for my Corridor.

in order to not overload my corridor file, I've Created another file just for my Cross Sections.

For that, I've Created a regular Corridor Data Shortcut. 

I don't why, but i Couldn't create the Reference for the Corridor in my Cross section file.

I can see that the shortcut in the Prospector, but when i create the reference, the file just keep loading and nothing happens.

I've waited for almost an hour, but the process could not be completed.

I've tried a different Cross Section file and a new Corridor file (by save as) but i keep getting the same result.

has anyone experienced something like that?

Thank you for your help.

Khaled 

[Joe-Bouza]

Mercer worked for me. Known Issie :does not support offset assemblies

if all you are doing is sections. Xref the corridor; xref the alignment and add sample lines and section views.

must ATTACH. Xref

[tcorey]

What version are you using? The latest updates for Civil 3D versions are:

Civil 3D 2018.3 update

Civil 3D 2019.3 update

Civil 3D 2020.3 update

(That's from memory and someone please correct this information if I have erred.)

You can type ABOUT on the command line. This will tell you your current version. If you don't have the latest update, as listed above, you should do that first. Maybe your error has been fixed. Be sure to update AutoCAD to the latest, too. Civil 3D updates do not include AutoCAD updates. It would be nice, but that's a discussion for another day.   😉

[khaledCULN8]

Hi,

I'm working with the Latest version of civil 3D (civil 3D 2020.3).

still, i couln't create the shortcut.

Khaled

[khaledCULN8]

Hi,

I didn't understand what you wrote in the first sentence.

but, I do have some offset Alignments (corridor targets). but the corridor built from a regular alingment.

Khaled

[Joe-Bouza · Accepted solution]

Sorry, I was using my phone and the web site and iphones don't mix well

DS Corridor has never worked for me. Known Issue : Dref corridors does not support corridors that use offset assemblies

if all you are doing is cross sections.  simply Xref the corridor;Dref the alignment and add sample lines and  the corridor section will work. even if offset assemblies are in use.

must ATTACH. Xref

[khaledCULN8]

Hi,

I need more that cross section. so your way is not ganna cut it.

khaled

[Joe-Bouza]

Silly me .

[khaledCULN8]

Hi,

I'm sorry if i offended you in any way.

yes, i need a new file just for my cross sections.

but i need to project multiple things into the cross section views. Crossings, some feature lines etc...

and create some surfaces to calculate fill/cut volumes.

if your way can manage that, I'll gladly try it.

khaled

[Joe-Bouza]

No offense. I'm just busting your chops. You did specifically say for cross sections.😎

but i need to project multiple things into the cross section views. Crossings, some feature lines etc...

and create some surfaces to calculate fill/cut volumes.

if your way can manage that, I'll gladly try it.

you do not need to data ref a corridor to project object to views including crossing and feature lines. data ref the pipe etc. Data ref into a new file your alignments, profiles , pipes and surface. Xref the corridor as "ATTACH" and go.

IMO data ref a corridor is intended for those that set their code set styles in such a way to use the corridor lines for the plan lines. XREF-ing the corridor for sections is a workflow that has been in the books for a while. Make sure the code set style you want the section to show is in the new drawing

making the the surface in the corridor file should not crush performance; set the display to minimal (maybe off unless in the corridor parent you have to see something)

[khaledCULN8]

Hi,

I've tried your way and it worked!.

one problem: there is a section that not displaying the whole data.

both with same code set style.

almost all the sections are showing the whole data. but Some of the subassemblies and labels (elevations) are missing in some of them.

I've atttached a photo showing the same section created in the corridor file (Left) and the one created in the cross section file (right).

any reason for this strange outcome?

khaled

[Joe-Bouza]

You sure you have the exact codeset style in both and MOST IMPORTANT :The corridor HAS TO BE  xrefed as ATTACH no overlay

[khaledCULN8]

Hi,

yes. I'm sure that i do have the exact code set style in both files.

also, the corridor is xrefed as attach not overlay (see the attached photo).

as i explained, the problem in a few of the sections. so for most of the sections, everything is fine.

Khlaed

[Wojtek_Garczewski]

Hi @khaledCULN8 

I see that some of your initial questions have been resolved by @Joe-Bouza. Thanks for your contribution to this topic.

Please check if all necessary corridors are added to the sample sources.

If so, please try to delete all sources from the section sources, apply and close. Then add back all needed sources again. 

If above didn't help, can you share the model with us, so we can have a closer look at it, please?

Regards,

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[khaledCULN8]

Hi,

unfortunatley, none of what you said helped.

here is a link to download the file.

Corridor File 

Khaled

[Joe-Bouza]

A little preamble on the files would be helpful.

looking  now

[Joe-Bouza]

What stations are you missing or incomplete corridor section?

I just did it and they all look complete to me

[Joe-Bouza · Accepted solution]

I cut the section in the corridor file and the same section in a cross section file and they are all identical. No missing parts.

Maybe you have missed something in the work flow. 

lets take the styles and code set match out of the equation Try this:

I will assume you have data shortcuts for the alignments surfaces, pipes , etc.

1. make all the xrefs in your corridor file type = overlay, save

2. then save as "sections- xref corridor.dwg"

3. now in the toolspace prospector remove all the civil3d objects except your feature lines

4. Xref the corridor file as ATTACH

5. dref AXIS 1 RAMOT alignment, the pipe network, and surface

6. add sample lines  be sure to chaned the corridor style from basin to Cross Section -JTMT

7. plot your sections using your prefered section view style

8. project you Feature lines

[JaysonE]

@Joe-Bouza 

I apologize that I'm about a month late to the party. 

But, what do you mean data referencing does not support offset assemblies?

How does AutoCAD expected me to design a roundabout or any other kind of road without using assemblies that use offsets?

[Joe-Bouza]

No worries.

there is a known issue with data referencing a corridor that employs the use of an offset assembly.

Offset assemblies are the same pieces used in an assembly but there is a option to use an offset node that follows its own alignment and profiles.

often used when a corridor might have transition areas that are not parallel to the base line. Example a curb and sidewalk that meanders away or towards the baseline. the method keeps the insertion of the subs perpendicular to their base line instead of the central base line thus creating a more true model