hi, this is my first post in this forum as we have now started transitioning to Openroads coming from Inroads SS2.
Trying to use target aliasing on Openroads 2022 Release 1 but i'm unable to make it work.
I've done this in Inroads SS2 with no problem but for some reason can't make it work in Openroads.
On the snapshot, i'm applying a target aliasing on a corridor going above another corridor named Flare Area. My template is just a basic template with only Active Surface as the target.
As you can see on the snapshot, it is ignoring the corridor but only seeking to target the existing ground Mildred Lake.
Anything i'm missing here?
Have you tried unchecking the "Use Closest" option? It's a bit of a long shot. I don't think that option measures "closest" from the start of the end condition, rather it starts measuring from the template-defined location of the end point. I think.
i've tried both already. but something weird is something, i tried doing the same thing a trial corridor using the datasets that came with the software and I was able to do it. but on the actual project terrain and corridor that I'm working on, does not work. i must be doing something wrong but can't figure it out.
I used the same template, only different is the existing terrain model and the 2d dgn I used to create corridor.
It looks like you have three Flare Area corridors. Are you sure you've selected the correct one?
I've thought of that too and double-checked it several times. And just to be sure, i also tried adding the other corridors to be targetted first before the existing grade.
Hi Chris, my understanding is that Target Aliasing of another Corridor will not be available if there is a relationship between them that will potentially create a processing loop. Try double checking point controls, etc. and see if that is what is causing it.
Regards,
Mark
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023 | ProjectWise CE 3.4
I was able to resolve this by replacing the seed file I used.
for some reason, the global origin on client's dgn seed file causes it.
I have tried the following,
1. re-create the seed file using the dgn seed delivered with openroads by adjusting the global origin; still did not work.
2. use the dgn seed file without any changes on the dgn seed delivered with go=0,0,0; worked like a charm..
i have another topic posted here about volume cut and fill analysis not working but was fixed by using the updated dgn seed file.