There does not seem to be a consistent answer on this Global Origin Issue. If I don't adjust the global origin, and my project has large numbers for northing/easting the resolution falls apart on the 3d models and they look awful. If I do adjust the global origin, so my project falls within the sweet spot for modeling, then other tools do not work. gINT does not like a shifted global origin, and ignores it, placing data in space at the location it would be at if the global origin were set at 0,0,0. I just found that ORD Annotation labels do the same thing. I place a data point where I want the label to be placed, and it zings out in to the far off location that coincides exactly the distance and direction of the global origin shift. What's the answer? Is there any way to get all the pieces to work in a multi-discipline setting?
There are so many things that do not work well with a global origin shift it is not worth doing it. There is little to no benefit to making this setting.
Leaving the Global origin at 0,0,0 would certainly be easier, but how do you get the models to look good in that case?
We clip our references for things like i-models from Revit that have a point at 0,0,0, etc. so only elements near our model are included. Toyed with Global Origin but gave up when it started causing other issues.
Regards,
Mark
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023 | ProjectWise CE 3.4