first the product details as i am using older version
Microstation V8i SS3 V-08.11.09.714
Inroads V8i SS2 V-08.11.07.566
Problem:
I have created a model for an realignment road works. I have a location where I want different end condition solution which I applied with end condition exception tool. The end condition exceptions replaces the original template solution fine but the origin points of new end condition seems doesn't move with the superelevation rotation at the same area. I have superelevation developed with superelevation tools and the pavement rotation is happening at the same area. It seems that the end condition start point from template doesn't follow the rotation but follows the gradeline (verticaly its downhill). I have found other people also had same issue before (almost 7 years ago) on this link
Superelevation and EC exception problem
I have some screenshot to show what exactly happening. I solved the model with alternate solutions but I would like to know why the end condition exceptions doesn't seem to work with superelevation tool. Is it a limitations of this version? or I am making mistakes somewhere and don't know where to find it? Hope someone can please help. Thanks.
The origin of your end condition must be constrained to the end of your backbone. With no constraints on the end condition it will maintain its position relative to the template origin, regardless of superelevation or other controls on the backbone.
Hi Ray, I tried that too earlier and got same results. I am re doing it just to show you the screen shot with constraints.
Are superelevation flags set at centreline and EOP? Have you considered 'vector-offset' instead of 'slope' to these two points?
This is SS2 so there are no superelevation flags. Changing the constraint type is definitely worth a try. You might also try controlling Lt_Road_Verge1 with a superelevation point control rather than some sort of slope constraint. I have to admit, I'm running out of ideas.
Hi Ray, thanks for the idea. I have to admit too I don't know what else can be done. FYI guys, the superelevation by itself is working it's just the connection between backbone to the end condition. It feels like the connection between the end condition and backbone is gone. It doesn't change with horizontal curve and super rotation. Means it stays at the first location where I put it at the begining chainage. No shift between horizontally and vertically to follow the corridor. I might try applying the superelevation point control on Lt_Road_Verge1 point too. Will let you know soon. thanks.
Gary Thanks for the idea of Vector-offset. Will try soon and update.
The other type of constraints also results the same thing. Also noticed another thing now when I try go change the constraints, the constraints get removed once I get out of the template modification and run the model. Next time I go in to edit the end condition exception template the past constraints from Lt_Road_Verge1 get removed. It doesn't stay.
Since it's in the backbone, I don't think you can control the location of Lt_Road_Verge1 with an end condition exception. I think you will need to change the constraints on that point in the template.
another thing I would like to inform, I have display rules for the backbone component. This rule switches off kerb and turn on verge at the end of road lane. This switching is controlled with parametric constraints to trigger at particular chainage.
I haven't used display rules very often. But since the break is between the verge and the end condition I wouldn't think that would be the issue.
One option is to use the corridor as is, with the end condition exception but without override and add the alternate grading as a secondary corridor or linear template along the last feature.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page