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.
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.
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.
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...