Is anyone else still dealing with the legacy of V7DGN Global Origin Offsets in the civil design world?
In vanilla MicroStation:
Due to the use of a Global Origin Offset in legacy V7DGN format files, the same Global Origin Offset was added to our V8DGN format files to allow us to attach V7DGN references using the "Coincident - World" method and have all coordinates align.
This also allows for the conversion backwards from V8DGN to V7DGN when required (not so much any more) without that pesky "Off the Design Plane" error.
In OpenRoads Designer:
If this same Global Origin Offset (go=-4425.954,5656450.832 based from xy=0,0,0\uor) is applied to the metric seed files delivered with ORD, will it cause any problems with the ORD Civil Design tools?
Do I leave the GO as delivered and use the reference attachment "Coincident - World" when attaching legacy data files that have the Global Origin Offset applied to keep the geographic coordinates aligned between the files?
Thanks for your insights!
The old Texas seed files used to have a global origin shift in them as well. This initially caused major problems with the SS4 product. It was fixed in subsequent releases of SS4 and in ORD....BUT, why take the chance if you don;t absolutely need to? The program is finicky enough as is so adding in more complexity is never a good thing.
I would say do it as your own risk.
Marc
The sheet tools do not deal well with global origin shifts. A sheet border reference file must have its border graphics drawn with xy=0,0 being the lower left corner of the sheet in a file with GO=0,0 (Center, Center)
We found Coincident World addressed mismatched global origins, while coincident did not.
We carried our shifted global origin over without even realizing we were doing it. Resetting our seed files to remove the shift did not seem to raise any big issues except when we had to issue a new set of sheet borders. Since we knew the coordinates before and after, it was possible to setup a keyin to be recalled repeatedly as one fixed any files that were affected.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Hi Marc and Charles.
I tend to agree with you that I should proceed without the GO shift when setting up our new implementation of ORD.
Regards,
Bert