Corridor Data Shortcut does not match corridor model

Corridor Data Shortcut does not match corridor model

oalfonso
Participant Participant
4,069 Views
17 Replies
Message 1 of 18

Corridor Data Shortcut does not match corridor model

oalfonso
Participant
Participant

Hi all.

I have a corridor that is divided in regions to model an intersection, the corridor in the model is shown fine but when I bring the corridor as Data Shortcut to a new drawing is not behaving the same, at the boundary between the two regions, the curb and edge of pavement from one side of the road cross the corridor to connect the curb and edge of pavement of the other side (see image attached). As I mentioned before, in the original model I don't have this problem.

 

Orlando

Civil Engineer

0 Likes
Accepted solutions (2)
4,070 Views
17 Replies
Replies (17)
Message 2 of 18

ecfernandez
Mentor
Mentor

Hi @oalfonso, I hope you're doing fine. In the drawing where you have the data referenced corridor, make sure the "feature line cross baseline" option is deactivated. If not, deactivate it, and data reference your corridor again

ecfernandez_0-1654199077323.png

Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 3 of 18

oalfonso
Participant
Participant

Thanks Camilo for the feedback. I did your suggestion but still not working, I even did on a new drawing and still has the crossing over lines.

0 Likes
Message 4 of 18

ecfernandez
Mentor
Mentor

Hi @oalfonso, that's a shame. Try this now. In the corridor properties window look for the "Feature Lines" tab, and there check this option

ecfernandez_0-1654200062784.png

If you have Inward, change to Outward to see if that fixes the problem. This must be done in the source drawing, not in the referenced one.

Let us know if it worked. Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 5 of 18

ecfernandez
Mentor
Mentor

Another option would be this. Hover over the feature line that is crossing from one side to the other. When the tooltip appears you will know the code of that feature line, and if you realize that it has to do with a feature line that can be deactivated or assigned a "NO DISPLAY" style just turn it off. Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 6 of 18

ecfernandez
Mentor
Mentor

Regarding the first option that you already tried. Make sure when you change the "feature line cross baseline" option, that this other property is activated before hitting OK or Apply and exit the window.

ecfernandez_0-1654200636592.png

Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 7 of 18

oalfonso
Participant
Participant

Unfortunately still not working, the option of "No Display" does not work in my case because I need to show the curb and EOP lines which are the ones giving me problem. Thanks.

0 Likes
Message 8 of 18

ecfernandez
Mentor
Mentor

I will try to infer what is happening without checking your drawing. The curb code for your curb return region and the left curb code of the main road is the same.  I mean, for instance, if you had for the main road (Curb_Left) and for the curb return (Curb_Right) that shouldn't be happening. This is pretty weird because that normally doesn't occur. However, the last resort would be to differentiate codes between regions and present them in the plan view through your code set style instead of the ones that are crossing the road. To achieve this, one option is to put a "MarkPoint" with the code of your preference on each subassembly and run the corridor again.

I hope this helps. Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 9 of 18

oalfonso
Participant
Participant

I added tow marked points (different names) on the subassemblies that are connected wrong but still the same, however, even adding marked with different names, the subassemblies still have the original same codes (Top of Curb, Back of Curb). Allow me to clarify something I said wrong at first, the issue is only with the curb/gutter subassembly, the EOP is correct, still very weir what is happening.

0 Likes
Message 10 of 18

ecfernandez
Mentor
Mentor

That's too bad. Pretty weird this issue. Would you mind posting your drawing to give it a look?

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 11 of 18

oalfonso
Participant
Participant

Camilo, I attached the model for your reference, the corridor name is NEW_ROAD-OPT 2, your help is highly appreciated. 

0 Likes
Message 12 of 18

ecfernandez
Mentor
Mentor
Accepted solution

Hi @oalfonso, I checked your file and it worked. I used "markpoint" to singularize the codes of both sides of the corridor so Civil 3D doesn't get that feature line crossing the road. I also used the configuration for "datareferenced" corridors that I previously mentioned. I have attached the two (the original and the drawing with the DREF corridor) files here.

I hope this finally solves your problem. Best regards!

 

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
Message 13 of 18

oalfonso
Participant
Participant

Thank you Camilo. Your solution worked, I was able to remove the crossing feature line when using the code set style where the Top/Back Curbs are off but if I set "All codes" on in my file, the Top/Back Curbs are still crossing, and I noticed that in your file doesn't happen, it looks to me that there is a setting in my file that I have it wrong. Below are the actions I took based in your response, please advise if I am missing something:

- I added the Marked points as suggested.

- In my reference file I verified the setting for "Save Command Changes to Settings" to "YES" and "Feature Lines Cross Baseline" to "NO".

- I made sure that in the original corridor drawing the setting under "Feature Lines" is set to "Outward".

 

On a site note, I actually imported the revised assemblies you sent to discard something related to the Markpoints and still having the issue. It looks to me that there is a setting within the corridor that is causing the problem.

Let me know if you can see what I am missing, if not, I can still use the code set style that is working.

Message 14 of 18

ecfernandez
Mentor
Mentor

Hi @oalfonso, that's pretty weird. Is the same feature line you first posted the one that is still crossing the road? or is it another? I don't think this is related to the C3D Versión, but in any case, I let you know that I used Civil 3D 2023. Which version do you have?

Regarding what you did, that was the same as I did with the file you sent me. However, I didn't have to set the "Outward." I let it as it was because I noticed that it was working.

My last advice would be to replace your work file with the one I sent you. I didn't change anything important, just the part we have been discussing in this forum.

Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 15 of 18

oalfonso
Participant
Participant

It may be related to the C3D version, I am using 2021. I even tried to reproduce what you did using the file you sent and create a new drawing calling the corridor from your file and the lines intercepts, very weird, but I least I can control with the code set style. Thanks for your help.

Message 16 of 18

ecfernandez
Mentor
Mentor

This issue intrigued me a lot. I was even searching the web to find a possible reason for this, but I wasn't lucky. So I'm happy to help @oalfonso. Have a good day! 

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes
Message 17 of 18

oalfonso
Participant
Participant

Camilo, It appears to be a glitch on version 2021, if I open the file in 2022 or higher there is not issue with feature lines interception even without adding Markpoints. Markpoint works only if you open the file in 2022 save it and later work on 2021, that explains why your file was correct when I opened in 2021. 

I think the solution for me is work on 2022 version. 

Thanks for all your help.

0 Likes
Message 18 of 18

ecfernandez
Mentor
Mentor
Accepted solution

Hi @oalfonso, I'm glad you finally solved it. You may be right about the version glitch. I tried with C3D 2020, and it worked identically to the C3D 2023. Have a good day!

Best regards!

Camilo Fernández

P.Eng | Transportation

EESignature

LinkedIn
0 Likes