• State Not Answered
  • Replies 7 replies
  • Subscribers 140 subscribers
  • Views 7668 views
  • Users 0 members are here

Open Roads and multiple file use.

Ronald Brys
Offline

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

Parents
  • 0 Offline

    Ron

    Please look into some of the videos on the support site and MBUILDS channel  on youtube... mbuilds

    It is easiest to approach Open Roads Tech by giving comparisons to the legacy app you are using.

    So In a project you may currently use a DTM or a TIN... IMHO Terrains should be stored in there own 3D design file... if you want rename the DGN.. (example (TIN.DGN)

    Next is Geometry... Geometry is created in a 2D (seed). A user can create as man or as few Geometric alignments in a single DGN... So if the goal is multiple users constructing different alignments, each could work on a seperate Hz and the could all collectively beto a master geometry DGN

    Vertical > when the user begins defining the Vt  (profile) a 3D model is immediately created. any number of Vt (profiles) can be stored with a Hz but only one can be active!... Last Profiles can only be created in the file the Hz resides (IE you cannot profile a Hz that is in a reference)

    You can however use a referenced Hz to slope another profile (IE: I have a Hwy Alignment referenced to my Ramp geometry file > I need to set the beginning ramp profile at -3% from my Hwy CL > use the slope from element command and select the referenced Hwy CL as the slope reference and WA LA you can now snap your proposed aligned to the slope ref, whereby you have just created a rule in a profile.

    Civil will also work with references... see the cell placements on Mbuilds channel... these all use corridors and Geomerty referenced to the design...

    HTH

    Michael Barkasi

    Application Engineer 

    Reality Modeling



  • 0 Offline in reply to Mike Barkasi

    Thanks for the responses. I see how it's supposed to work but can not get successful results. Does it matter what models the elements reside in when trying to select alignments or features across references?

  • 0 Offline in reply to Ronald Brys

    Hi Ronald,

    I don't have a definitve answer to your question but I can confirm the following will work:

    File1.dgn - Main Rd Hz and Vz (2D model)

    File2.dgn - Side Rd Hz and Vz (2D model) - File1.dgn attached as a reference

    File3.dgn - (2D model) reference File2.dgn with live nesting (or reference File1.dgn and File2.dgn without nesting)

    Place civil cell in File3.dgn using alignments from File1.dgn and File2.dgn

    You can also do the same as above using 3D models.

    I guess there are many combinations of reference file arrangement and geometric design and so it may be easier to assist if you could outline the structure of your files and data.

    Regards

    Paul



  • 0 Offline in reply to Paul Cusack

    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

  • 0 Offline in reply to SebastianHolvast
    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
Reply
  • 0 Offline in reply to SebastianHolvast
    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
Children
No Data
Communities
Support and Services
Training and Learning
Social Media