ORD Template drop using internal station

I created several corridors along alignments that have a manually set start chainage. This start chainage is something like 1633.790 instead of 0.000
The chainages that the corridor and the template drops use are what you can see and read out using analysis functions. They all are what you expect in relation to the chainage.
When creating a corridor results report, and checking the raw xml data, there is both an external station and an internal station. The difference between these is equal to the start chainage of the alignment.
Now I have an new alignment that starts at chainage 0.000, and I’m transferring the corridors over to this new alignment using reattach corridor.

This is where it gets interesting.

Every template drop in the corridors I have transferred to the new alignment jumps to a location somewhere to the beginning of the new alignment.
When creating a new corridor results report from this displaced corridor, the internal station and external station are the same.

This is where I think the problem originates.

Somehow the corridor uses the internal station, but presents the external station to the user.
This works fine until you start using an new alignment where the stationing is different and the internal station is used to place the corridor on the new alignment.
This also works down to the parametric constraints.

I have added several images to show the change in stations, both from within ORD and from the reports.

I would really like to know how to avoid this. Did anyone else have the same problem, and have you solved this without having to change all chainages by hand?

At the moment I’m using ORD 10.06.00.38. I had the hope this would be solved in release 10.07.00.56, but unfortunately it’s not.

template drop old alignment
template drop old alignment

template drop new alignment
template drop new alignment

constraints old alignment

constraints new alignment

corridor report showing internal and external station

Parents
  • I filed the enhancement request 1021494 concerning the corridor reattach command not honouring the customised start station.

    Are you familiar with the concept of Design Intent with ORD? Basically the application will remember where and on what you snapped to apply the template drop and will keep it as reference. I thought you could use this capability as a workaround. You could draw line where your template drops should apply.

    See this video for more information: https://youtu.be/y8J1jc_CXtI

    Let me know if I'm not clear enough.

  • looks it is not solved... I had an alignment (baseline) negative (-)1+000 to 2+500. Corridor was build starting at 0+000. Then the baseline was shortened at the beginnig to start at negative (-)0+500 to end at 2+500. Station 0+000.00 remaned phisically at the same location. Corridors are corrupted now. Template drops, point contols, key station and paramietric constraint are moved. Looks all corridor settings in corridor objects are based on physical stationioning of baseline element rather than on the station. So template drop taht should be at 0+00.00 after trimin first 500 m is now at 0+500. Stationing I provided are hust example. Take look at th reports of corridor input befor and after alignment changed. Only internal station is the same. X, Y, external station are different.

    I am posting this here to warn you - if you need to change baselinene when corrdors are done - just be carfull with OpenRoads Disaster - I have massive work to be done. 

    Best,

    Adam


    OpenRoads Designer 2023   |  OpenRail Designer 2023

                 

  • need to add - I got XML with alignment form external designer and keep updating dgn by importing geometry from XML. Have no idea why Northing and Easting of my template drops were changed - see print screen from raw reports above.

    Best,

    Adam


    OpenRoads Designer 2023   |  OpenRail Designer 2023

                 

  • Hi Adam,

    Since SS4, all Corridor stations in OpenRoads look to be stored as an internal distance from Alignment start value that all adjust if the Alignment start is changed, ie changing to maintain the same distance from alignment start.

    This has caused us much pain in the past but I have been told that this is apparently resolved in the upcoming 10.10 release.

    In the meantime, we snap all point control and parametric constraint stations to CAD lines to anchor them in an XY location. Annoying, but we get piece of mind if the Alignment start needs to move.

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

Reply
  • Hi Adam,

    Since SS4, all Corridor stations in OpenRoads look to be stored as an internal distance from Alignment start value that all adjust if the Alignment start is changed, ie changing to maintain the same distance from alignment start.

    This has caused us much pain in the past but I have been told that this is apparently resolved in the upcoming 10.10 release.

    In the meantime, we snap all point control and parametric constraint stations to CAD lines to anchor them in an XY location. Annoying, but we get piece of mind if the Alignment start needs to move.

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

Children
No Data