Would like to suggest the option to set the corridor feature definition while importing the IRD.
Thank you, Derricke. I know you guys are not a big fan of the IRD Remapper, but I am certain it will be a critical component in migrating our SS2 projects to OpenRoads if implemented and managed correctly. Here is an example of how the IRD remapper and this enhancement request can work together to provide our engineers the ability to make this transition as seamless as possible. We can all agree that the template drop interval has changed drastically from when it was used in SS2. The introduction of the interval multiplier in SS3 and the new corridor type and definition in ORD, just made matter more complex. Creating the new ORD corridor feature, which inherited some of the design stage settings from SS3/SS4, cannot be accomplished solely using the IRD. Including cardinal points and critical sections were part of the XIN preferences, while densifying the horizontal and vertical curves was part of the DTM Create Surface process.
The creation of the top and bottom meshes was not part of the SS2 workflow so there is no direct translation to remap to. On a typical SS2 project, a managed corridor in Roadway Designer may contain several template drops, with a variety of template drop intervals.
ideally we want to remap the intervals to a fixed number in order that the corridors can be more consistent once the corridor definition can be set in ORD. With this enhancement request, the template drop interval can be set beforehand and the interval multiplier along with the other corridor definition settings can be applied when the IRD is imported.
One of the safeguard design built into the IRD Remapper is the original IRD is never modified (read only). Our engineers can remap each IRD object or all at once, while the program creates a new incremental file at each instance.
MS (SELECTseries 2) Ver. 08.11.07.443Geopak Ver. 08.11.07.619