Auto Corridor Feature Lines not Dynamically Updating (Crossing Point Problem?)

[izzyloh]

Hi All,

I have a corridor with multiple regions. Each region is using a subassembly to generate a gutter (link) and lip (point) among other things. I have extracted dynamic Auto Corrdior feature lines to help model some areas beyond my lip, but some of them do not update as I change my corridor profile (see attached).

Also, it appears that the auto corridor feature lines that are not updating are ones that have been extracted from regions using offset baselines. All auto corridor feature lines are not on any site, and all use the same style.

Thanks - 

[tcorey]

As general information, not necessarily directed at @izzyloh , but for everyone: Even though they are called Auto Corridor Feature Lines, they might not be dynamically linked to the corridor. During extracting the feature lines from the corridor, check the Settings button to be sure the box is checked for Dynamic link to corridor. 

On to your specific question. If you check on the Feature Lines tab of Corridor Properties, is the box checked in the Connect column, for the feature line from which the extraction was made? I has to be checked or the auto corridor feature line will no longer dynamically update. If you turn connect back on, re-build the corridor, the extracted feature line will re-connect to it's parent in the corridor.

[izzyloh]

Thanks for your response Tim. I have checked my corridor properties and the "connect" box is checked. I have also confirmed that the auto corridor feature line(s) in question are set to dynamically update.

I have a sneaking suspicion that extracted feature lines from offset regions don't work as advertised / as they should. I will do some testing and let everyone know.

I also recorded a screencast of me checking what was mentioned:

https://www.screencast.com/t/GptueFeHvDTL

Thanks - 

[mjung]

Just ran across this problem as well. Did you ever find a solution?

[izzyloh]

Unfortunately not - shortly after the last reply on this thread we changed our workflow to avoid this scenario.

[ndegan]

We are running into this issue in my office as well. Do you mind sharing your changed workflow to see if it works for anyone else? 

Our specific reason for using for using the auto corridor feature line is to add it as a baseline for curb on a parallel parking area on a road corridor.

[izzyloh]

We've been trying out link omissions instead of using floating subassemblies or offsets:

https://forums.autodesk.com/t5/civil-3d-forum/subassembly-with-offset/m-p/8092837#M374861

Additionally, we've been extracting feature lines as joined between regions.

Hope this helps!

[izzyloh]

Nick,

We are developing our worklflow to use styles to manage "split point resolution" for feature lines. I ran into a fluke where I was able to violate the the style hierarchy. Somewhat similar issue ensued: i had a segment of auto corridor feature line just floating, not where it should be (per the corridor framework).

However, I found that if you go into the feature line properties dialogue box... just to open it, and then close it, the auto corridor feature line seems to look back at the corridor to update itself and it's PVI's. Check out the GIF below.

Maybe this "open the feature line properties dialogue box and close it" will help your situation. If it works, please let me/us on this thread know.

Thanks!

[MMcCall402]

I just had a very similar situation.  I was having a location along the Auto Corridor featureline that wasn't updating at a location the coincided with another feature line in the same site even though it was higher in the feature line hierarchy for the site.   I tried opening and closing the feature line properties as you suggested but there was no change.  Then I noticed in the image you posted that the your feature line had Smoothing unchecked.  Once I unchecked it everything worked as expected.  The auto feature line updated when the corridor was rebuilt and in turn changed the end elevation of the other feature line where it crossed.

[ndegan]

Thanks for the info MMcCall402 and izzyloh! I haven't seen this issue in a while but I will try these steps the next time I do and see if it helps.

We don't really use the feature line style hierarchy in our work, all feature lines go on the same style (I know we are missing out on a nice feature but I have bigger training fish to fry at the moment). Though we don't use the hierarchy, it still exists and has its order. I will check that again and make sure our default style is on top. As for the feature line smoothing, I can't remember if this was checked or unchecked in the problem file I had originally but I just created a new auto feature line and it did have smoothing checked by default. Next time I see the issue I will try these workflows out.

[b.herronN65PF]

I used a single region & assembly for my lanes, extracted the ETW (Edge of Traveled Way) to use as a baseline for regions with varying scenarios of curb & gutter..... and it looks like if you use the Dynamic AutoCorridor Feature Line as a baseline for another region that the dynamic link switches to the new region, because when I adjusted my profiles that new region for my curb & gutter assemblies did not follow, even though all indications are that it's still dynamic. Now my entire subdivision is jacked. Is there any way to see what REGION the auto corridor feature line is dynamically linked to?

[mark.reeveTXANL]

I've had this a few times and found that if you select the featureline that needs to be updated open the properties, uncheck dynamic link, apply, then re-check dynamic link it updates itself.

The disclaimer: This only works occasionally, 50/50 at best. I've found corridor featurelines to be pretty temperamental so try to avoid using them when possible.