I am tryingto locally modify the edge of a path to match the fall of a crossroad. The edge point is created in the template, I am then profiling the edge point, and attempting to manually insert a profile into the profile that has been created by the template.
I have managed to break the profile that has been created by the template and then make the changes I require. I have then made a complex element and set this as the active profile, however it doesn't want to override the vertical alignment that is automatically created by the template as when I look at the cross section, the point is still above the existing surface.
Is there something I'm missing?
The image below shows the profile (the one created by the template is in cyan and the one in white is the modified profile that I have set as active). I have also attached a cross section view with the point circled that I am trying to modify.
I'm not certain, but I think the profile of the element controlled by the template is...controlled by the template. It's not an independent element that can be set on its own. I could be wrong, but the elevations of that feature are derived from its relation to the rest of the template geometry. I don't think you can define a different profile for it. I could be wrong...
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
You need to use a corridor point control to do this. Trying to override a template point profile will either get lost on corridor reprocessing or even eventually corrupt that feature, etc.
Try creating some geometry that has profile you want to apply and point control that edge to it.
OpenRoads Designer 2022 R1 (10.11) | Microstation CE Update 17.2 | ProjectWise CE 3.4
Thanks for the advice Mark - I managed to get it working doing that earlier.
I was still having an issue with a recursive solution, however that was due to using the partial offset to create the point control string. After removing all rules, and using that string to apply the vertical with a point control its all working. It just means that if that point moves in the future, the process has to be manually repeated as the point control string won't move with the corridor. Slightly annoying but workable.
yep, if you have a standard offset from your alignment you could have it offset from that making it a little less manual.