Section view not displaying corridors properly

[Anonymous]

Dear Civil 3D experts, 

When I create my section views for my Railway design I encounter a problem with displaying all corridors. As show in the screenshot below. 

You see here 4 rail corridors. In the top section view they are displayed as normal. The bottom section view is missing the ballast on the left corridor, and a block for, what we call, 'profile of free space'. This block is missing from my second corridor as well. This block is defined in a marker style. 

This problem seems to occur more frequently when the corridor alignments are not perfectly parallel, for example in corners. But even when they are parallel they bug out. I have tried the following things to resolve this issue:

- Increase the frequentie of the corridors. - Didn't help

- Reset the code set styles. Or give one corridor a different set then the others. 

- Lengthening a sample line. Did sometimes fix this problem (looks like it recalculates the section view). 

- Recreating the section views. Did also fix some of the problems. But still not all section views where properly displayed. 

- Making a surface is not a solution here because I am missing a shape not just a line. 

- For this test I didn't use any data shortcuts. 

Does anyone know a solution?

I am using civil 3D 2015. But opening this drawing in 2017 and recalculating everything didn't resolve this problem.

[tcorey]

Can you post the drawing file?

[Anonymous]

Unfortunately my projects confidentiality agreement wont allow me sending this file. But when I get some spare time, I will build a similar drawing with the stock rail assembly and code set style. I will get back to you. 

But nonetheless I would think this is a mayor, and therefore well known, problem for a lot of users. Being able to view multiple corridors in a cross section seems quite vital. 

[Jay_B]

Do all Sections have a companion Corridor Frequency Line matching the exact same station of Sample Line?

[Anonymous]

---

@Anonymous wrote:

Do all Sections have a companion Corridor Frequency Line matching the exact same station of Sample Line?

---

Yes all 4 rail corridor's use a corridor feature line (the pink one) of a 5th corridor which calculates the ballast height. When I raise that 5th corridors frequentie to say calculate every 1 meter, the 4 other corridor's will be calculated every meter as well:

 

[Anonymous]

The problem seems solved with AutoDesk Civil 3d 2017. 

[Anonymous]

Discovered the same issue in C3D 2018 version.
I do the same command in the same drawing.
Corridor sometimes show sometimes not.
It spend me half day on it. Finally found this post.
Every year we pay to update and we always painful in your bug. Are we work for Autodesk?
Are we tester of Autodesk?
No as we paid and work for you.

[Anonymous · Accepted solution]

So, it has been a while. But my previous mentioned solution (upgrading to the newest version) did not suffice. But in the meantime, I have been in contact with an infrastructure specialist at AutoDesk. He looked into this problem, and we found a partial solution.

First part of the problem was partly in my subassambly. There was a situation in which the SA would create a line with zero length. And this line was used to create a shape. Even though there where multiple places in my corridor in which this situation would occur and in some of these places the shape would be properly displayed. But still in some section views it wouldn't show, as seen in the original post.  

     

So, the solution was to never create this zero-length line.

But there where some other strange things happening with this bug.

1- First even though my shape code was not showing in my section view. It was showing in an Isometric view of the corridor.

This means the zero-length link did create a shape for the Isometric view but not for the section view. This can be resolved with the previously mentioned bug fix, be sure you do not create a zero-length link.

2- Secondly the point codes (the ones showing the height of the track) are missing in the section views as well. This happens to the point codes from corridor's that are not linked to the alignment that has the sample lines. This is a bug which AutoDesk hopes to resolve soon. 

You can use the following workaround. First create the corridor's as you normally would. Extract feature lines from corridor. Create subassembly where a point (with point code) is created at a target elevation and target offset. Use this SA to create the point code in your main corridor (targeting the extracted feature line)

3 - Another thing that this bug showed us was what happens with volume tables in section views. The volume that is calculated uses the area of the shape in your section view, multiplied by the distance between sample lines. What this means is that if your shape codes are not completely visible in a section view, you get an incorrect volume. The one that is based on an incomplete area. Not only wouldn't the volume be calculated when a shape is incorrectly displayed like with the 1st bug, but also when your sample line doesn’t contain the complete corridor.

So always check your sample lines and corridors to be sure the whole corridor is within you sample line width. 

The TL;DR version:

- Shape codes are not properly calculated when it is created with a zero-length link

- Point codes in secondary corridors are not displayed in section view. AutoDesk is working on it.

- Volume/Area is only calculated using the shape that is within a sample line. If a shape is partly outside of a sample line, it does not use the complete area in the calculations. 

[Anonymous]

2- Secondly the point codes (the ones showing the height of the track) are missing in the section views as well. This happens to the point codes from corridor's that are not linked to the alignment that has the sample lines. This is a bug which AutoDesk hopes to resolve soon. 

