I am working on a project where I have been trying to add an end condition override in a superelevated section of a road.
In this first picture I have the roadway modeled fine except I want the short slope on the right to go down instead of up. So I created an end condition exception for this area.
When I apply the end condition exception I get the following.......
You can see the contours become jagged in this area and the second picture shows the features a created with a hump.
I can't figure out why this is happening in a superelevated area. It is a simple 2 lane road. There is only 1 template. This also happened a little further up the road where there is a structure. I created an EC exception so the modeler would remove the slopes. When it came to the structure there would be a jump in the features and the contours would be jagged. The only way I could prevent that from happening in that area was to copy my template and remove the end conditions from the template. Even defining the EC to use backbone only did not rectify the issue.
Does anyone have any insight? This only happens in superelevated areas.
Anybody have any ideas/solutions with this?
Microstation CONNECT - 10.17.2.61
ORD - 2021 R1 10.10.1.3
ORD 2022 R1.1 - 10.11.3.2
ORD 2022 R3 - 10.12.2.4
Microstation v8i SS 10 - 08.11.09.919
Power InRoads v8i - 08.11.09.615
ProjectWise - 10.0.3.453
I ran the 1029typ-3% template with no problems. I ran super by the template method about the crown point. I placed an end condition over ride just past curve center where my alignment and surface triggered the cut solution you were having problems with. It worked fine for me.
When an issue like this can't be replecated I start looking for the "ODD" causes.
1) Did you try removing the rounding from your template?
2) Did you try compressing your surface?
3) Did you try a new DGN file?
4) Did you try creating a new geometry project and copying ONLY the alignment of interest into it and then closing the main geometry project?
I have found interactions between 'user data' (corrupt horizontal alignment, corrupt surface feature, a DGN glitch) can cause errors where there should be no error.
Thanks for the reply.
1) No I did not try this.
2)No
3)Yes
4)yes
I don't think compressing the surface will make a difference. Usually when I run a surface and have issues I delete the surface and re-run it. I re-ran this surface several times after deleting the original with no difference. I don't know that removing the rounding makes a difference either since I applied an EC override to remove the cut and force a fill condition where there is no rounding.
I will need to give these suggestions a try when I get back to that project so I can rule them out.
Thanks again,
Mike
Mike,
I don't think removing the rounding will make a difference either but you have to eliminate every possible issue.
I mean for you to compress the target surface. I've seen various InRoads commands fail due to errors in the surveyed / target surface.
You might try exporting the target surface to LandXML and then importing the file back to InRoads as a new surface. That should eliminate the original surface as a possible cause. You might consider export/inport triangles only and render the new surface to check for holes.
Paul
Thanks, I will need to give it a try when I get back on that project. I got it to work a different way for now.