Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Future consideration
Categories General
Created by Guest
Created on Aug 12, 2022

Floor Manager and Grid tools should recognise Coordinate Systems and enable defined building locations

On large projects, with multiple (& repeated) buildings it is common to model the building around the file origin, and then reference/place into actual location.

The current system does not recognise if the refernce is moved, so the floor manager/grid stays in the same location as the refence is moved.

Ideally I would like to be able to define a master grid, with setting out points that define building locations, that enable referencing of files relative to these points. (A little bit like shared coordinates, but better)

The individual building grids would then have a defined Origin which would enable snapping to the master grid setting out points, Ideally the referencing dialog would recognise these enabling selection in the reference location settings.

If the master grid was updated, the references would automatically reposition on next opening, much like updating GCS transforms/AEC Transform option


How frequently will feature be used? Several times a day
How much time will you save? This will prevent manual location of buildings within master models so may not save a massive amount of time but will greatly improve accuracy and reduce risk of error.
  • Admin
    Johannes Lerch
    Reply
    |
    Mar 20, 2023

    Hi Duncan, This is a good idea. We will discuss this internally for future consideration.

  • Guest
    Reply
    |
    Aug 16, 2022

    Adding my use-case:

    We often find that there is a "Site grid" with some local origin and a certain Z origin as well. For surveyor work, infrastructure, underground utilities, ... it's very useful to refer to that site grid.

    Buildings on the other hand use another reference. The X/Y position is not all that important on building layout drawings, we can just crop the drawings at the location we are looking at. The Z coordinate is another story though. Each building on a project (/building site) might have a different Z origin. I'm not sure how it is done in other countries but in Belgium it's common that Z=0 refers to the finished floor level of the ground floor. If each building has a different Z=0 related to the site origin it can be a bit chaotic.

    What I'd like to do is define my Floor Manager with the building's Z=0 coordinate for modelling and drawing generation of the building itself. When going to export IFC however we'll probably require the use of the Site origin/coordinates. For X/Y that would mean the grid lines will no longer align (because the building's reference is moved in the master model used for IFC export). That might or might not be a problem, depending on the IFC reader and whether or not the coordination actually uses those grids. The height (floor assignment) however will be a big issue. If the floor manager is defined for the building's Z=0 coordinate and the building is moved up/down in the master model then the model won't match the defined floors anymore.

    The only workaround I can see for now is to keep two BB_Floormaster.dgnlib files (maybe even in separate worksets) and with duplicated floor / grid assignment. One with the local grids / floors for the building, the other one with site grids/floors.

    It would be very useful though if that could be integrated in a better/autmated workflow!