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
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?
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.
Yes, I totally forgot about that. It is a good visual indicator.
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.
For me, "moving the GO" simply means assigning specific coordinates to a designated location. So instead of the SWA center being 0,0,0 it could be something like 20000, 20000, 0. You would still be modeling within the SWA, but would also see real world coordinates based on the project's location.
Geo-referencing/coordination takes this a step further by aligning coordinates across multiple files/disciplines. It's certainly not something I work often with myself, but it seems to be the preferred workflow AFAIK. Further information can be found here:
http://communities.bentley.com/products/microstation/w/microstation_v8i__wiki/geographic-coordinate-systems-fundamentals.aspx
http://communities.bentley.com/products/microstation/w/microstation_v8i__wiki/geo_2d00_coordination-with-microstation.aspx
http://communities.bentley.com/products/microstation/w/microstation_v8i__wiki/georeferencing.aspx
This section covers the interaction between Geographic Coordinate Units and Model Storage Units so also may be of interest:
http://communities.bentley.com/products/microstation/w/microstation_v8i__wiki/5898.aspx