Open Roads and multiple file use.

The best practices information I've found suggest using different dgn files to seperate design data.

However if mainline and side road horizontal and vertical geometry
is stored in separate dgn files, it seems you lose the ability to project ‘profile
intersection points’ between files.  Is
this correct or is there a workaround?

This also seems true for civil cells. The ability to select
reference elements in separate dgn files does not seem feasible. Workaround?

Thanks, Ron

  • Ronald,

    I initially had issues- make sure the dgn eg main rd.dgn you are referencing in has the profile made 'active' in it before you reference it in to side road.dgn.

    After I made an active profile for each control, it was then able to project when referenced in.

    Hope this helps.

    Seb

  • Hi,

    Has anyone resolved this issue?
    I am having a similar problem with rules not being honoured across files.
    For example, if I have a vertical line in one file (File A) and I do a perpendicular snap to that line in the same file (File A) the snap will be honoured if I rotate the vertical line to a different angle. However, if I open a new file (File B) and do a perpendicular snap to the vertical line in File A, the snap in NOT honoured if I rotate the vertical line (in File A) to a different angle.

    This issue also significantly reduces functionality when having Alignment and Corridor data in separate files. For example, if I have a dynamic template drop in a corridor which is based on geometry (e.g. a curve/tangent point, kerb return location etc), this dynamic station will not be honoured if the alignment is altered in a separate file (This functionality works well if the alignment and corridor are in the same file, however best practice says to separate these file types).
    Any information on these issues would be appreciated.

    Thanks,

    Ryan