[OR] CR - Tool to import Civil Objects from Another File

Question

When Design information was saved in External files, it was a normal workflow to have a working file where we manipulate DTM's, ALG's, ITL's and IRD's as we refine our project. Once a workable design is created, we would open actual project Files and display the design data. The working files were not part of any deliverable. 
 With Open Roads Designer phasing out the Native Applications, we will need some way to export portions of our designs, in the same manner as these prior workflows. 
 LandXML so far only offers some limited capabilities - AFAIK, there is no easy way to export all civil geometry and all terrain elements automatically. I also don't know if Corridors and Templates have a LandXML format. 
 One way to remedy this, would be an Import Civil Object tool, that works similar to how you can import a model, saved view and more. 
 It would need intelligence, for example: To import a corridor, it should be able to import any active file elements that the corridor is dependent on. And if the dependency is in a reference file, offer to bring the reference attachment along or to import the dependent object from the reference file. It should also be able to detect if the necessary reference file is already attached, it offers to use the current attachment.

Mark Shamoun · Answer

Hi Andre, 
 
 Heres something I finally finished to export out a corridor as an IRD file from ORD using a Corridor Design Input Report. 
 
 As long as you LandXML out the dependency elements and import them into the new DGN (or reference them in), all looks to be rebuilt with all Template Drops, Point Controls, Parametric Constraints, Secondary Alignments, End Condition Exceptions being recreated using the IRD Import tool. 
 
 Limitations include no ability to recreate External References or Clipping Boundaries due to a limitation in the Corridor Design Input Report function of ORD (as of 2019 R2), and Corridors are created without the "Use Active Profile" flag enabled and without a Feature Defininition. 
 
 I hope to work on this a bit more so feedback is welcome. 
 Corridor-IRD_Export.xsl

Mark Shamoun · Answer

Hi Andre, 
 
 Heres an example I just put together with a Corridor IRD, Alignment Baseline XML and Corridor Dependencies XML. Not being an Inroads users, im not too sure what "traditional" IRD setups looked like, but this seems to work: 
 
 M120-Corridor_IRD.zip

Mark Shamoun · Answer

An interesting find is that ORDs IRD importer doesn't SEEM to care about the Corridor Baseline and Point Control OIDs (which is a big relief). As long as Plan and/or Profile name matches it seems to build things quite nicely. 
 The one exception to this is, as you observed, is "pure" Secondary Alignments that seem to specifically use OIDs. Funny enough, looks to be a defect here with what ORD reports as its OID as ive found it to be incorrect...