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 geometryis stored in separate dgn files, it seems you lose the ability to project ‘profileintersection points’ between files. Isthis correct or is there a workaround?
This also seems true for civil cells. The ability to selectreference elements in separate dgn files does not seem feasible. Workaround?
Thanks, Ron
Working across files is supported and is working for geometry and civil cells. For example if you have a MainRd.DGN with a Centreline horizontal and vertical and then attach it as a reference to a SideRd.DGN you can then create a horizontal at 90 degrees to the main rd. You can also create a profile for the side rd with the profile intersection point and snap the vertical geometry to the intersection that will be maintained when either alignment moves. A civil cell can then be placed using the two alignments in the separate DGNs.
Regards
Paul
Hi Paul,
If I try projecting profile points or placing a civil cell using multiple files, I get the error message 'element is in a read only reference'. What am I missing?
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
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?
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.