This bug makes my work with civil very unpleasent every day. Please fix it soon !!!!

The Corridor is a very good all-round tool in civil 3D. But if I can't label the corridor in the section views it is (almost) useless.

I attach an example which i have tested in Version 2019.0.1.

Two alignment for two Railtracks (Gleis 1 und Gleis2). The lines are parallel. The curves are non parallel.

The Corridor and the samplelines are definedt with Alignment "Gleis 1"

I want to label the left rail, the right rail and the gradient.

Section 514, labels are ok (two parallel lines)

Section 2920, labels "Gleis 2" is wrong

Section 975, labels  "Gleis 1" and "Gleis 2" are wrong 

[Anonymous]

I am not sure when they are able to fix this. They couldn't tell me. But in the meantime you can try the workaround. See the attached .pkt. Create a Feature line of the SOK point from the Gleis2 corridor, and use that as target for the SOK_Target.pkt subassembly (which you connect to your main alignment, same as the alignment used for your sample lines). You will need to copy the SA and rename for your other point codes. It is quite time consuming. But at least you can make the point codes visible. 

[Anonymous]

Thank you for your answer J_Koedik, I will try your work arround.

Another option is, to project the feature line into the section view and label the intersection of the feature line.

But I think, their are general Problems with the code-set-labels in the Section-view. If you look at profile 975. The label are wrong in the mean corridor "Gleis 1" and the non parallel corridor "Gleis 2".

I hope, autodesk fix this bug soon, because every work arround is error-prone and waste time.  😉

[alex_montanus]

I also have this problem with my custom subassemblies. Some of the autodesk subassemblies don't have this problem (for example the LinkWidthandSlope). But for my custom subassemblies some points will appear or disappear based on the setting of some variables in the subassembly. For example showing the thickness of the asfalt. It looks like something that can be fixed in the custom subassembly or in the way Civil3D defines the points in the sectionview.

I have a screencast of what is happening. I have tested this in Civil3D 2020

[Anonymous]

Hi Alex,

From what I can tell, you have the problem of point codes not being visible in your section view. Unfortunately I only know the above mentioned workaround.

So make sure the point codes you want to show are in a corridor linked to the same alignment as the section views.

Workaround:

If those point codes are on a corridor linked to a different alignment. You need to extract them as feature lines. And create a new corridor linked to main alignment. In the new corridor make a point which uses target offset and target elevation, which you link to the extracted feature lines. That new point will be visible in the section view.

Good luck

[Jowennl · Accepted solution]

Hi @Anonymous  / @alex_montanus  / @Anonymous ,

I saw this old post the other day and wanted to add some more guidance in preventing the issue and finding a better workflow. Please refer to my <AU Class CI123653 Link> to see workaround demo using 0001 Method:

Item 1. Always make sure no zero length link created in your corridor as this will cause problem with solid output and section view creation.
Check out 35:56 to 42:07 <- Fixing issue of solid missing if it transition to zero

Item 2. Point code and link code not working properly in section for non-parallel to section baseline.
Check out 52:23 to 55:29 <- Fixing corridor to surface automatically with null gap
Check out 55:29 to 58:06 <- Fixing point code issue for section
Check out 58:06 to 1:08:03 <- Fixing surface, link code and point code issue for section

Item 3. Good pick up about the volume that we need to check. Making sure you have Item 1 and 2 sorted will help prevent volume issue. As a designer, it is our task to check this values.

Bonus information:

I've summarized a detailed guide to corridor cross section workflow. Refer to message 2 of this <Thread Link>

Cheers,

Jowenn

[simon.erikssonM73T2]

Hi Jowenn! 

Great class and helpful tips!

Regarding "Check out 55:29 to 58:06 <- Fixing point code issue for section".

I've come across this problem but can't get that workaround to succeed when I have 2 corridors in different models and using Data Shortcuts.

If I put the "Markpoint" on the node, in this case center of the Road which also is the center of the Assembly, it wont read that point code in the other model with the section views.

If I choose another point code, it will though. I also tried connecting it to another node and then offset the "markpoint" so It would be in the correct place but as soon as I move it, it disappears from the section view in the other model.

Any thoughts?

My current workaround is to create Auto corridor Feature Lines from the corridors and project them into the section view instead.

/Simon

[dirk_brus]

This solution worked for me. I have a corridor with 2 baselines and my sample lines are build on a third alignment (not the best way of working, but it is a project bound method). this created strange representations of my corridors (point codes) and specially when targetting a lot. But making sure that all my sample lines are perpendicullar to my corridor when crossing and havind a frequency on that same place works.

thanks

[heyttorgonzaga17]

solved my problem, ty!!!