Has anyone changed the global origin in model files before?
We have decided to lift the building 300mm during our design phase (OMG) But we have 6 dgn files and each dgn has a model to represent each floor, with 5 floors that's 30 files I have to go and move everything we have drawn so far. (hence the OMG)
I thought it could be easier to just change the GO in each model instead - lowered 300mm (as I could do this by a batch-command script) then my Z co-ordinates will read the correct RL?
How does this effect my Floor manager? Anyone have experience with this?
regards
Damon
Good question... The obvious result is that the Z elevation coordinates for those 30 models should read 300mm greater than they are now. However, I've never personally looked at how that interacts with the FloorMaster file. I would try backing up that file, then also changing the GO in the working copy to match up.
Of course, if anyone has first-hand experience in doing this that would be best. :)
I forwarded this on to a colleague that was just looking at a similar situation a couple weeks ago to get his thoughts on it. That experience would make him the one that has "first-hand experience". I think he is on-site this week, but I am hoping he might have an opportunity to chime in.
-travis
OK thanks Steve, also i am told there is a mdl "swa.ma" that highlights the SWA, but I haven't got this in either AECOsim or Microstation files... Any chance to get it for download? Cheers.
Please ignore, I found the mdl since posting thanks.
Yes, I totally forgot about that. It is a good visual indicator.
While we're busy making for of the situation, the reality is that, for some of us, the situation of the SWA DOES create real hassles. Many of our projects are over multiple locations or cover items that are 40-50km long and mean we are forced to manage multiple seed files depending on the location and run the gaunlet of probelms to be able to model itmes such as overland conveyors etc. AECOsim is NOT just used by building groups, though that seems to have been mostly forgotten.
Totally agree with you Bear, there is also an item that is not clear to me is what is the real impact of model being outside the SWA - I understand some elements have their own SWA which means they should not be affected... DO you happen to have any detail info on this?
Biggest issue has been in creating extractions, especially with any solids or forms modelled. Basically, we can't afford to be outside of the SWA. What does concern me though is being criticised by support for using seed files with too large a SWA. Most of my projects would fit inside of what they recommend as the 'ideal' SWA size.
I take it you mean "would NOT fit" right?
Yes.
So too large a SWA means you're loosing in Solids accuracy right?
So I have been told.