InRoads DGNs to OpenRoads via Merge to Master: WHY?!

We have a procedure that everyone uses but no one really knows why and what the effects are.

From your new ORD Seed. dgn, reference in your old InRoads DGN.  And then Merge to Master.

Why?

I absolutely understand that for OpenRoads Projects we want to work from a consistent seed (with GCS, etc. etc. etc.).

What specifically does the Merge from Master do that a reference file does not?  I know it copies the data into the local file and then detaches the reference.  The old graphics are now in the local file with the new seed settings.   It also drops any SS2 or SS10 intelligence (and allows OpenRoads to open it (avoiding that "old Civil data, can't open" stop).  Does it do anything else?

We're also doing mass blind Import Models from the original "InRoads.dgn"  In of itself, this is bad practice, but the reference paths all point to the original files/models, not the new files/models.  See my other Ask about the file types (design models, derivative models (drawing production), and static standalone data) and costs/benefits of migrating or leaving.  Legacy DGNs to OpenRoads - Project Decisions 

Any referenced material would be greatly appreciated, as well as any insight you care to share.

Thank you,

  • When you attach a reference file, it tries to scale Master Units to Master Units. And if it is Coincident World attached, it aligns Global Origins vs Design Plan/Cube.

    A Merge into Master will adjust any resolution difference, global origin shift and possibly resolve any other scaled resource issues.

    We have used a resolution of 1000 PU:MU since IGDS days. The Connect Platform apparently expects a resolution of 10000. We tried to preserve our original resolution and it failed miserably. Additionally, we had a number of files with a GO shift. A lot of these were cells in a cell library. These were a real pain to fix. Finally, our Scale/Units/Sheet Sizes.def files were setup such that our Engineering scales had the 12" = 1' built into them. So our scales were not true ratios. 50 scale was also 1:50 instead of 1:600. This allowed us to define text sizes as decimal inches. This made them similar to Leroy lettering sizes, which at the time was second nature to most of the staff, having come up through the ranks from the days of manual drafting. Nowadays, this skill is a lost art. All of these factors make a simple opening of a V8i file anything but.

    Needless to say, we anticipate many a V8i project in the pipeline staying in V8i until its finished, unless it's thrown on the shelf for a few years.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • Chuck, you can't just throw out MU:SU:PU like that without some sort of Trigger Warning.  

    Pulling teeth with pliers and shot of whiskey is, nowadays, also a lost art.  Laughing

    We have been migrating InRoads projects to ORD, but without much context or consistency.  

    I'm just trying to understand the benefit of Merging to Master vs, keeping the old dead stuff as a reference.  I suppose it you have to edit the stuff in the file, that's the way in (if I recall, files with InRoads tags in them essentially lock out ORD (at least in some cases).

    Thanks for your detail there.  GO looks good for now, but you know how that goes.  Somebody, somewhere...

    Thanks!