Corridor regions renamed when changing assembly

[jacob.dwyer]

Hi All,

Searched help and the boards a lot. Could not find what I was looking for. When I work with corridors, I want to name the regions in a way that helps me to understand where in the drawing they are. For example, I would like to name the region between the intersections with Road A and Road B "Road A to Road B". Pretty clear exactly what that is. However, if I ever need to switch out the assembly (say I want to change the side of the road the sidewalk is on) the region is automatically renamed. There is no way that I can find to disable this behavior, and any work-arounds I can think of are more work than simply renaming the region as I would like it to be named. 

I have posted the removing of this feature (or at least having an option to disable it) in the ideas..., but if there are any suggestions for the intervening 40 years before its implemented, I would love to hear them.

Thanks!

[ytzvib]

Hi,

You Can change the Naming template for your regions by going to settings in tool space right clicking corridor and selecting edit feature settings and in the dialog box expand default naming format and click on the small box by corridor region name template, in the next dialog box If you set the default to a custom  name and then with a counter then it will solve your issue.The reason why you need the counter is because you cannot have two regions with the same name. See attached image.

[jacob.dwyer]

I'm aware of the naming template for regions, but the options in it are painfully limited, and it does not address the issue that the region is renamed every time the assembly for the region is changed. 

Thanks for the suggestion though.

[ytzvib]

When you change the naming template to not be based on the assembly then it does not update every time you update the assembly. 

[jacob.dwyer]

I just did a test, and it still overrides the old region name, just with whatever i have in the naming template, regardless of its association to the assembly. Your solution only works if I want every region to have the same name. What version of Civil 3D are you working in? I'm in 2017 and it would be another argument to my boss to upgrade if this issue has been fixed.

[ytzvib]

Hi,

I'm in 2018 but I just tested it in a different drawing and I'm having the same problem so it has to be some setting because I have one drawing that it works and one that it doesn't. And when I IMPORTSTYLESANDSETTINGS then it does work I will try to find the setting.

[ytzvib]

Hi,

I don't know if this will help for you but when I forced back all child overrides then the naming worked. So in the settings tab right click corridor and near the naming for regions select the down arrow (it should now have an x on it)select ok and create a region again. See image.

[jacob.dwyer]

No Luck, I tried it both ways and the name still overrides. I appreciate the assistance though.

[jacob.dwyer · Accepted solution]

To come back to this, I did find a work-around that is effective for what I want. Since you can add the same alignment as a baseline multiple times to the same corridor, regions can be defined this way. Then the naming stays as I would like it, and it fixes some issues with feature line continuation between regions as well. There may yet be some unexpected pitfalls to using this method, I will update if I find any issues.

[kiribQXRVK]

Hi Jacob,

I have a workaround for this issue. If you change the assembly in the Region properties window (under modify region dropout button) the name of the region won't change. 

Also this is not a solution and it would be better if you could do this through Corridor properties window and if you have found some solution for this issue please share.

Thanks, Balázs

[jacob.dwyer]

Thanks for the interest in this years later! I've since stopped using the corridor properties window for the most part and edit my corridors using the tools in the contextual ribbon, so naming the regions has become a bit less relevant for me, since I largely identify the area I'm working in graphically now. I'm very visual and find that feedback a much better way for me to work personally. So I guess I solved the issue for myself by making it irrelevant to my workflow. I'm glad to hear there are some workarounds though.